Accounts and Security · Topic 14 of 17

User, Role and Grants Provisioning and SCIM

Provision users, roles and grants at scale: system roles, SCIM with Okta or Entra ID, managed access schemas, future grants and security integrations.

  • 5 min
In a nutshell
  • USERADMIN creates users and roles; SECURITYADMIN manages grants; SYSADMIN owns objects.
  • Future grants and managed access schemas keep grants consistent and centralized.
  • SCIM maps IdP users to users and IdP groups to roles, through a provisioner role that owns the objects it creates.

What it is

Provisioning is the process of creating users and roles and giving them the right grants, and keeping that in step with the identity provider as people join, move and leave. At architect level the question is who should do it, with which role, and whether it should be automated.

Snowflake has two supporting ideas. System roles divide the administrative work, and security integrations connect Snowflake to external identity systems, including SCIM for automatic provisioning.

Identity providerOkta or Entra IDSCIM requestsSCIM integrationruns as provisioner rolecreatesUsers and rolesowned by provisionergranted toFunctional rolesaccess to data

How it works

System roles and separation of duties

RoleResponsibility
ORGADMINManages the organization and its accounts
ACCOUNTADMINTop account role; contains SECURITYADMIN and SYSADMIN
SECURITYADMINManages grants globally (MANAGE GRANTS); contains USERADMIN
USERADMINCreates and manages users and roles
SYSADMINCreates warehouses, databases and other objects
PUBLICGranted automatically to every user and role

The design principle is separation of duties. The role that creates users and roles (USERADMIN) is separate from the role that owns data objects (SYSADMIN). Custom roles should be granted to SYSADMIN so that administrators can still reach the objects those roles own.

Exam tip

Build a role hierarchy from functional roles (what a person does, for example ANALYST) and access roles (what data they may touch, for example SALES_READ). Grant access roles to functional roles, and functional roles to users.

Grants at scale

TechniquePurpose
Future grantsGRANT SELECT ON FUTURE TABLES IN SCHEMA s TO ROLE r covers tables created later
Managed access schemasOnly the schema owner or a role with MANAGE GRANTS can grant on objects in the schema, not the object owners
Database rolesRoles scoped to one database, useful for sharing and for packaging privileges
Secondary rolesUSE SECONDARY ROLES ALL combines privileges of all granted roles in a session
COPY CURRENT GRANTSKeeps existing grants when a table or view is replaced

A managed access schema is the answer when a scenario says object owners must not be able to hand out access on their own. Without it, the owner of an object can grant privileges on it.

User types

A user has a type that tells Snowflake how it signs in. PERSON is for humans and may use a password with MFA or SSO. SERVICE is for programs and uses key-pair, OAuth or programmatic access tokens, with no password and no MFA. LEGACY_SERVICE is for older programs that still use a password. Choosing the right type matters because MFA requirements apply to people who use passwords, not to service users.

Security integrations

A security integration is an account level object that sets up a trust relationship between Snowflake and an outside system. One CREATE statement exists per kind, selected by TYPE.

IntegrationPurpose
SAML2SSO with a SAML 2.0 identity provider
OAUTHSnowflake OAuth for partner or custom clients
EXTERNAL_OAUTHTokens issued by an external authorization server
SCIMAutomatic provisioning of users and roles from an identity provider
API authentication (API_AUTHENTICATION)Lets Snowflake authenticate to external services with OAuth, for example through external access or a Git repository

Creating one needs the global CREATE INTEGRATION privilege (held by ACCOUNTADMIN by default) and the integration can be changed with ALTER SECURITY INTEGRATION. A network policy can be attached to an integration to limit where its requests come from.

SCIM provisioning

SCIM 2.0 lets the identity provider (the client) call Snowflake (the service provider) to create, update and remove users and roles. Snowflake supports Okta, Microsoft Entra ID and custom providers. Users in the IdP map one to one to Snowflake users, and IdP groups map one to one to Snowflake roles.

The integration runs as a dedicated provisioner role, one for each kind of provider.

ProviderProvisioner roleSCIM_CLIENT value
OktaOKTA_PROVISIONEROKTA
Microsoft Entra IDAAD_PROVISIONERAZURE
CustomGENERIC_SCIM_PROVISIONERGENERIC
CREATE ROLE aad_provisioner;
GRANT CREATE USER ON ACCOUNT TO ROLE aad_provisioner;
GRANT CREATE ROLE ON ACCOUNT TO ROLE aad_provisioner;
GRANT ROLE aad_provisioner TO ROLE accountadmin;

CREATE SECURITY INTEGRATION entra_scim
  TYPE = SCIM
  SCIM_CLIENT = 'AZURE'
  RUN_AS_ROLE = 'AAD_PROVISIONER';

SELECT SYSTEM$GENERATE_SCIM_ACCESS_TOKEN('AAD_PROVISIONER');

The generated token is given to the identity provider and is valid for six months, so it must be renewed on a schedule. The provisioner role must own the users and roles it imports, otherwise later updates from the IdP do not synchronize.

Watch out

Users and roles created by hand before SCIM was enabled are not owned by the provisioner role, so SCIM cannot update them. Transfer ownership first or recreate them through the IdP.

Combining SCIM and SSO

SCIM only creates identities. Authentication is separate. The usual design is SCIM for provisioning and a SAML2 or OIDC integration for sign-in, with users created without a Snowflake password so they must authenticate through the IdP.

Common mistakes

Using ACCOUNTADMIN for provisioning. Use USERADMIN for users and roles and SECURITYADMIN for grants, and keep ACCOUNTADMIN for rare tasks.

Creating objects as SECURITYADMIN or USERADMIN. Those roles are for security administration, not for owning data objects. Use SYSADMIN or a custom owner role.

Expecting SCIM to authenticate users. It provisions only. Add SSO for sign-in.

Letting the SCIM token expire. It lasts six months and needs regenerating.

What to remember for the exam

  • USERADMIN creates users and roles; SECURITYADMIN manages grants; SYSADMIN owns objects.
  • Future grants and managed access schemas keep grants consistent and centralized.
  • SCIM maps IdP users to users and IdP groups to roles, through a provisioner role that owns the objects it creates.
  • Provisioner roles: OKTA_PROVISIONER, AAD_PROVISIONER, GENERIC_SCIM_PROVISIONER.
  • The SCIM token comes from SYSTEM$GENERATE_SCIM_ACCESS_TOKEN and lasts six months.
  • A security integration is created with CREATE SECURITY INTEGRATION ... TYPE = ....

Check yourself

  • Which design stops table owners from granting access to others?

    Put the tables in a managed access schema. Then only the schema owner or a role with MANAGE GRANTS can grant privileges on them.

  • Why does a SCIM update from the IdP fail for one user created manually?

    The provisioner role does not own that user. SCIM can only update objects it owns.

  • Does SCIM provide sign-in?

    No. It only provisions users and roles. Sign-in needs SSO or another authentication method.

Topic 14 of 17 in Accounts and Security

Test yourself on Accounts and Security

The full Snowflake ARA-C01 question bank has 687 questions, with timed practice exams and an explanation for every answer.

This study guide is independent and is not affiliated with, endorsed by, or sponsored by Snowflake. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.