---
title: "Onboarding a Snowflake Organization application in Britive"
slug: "onboarding-snowflake-org-application-in-britive"
updated: 2026-04-16T07:10:47Z
published: 2026-04-29T10:51:57Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.britive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Onboarding a Snowflake Organization application in Britive

Follow these steps to configure the Snowflake Organization application in Britive.

1. Log in to Britive with administrator privileges.
2. Click on **System admin** -> **Tenant Applications**.
3. Click on **Create Application**from the **Tenant Applications** page.
4. Click the **Add (+)** sign inline with the Snowflake application on the **Add Application** page.
5. Enter the following values in the **Application**tab:
  1. Enter the **Application Name**.
  2. Enter the **Application Description**, if required.
  3. Select the **email** in the **Account Mapping.**
6. Click **Next**. The **Settings** tab is displayed.
7. Enter the following details on the **Connection Properties**page:
  1. Enter the **Account ID** of your Snowflake instance.
  2. Replace **{accountId}** with the Account ID in the **Login URL**.
  3. Enter the **Username of the user in Snowflake** created in this section, [Configuring on Snowflake application](/v1/docs/configuring-on-snowflake-application).
  4. Enter the **Custom Role assigned to the user** created in this section, [Configuring on Snowflake application](/v1/docs/configuring-on-snowflake-application).
  5. Upload public and private keys created for the custom user. For more information, see [Configuring on Snowflake application](/v1/docs/configuring-on-snowflake-application).
  6. Enter the password of the encrypted private key in the **Password of the Private Key** field. Leave this blank if the private key is created without a password.
  7. Select **Use login name for account mapping** if you want to use the login name field in Snowflake instead of the name field for account mapping during a scan.
  8. Select **Use same user, role and keys for all accounts** if you want to copy the settings to other accounts scanned by this app.
  9. Select **Skip collecting schema level privileges**, if schema level privileges are not needed for collection during a scan.
8. **Profile Settings**: Configure the maximum session duration for profiles. You can select the duration between 15 minutes to 7 calendar days. This allows to setup expiration duration for each profile while creating/updating the profile up to this configured value. If existing profiles are created with more than 12 hours and the above setting is changed, then it cannot be lowered until all profiles are updated with a lower expiration duration.
9. Click **Save and Test**. A pop-up displays a success message if the environment is correctly configured. If any error message is displayed, review the error, correct the configuration, and test again.