Structuring Email Addresses for Conga Sign Between Environments
Enable users to effectively manage email addresses for accessing multiple Conga Sign accounts within the same environment type by using email aliases or SSO.
Examples of this Use Case:
Using Email Alias for Multiple Accounts
Scenario: John Smith wants to use his email john.smith@example.com to register a second Conga Sign account.
John confirms he uses Gmail as his email provider.
He creates an alias email, john.smith+business@example.com
He registers the alias with the second Conga Sign account.
He verifies he can access both accounts without conflict.
SSO Configuration for Sub-Accounts
Scenario: An organization with a parent Conga Sign account wants users to access multiple sub-accounts without creating multiple user IDs.
The IT Administrator sets up Single Sign On within the parent account.
Users log in to the parent account using their email.
Once logged in, users use the root menu to navigate to the desired sub-account.
Encountering Aliasing Limitation
Scenario: Emma uses Yahoo email and wants to access two Conga Sign accounts for different projects.
Emma discovers that Yahoo does not support aliasing.
She decides to set up a new email account with Gmail to manage aliases efficiently.
She uses the new Gmail address to create aliases for the second Conga account.