Skip to end of banner
Go to start of banner

Managing SnapLogic Users

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 30 Next »

SnapLogic provides these user roles:

  • System Administrators (SysAdmins). Users in the root Org (/), including SnapLogic Support Engineers. To designate a user as a System Administrator, contact support@snaplogic.com.
    • Provisioners. SysAdmins who enable applications for Orgs and create new Orgs.
    • Read-only SysAdmins. SysAdmins who can view everything in every Org but cannot create or modify any Org or asset unless they have additional permissions for a specific Org.
  • Org Administrators. Users in a specific Org who manage that Org. Within the Developer Portal, an Org Administrator can configure the portal, publish or deprecate APIs, and approve subscriptions and accounts. To designate a new user as an Org Administrator, enable Provision the new user as the organization's Administrator when creating the user account.
  • Regular user. All other users in a specific Org. Within their Org, they can create projects and work with assets in a limited capacity.


Only Org administrators can manage users.

The Users screen in SnapLogic Manager enables you to manage your user's permissions and access. 

The above table displays a list of all the users in your Org, along with the corresponding subscription to SnapLogic Intelligent Integration Platform (IIP) or Flows.

Use this page to perform the following tasks:


De-provisioned Users and Orphan Service Accounts

As part of the SnapLogic off-boarding process, we remove the employee's account from the SnapLogic Org and de-provision the associated assets across your Orgs, resulting in the following scenarios:

  • For each Org the de-provisioned user was a member, an orphan service account is created, and the user's assets are transferred to this account. The new Org administrator inherits the assets in the orphan service account.
  • Deleting the orphan service account transfers all of the assets associated with the orphan accounts to the respective new Org administrator. 
  • If the orphan account is not removed from the Org, any other de-provisioned user's assets from this Org become associated with the same orphan service account. When multiple users are de-provisioned in the same Org, their assets are transferred to the same orphan service account. One orphan service account is created for each affected Org.

See Also

  • No labels