Your Two Paths to Access: When Admins Must Create Users, and When They Just Must Activate Them
Prerequisite: Understanding User Provisioning in Receive
Regardless of your chosen Identity Provider (IdP) (Google, Microsoft 365, Okta, etc.), user access to Receive is handled by one of two provisioning methods. Understanding which one you are using is critical to successfully onboarding new users.
Option 1: Authentication Only (SSO without Directory Sync)
This method is used when the system is connected to your IdP for login verification, but not for automatically managing the user list.
-
User Account Creation: The Receive Admin is fully responsible for creating the user's account manually within the Receive platform.
-
Activation Requirement: The admin must manually define the user's Role and Locations (Scope) within the Receive platform before the user can successfully log in.
-
Summary: User creation and permissions are a manual, two-step process in Receive.
Option 2: SSO with Directory Sync (e.g., SCIM Provisioning)
This method is used when the IdP/Directory automatically synchronizes user accounts into Receive, but still requires an admin step to grant access.
-
User Account Creation: User accounts are automatically synced from your IdP into the dedicated User Sync section of Receive.
-
Activation Requirement: The synced users will appear in the User Sync section, but they are inactive. The Receive Admin must review the synced user and manually apply the Role and Locations (Scope) to activate the account.
-
Summary: User creation is automated, but the activation and permission assignment remain a manual step for the admin.