Organization SCIM API differences (Preview)

Organization-scoped SCIM uses the same /scim/v2/ endpoints as account-scoped SCIM. HTTP headers, the base URL, pagination, filters, and request examples are in the user API reference and the group API reference. This page lists the attributes Snowflake supports for an organization user and an organization user group, and the privilege each endpoint checks.

Create the integration with Provision organization users and organization user groups with SCIM (Preview).

Organization user attributes

For an account user, MAP_SCIM_USERNAME_TO_ENTERPRISE_ATTR chooses whether userName maps to NAME or to LOGIN_NAME. For an organization user, userName is always LOGIN_NAME. NAME is snowflakeUserName, or userName when snowflakeUserName is omitted.

Organization users don’t have a password.

The following table lists the organization user attributes that Snowflake supports:

SCIM User AttributeSnowflake User AttributeTypeDescription
idAssigned by SnowflakestringThe immutable, unique identifier of the organization user. Use this value as members.value when you add the user to an organization user group. Snowflake doesn’t return this value in the SHOW ORGANIZATION USERS output.
userNameLOGIN_NAMEstringThe identifier used to log in to Snowflake. This property can’t be changed after the user is created. An update with a value that differs only in case is accepted, and that value is returned in the response. LOGIN_NAME is stored in uppercase. An update that changes userName to any other value returns HTTP 400.
name.givenNameFIRST_NAMEstringThe first name of the user.
name.middleNameMIDDLE_NAMEstringThe middle name of the user.
name.familyNameLAST_NAMEstringThe last name of the user.
emailsEMAILstringThe email address of the user. This is a required property. A request that removes emails returns HTTP 400.
displayNameDISPLAY_NAMEstringThe text shown in the user interface when referring to the user.
externalIdN/AstringThe unique identifier set by the provisioning client, such as Microsoft Entra ID or Okta.
activeDISABLEDbooleanDisables the user when set to false. A PUT that omits active enables the user.
groupsN/AstringA list of groups to which the user belongs. The group displayName is required.
meta.createdCREATED_ONstringThe time the user was added to Snowflake.
meta.lastModifiedUPDATED_ONstringThe time the user was last modified in Snowflake.
meta.resourceTypeN/AstringThe type of resource. The value is User.
schemasN/Astring

An array of strings specifying the namespace URIs. Snowflake supports the following values:

  • urn:ietf:params:scim:schemas:core:2.0:User
  • urn:ietf:params:scim:schemas:extension:enterprise:2.0:User
  • urn:ietf:params:scim:schemas:extension:2.0:User

Custom attributes

Use the same namespaces as Custom attributes.

The following table lists the custom attributes that Snowflake supports for an organization user:

SCIM User Custom AttributeSnowflake User AttributeTypeDescription
snowflakeUserNameNAMEstringThe Snowflake identifier of the user. This property can’t be changed after the user is created. A value that differs only by casing is accepted, and the original value is preserved. When omitted on create, NAME is set from userName. An unquoted value is stored uppercased. A quoted value keeps its case.
allowedInterfacesALLOWED_INTERFACESstringDefines which Snowflake interfaces the user can access. Specified as a comma-delimited list of interfaces. If a value other than ALL is specified, then users can only access the interface specified and can’t interact with any Snowflake data outside of the interface specified.
defaultWarehouseDEFAULT_WAREHOUSEstringThe virtual warehouse that is active by default for the user’s session upon login.
defaultRoleDEFAULT_ROLEstringThe primary role that is active by default for the user’s session upon login.
defaultSecondaryRolesDEFAULT_SECONDARY_ROLESstring

The list of secondary roles that are active for the user’s session upon login. You can set this attribute to ALL as an alias for ('ALL'), or you can set this attribute to NONE or "" as an alias for ().

typeTYPEstringThe type of the organization user. You can set this attribute to either PERSON or SERVICE. For what SERVICE changes, see Organization user types.

