In the Okta admin console, navigate to Directory > People.
- Welcome to Adobe Acrobat Sign for Government
- First steps for new accounts
- Claiming an email domain
- Connecting Okta to a federated identity solution
- Manually create/edit users in Okta
- First steps for new accounts
- Administrator processes
- Configure your User profile
- Support resources
- Transaction limits
Users can not be created in the Acrobat Sign system until the user domains are claimed and verified.
If users are added to the Okta system prior to the domains being claimed, the Acrobat Sign group must be removed and added again to each impacted user to trigger the user creation process in the Acrobat Sign environment.
Creating individual users in the Acrobat Sign for Government environment manually
The below process creates one user manually in the Okta admin console. Admins will save time and effort by connecting Okta to their directory or SAML 2.0 compliant identity provider and should consider manually creating users one at a time through the Okta console as a method of last resort.
Users are only created in the Acrobat Sign system after the user's profile has been configured in Okta with the Adobe Sign group.
-
Complete the Add Person overlay:
- First name
- Last name
- Username – Must be in the form of an email address,
- Primary email – The functional email address that accepts email for the user.
- Secondary email (optional) – Any functional secondary email that can be used as a backup for the primary.
- Groups – Enter Adobe Sign
-
Scroll to the bottom of the page and enable the Acrobat Sign Roles as needed:
Account Admin – Account level administrators have direct access to configure the account level settings, as well as any group settings as needed. Additionally, account admins have direct access to all users, groups, and agreement data.
Privacy Admin – Provides access to additional tools for an Account level administrator. These tools permit deleting individual users and agreements from the Acrobat Sign system. (e.g., GDPR compliance). All Privacy admins must be account admins.