Creating a User

In this article

Overview

You can create a user in your Org in SnapLogic Manager. The user receives a sign-up email, in which the user clicks the sign-up link, and then is prompted to change the automatically generated password.

See User and Group APIs for information on creating users programmatically.


Prerequisites

  • You must be an Org admin to create users.

Steps

  1. Click Users in SnapLogic Manager.

  2. Click the  icon at the right of the Users screen. The User dialog box appears:


  3. Enter the email ID of the new user in the Username field.

    Username must be a valid email address and must meet the following requirements:

    • It must start with a letter, number, or one of the following special characters: !#$%&'*+/=?^_`{|}~-

    • The name part of the email address (before @) can contain one or more periods. The period must be followed by a letter, number, or one of the following special characters: !#$%&'*+/=?^_`{|}~-

    • The domain name (after @):
      • Must begin with a letter or number.
      • Can contain a hyphen. The hyphen must be followed by a letter or a number.
      • Must contain at least one period.
      • Must end in an extension that contains at least two characters.
  4. 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 space.

    This option creates a project name that reflects the user name. The 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.

  5. Click Add. If this is a new user, the dialog box expands to display additional fields where you must specify details associated with the user.


  6. Enter the First name and Last name of the new user.

  7. Select the Send notification emails option to send a welcome email when the user is created. In general, if you use Single Sign On (SSO) to log in to SnapLogic, you can disable this setting. If you are not using SSO and this option is disabled, the Org administrator is responsible for providing account information to the new user, since the welcome email contains the user's login information.

  8. 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 dialog box, you should have enabled SSO in your Org.

  9. To provide Org admin permissions to the new user, select Provision the new user as the organization's Administrator.

    Making a user an Org admin

    You can make a user an Org administrator by adding that user to the Org administrators group.

  10. To create an account to call Triggered Tasks, select Provision this new user as a 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.

    • Service accounts require permissions on a project or group basis, like regular user accounts. These accounts, however, cannot access Designer or Manager, and can only run Triggered Tasks with basic authentication.
    • The user that creates a service account will receive the welcome email for that service account. If you need to associate the service account to another administrator, contact support@snaplogic.com.
  11. To prevent the new user from logging into SnapLogic, deselect Allow this user UI Access (selected by default). This setting applies to all Orgs to 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.

  12. To encrypt the new user's emails, upload a public key. Currently, only .der and .pem file types 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. 

  13. Click Create to complete adding the user to the Org.

See Also