|
To create a user:
Enter the email ID of the new user in the Username field.
Username must be a valid email address. It should meet following requirements:
|
Click Create a project in the default project space if one doesn't exist if you want to create a project for the new user in the projects project space.
The Create project in default project space if one doesn't exist option creates a project named after that user. This project offers a workspace to build and test pipelines without affecting other shared projects in the Org. If your company has already defined multiple Orgs in SnapLogic, and this user exists in another organization or was previously removed, then the existing user is added to the current Org. |
If you plan to use SSO and do not want users to have a separate SnapLogic login, select Disable password-based login. For information on managing password-based logins for existing users, see Manage Password Logins.
To work with the Manage Password Logins popup, you should have enabled SSO in your Org. |
To provide Org admin permissions to the new user, select Provision the new user as the organization's admin.
You can make a user an Org admin at any time by adding that user to the Org admin group. |
To create an account that you want to use to call Triggered Tasks, select Provision the new user as the service account. Credentials for this user are sent to the account creator, as are all reset password emails. You can change a service account into a regular user account by updating the user and deselecting this check box.
|
To prevent the new user from logging into SnapLogic, deselect Allow this user UI Access (selected by default). This setting applies to all Orgs with which the user is associated.
This option is grayed out for service accounts. A regular user without UI access can act as a service account, but the individual user receives password reset emails. |
To encrypt the new user's emails, upload a public key. Currently, only .der and .pem filetypes are accepted. Encrypted emails are locked and can only be unlocked with a private key.
This option is only visible if Email Encryption is enabled in the Org Settings. |