Organization user endpoints

You manage organization users through the same SCIM endpoints as account-scoped SCIM. See the user API reference. A missing privilege returns HTTP 403. A list or a userName lookup without MANAGE ORGANIZATION USERS returns no users.

The following table lists the privilege that each endpoint checks:

EndpointPrivilege
GET /Users and GET /Users?filter=userName eq "..."MANAGE ORGANIZATION USERS
GET /Users/{id}MANAGE ORGANIZATION USERS
POST /UsersCREATE ORGANIZATION USER
PATCH /Users/{id} and PUT /Users/{id}MANAGE ORGANIZATION USERS
DELETE /Users/{id}MANAGE ORGANIZATION USERS

GET /Users returns a page of organization users. With MANAGE ORGANIZATION USERS, the query matches every organization user in the organization. totalResults is the number of matching organization users, including users that aren’t on this page. This differs from account-scoped SCIM, where totalResults equals startIndex + count when another page is available. See the user API reference.

GET /Users?filter=userName eq "..." uppercases the filter value and matches that LOGIN_NAME. userName sw uppercases the filter value and matches a LOGIN_NAME that starts with it. LOGIN_NAME is stored in uppercase. The filter doesn’t also search for the original casing.

DELETE /Users/{id} drops the organization user. See Removing users from all regular accounts.

Organization user group attributes

In organization-scoped SCIM, every SCIM group is an organization user group.

The following table lists the organization user group attributes that Snowflake supports:

SCIM Group AttributeSnowflake Group AttributeTypeDescription
idAssigned by SnowflakestringThe immutable, unique identifier of the organization user group. Snowflake doesn’t return this value in the SHOW ORGANIZATION USER GROUPS output.
displayNameNAMEstringThe text shown in the user interface when referring to the group. This property can’t be changed after the group is created. A value that differs only by casing is allowed, but the original value is preserved from creation time. Any other value returns HTTP 400.
members.valueN/AstringThe id of an organization user who is a member of the group. Any other id returns HTTP 400. A group can’t be a member of a group.
schemasN/AstringAn array of strings that indicates the namespace URIs. For example, urn:ietf:params:scim:schemas:core:2.0:Group.

Import adds the group’s users to the regular account and creates a role with the group’s name. See Import the group in a regular account and Resolve conflicts after importing users.

IS_GRANTABLE and VISIBILITY aren’t SCIM-settable attributes. Set IS_GRANTABLE and VISIBILITY with ALTER ORGANIZATION USER GROUP.

Organization user group endpoints

You manage organization user groups through the same SCIM group API endpoints as account-scoped SCIM. See the group API reference. A missing privilege returns HTTP 403. A list or a displayName lookup without MANAGE ORGANIZATION USER GROUPS returns no groups.

The following table lists the privilege that each endpoint checks:

EndpointPrivilege
GET /Groups and GET /Groups?filter=displayName eq "..."MANAGE ORGANIZATION USER GROUPS
GET /Groups/{id}MANAGE ORGANIZATION USER GROUPS
POST /GroupsCREATE ORGANIZATION USER GROUP
PATCH /Groups/{id}MANAGE ORGANIZATION USER GROUPS
DELETE /Groups/{id}MANAGE ORGANIZATION USER GROUPS

GET /Groups returns a page of organization user groups. With MANAGE ORGANIZATION USER GROUPS, the query matches every organization user group in the organization. totalResults is the number of matching organization user groups, including groups that aren’t on this page. This differs from account-scoped SCIM, where totalResults equals startIndex + count when another page is available. See the group API reference.

displayName eq and displayName sw work the same way as in the group API reference. eq matches the value as sent, as well as the uppercased displayName. sw matches the value as sent, and that comparison is case-sensitive. excludedAttributes=members also works the same way as in the group API reference.

DELETE /Groups/{id} drops the organization user group. See Removing users from all regular accounts.