> For the complete documentation index, see [llms.txt](https://docs.arcwise.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcwise.app/espanol/configuracion-de-arcwise/faq.md). # FAQ ### **How can I see if permissions were set properly to use Arcwise?** Using the `ARCWISE` role (or whichever role + user you have set up) run `show tables` in Snowflake. You should see all tables you intended to share access to listed there. ### **I am having trouble granting permissions to Arcwise. What can I do?** Reach out to us! Common issues include: * **Snowflake:** Granting access without including grants to `FUTURE`. Often times tables will be dropped and recreated by jobs. When this happens the access is removed unless `FUTURE` is included. ### **How and when does Arcwise use database compute?** Arcwise uses database compute in two ways: * When using **Connect Data** Arcwise will execute a `SELECT * XXX LIMIT 1000` query to preview the data. * When executing an Arc formula, EG `ARCCOUNT`, this is translated to an SQL query that will be executed in your warehouse. ### What does Arcwise do with access to DBT? Arcwise does the following: * read dbt artifacts * read results of last dbt job * read semantic later proxy URL (if you have it set up) Arcwise *doesn't* run any jobs. It is sufficient to grant Arcwise `Job Viewer` permissions. ### **What does Arcwise do with access to Snowflake database data?** Arcwise uses this access to read query history (SQL only, not data). This query history is used to present the most relevant tables, columns, and joins to Arcwise users. ### **What data is stored by Arcwise?** For basic usage of the tool we store: * names of tables * names of columns If we are granted access to Snowflake database data we additionally store query history (SQL only, not data), usage counts of tables, usage counts of columns, and usage counts of joins. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.arcwise.app/espanol/configuracion-de-arcwise/faq.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.