❔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.

How does Arcwise store sensitive data securely?

We use authenticated encryption to protect sensitive data, ensuring both confidentiality and integrity. Each organization has a unique encryption key. The key is securely generated using an industry-standard algorithm and is 256 bits in length, providing strong protection against unauthorized access.

This approach is used for both organization level credentials (like API keys) and data warehouse connection credentials (like keyfiles and passwords).

Why does the app request Google permissions?

Our app requests the following Google OAuth scopes to perform specific actions on the user behalf and to ensure a seamless user experience:

• https://www.googleapis.com/auth/bigquery - Allows the app to execute BigQuery queries on user behalf.

• https://www.googleapis.com/auth/drive.file - Lets the app create and edit only the files it has opened or created in your Google Drive.

• https://www.googleapis.com/auth/spreadsheets - Enables editing of Google Sheets documents on user behalf.

• https://www.googleapis.com/auth/presentations - Enables editing of Google Slides presentations on user behalf.

• email, profile, openid - These are used for login (when SSO is not used) and to retrieve basic user information like name and email address.

We only request the minimum necessary permissions to support features like querying data, updating documents, and authenticating your identity.