Provision Users
Batch-creates or syncs users. New users are created with the given role and locations. Existing users (matched by email, case-insensitive) have their role corrected if it differs and locations updated per location_mode; re-provisioning does not change an existing membership’s status (a Pending/Deactivated user stays that way). Validation runs for the whole batch before any row is written; a bad role_id or location_id fails only that row, reported in errors. An email that appears more than once in the same batch fails every row that shares it, not just the extras.
hasPermission/hasFeature gate of its own — any valid client key can provision users into its own workspace. Pre-provisioning a user here with a role and locations before their first SSO login means they land in that role and those locations instead of the workspace’s bare default SSO role. See the Single Sign-On guide.role_id/location_ids values? See Get Roles and Get Locations.Pending or Deactivated user stays that way. It also doesn’t bypass your workspace’s user-seat limit: if provisioning a new user would exceed it, that row fails in errors.Authorizations
Client API key for authentication
Client secret for authentication