A Celigo account has one Production environment and, on Professional and Enterprise editions, one or more non-production environments, and you control who can work in each one. This article is for account owners and administrators. It covers inviting users to an account or to a specific environment, changing and removing access, and how roles carry across environments. For what each role can do, see Manage user roles and permissions to an account. For what environments are, see Multiple environments overview.
Tip: Keep your account secure by inviting users with specific permissions to specific environments and limiting access to Production.
Invite users to an account or environment
- To invite a user to a specific environment, switch to that environment.
- Go to Account
, and then select Users.
- Select Invite user.
- Enter the user's email address, and select their role and permissions. To invite several users with the same role, separate their email addresses with commas.
- Select Invite.
The user receives an email with a confirmation link that takes them to the sign-in page. A user who doesn't have a Celigo account yet is taken to the sign-up page and gets access to your account after creating a profile.
A user invited to a specific environment appears in that environment's user list with the status Pending and is treated as an existing user before they accept. When a user is invited to more than one environment:
- If they accept, they're added to every environment they were invited to and can leave any environment at any time.
- If they decline, they're removed from every environment they were invited to. If they're invited to one environment again later, they're added only to that environment.
Regional accounts: The US (integrator.io) and EU (eu.integrator.io) regions are independent. A user who needs access to accounts in both regions needs a separate profile in each.
Edit a user's access
- To edit a user's access in a specific environment, switch to that environment.
- Go to Account
, and then select Users.
- Select Actions (...) next to the user, and then select Manage user.
When a user's role changes in one environment, the change applies to every environment the user belongs to. The invited user, the administrators, and the owner are notified when a user is invited, added, or removed, and when a user's access changes.
Remove a user
- To remove a user from a specific environment, switch to that environment. To remove them from the whole account, switch to Production.
- Go to Account
, and then select Users.
- Select Actions (...) next to the user, and then select Remove user from environment.
How owners and administrators work across environments
The Production owner and administrators hold privileges across the whole account. When a new environment is created, they're automatically given the same roles in it. Some actions stay in Production: an owner manages a Production administrator's security policies only from Production, and account ownership is transferred by the Production owner to another user in Production. See Transfer account ownership to another user.
How roles work across environments
A user can hold different roles and permissions in different environments, as long as they aren't the owner or an administrator of Production. For example, a user can be an administrator in one non-production environment and a Manage user in another, or have Manage access in Production and Monitor access in a Staging environment.
| User role | Production | Non-production | Notes |
|---|---|---|---|
| Owner | Yes | Yes | The Production owner is automatically the owner of every non-production environment. |
| Administrator | Yes | Yes | A Production administrator is automatically an administrator in every non-production environment. If they're removed from Production or changed to a user, they also lose administrator status in every non-production environment. |
| Administrator | No | Yes | A non-production administrator isn't an administrator in Production. They can be invited to Production as a user with Manage, Monitor, Custom, or Administrator access. They can't change the roles or permissions of a Production administrator who was automatically granted the same permissions in their environment. |
| User with Manage, Monitor, or Custom permissions | Yes | No | Production access isn't carried into non-production environments. The owner or an administrator must invite the user to each non-production environment. |
| User with Manage, Monitor, or Custom permissions | No | Yes | Non-production access isn't carried into Production. The owner or an administrator must invite the user to Production. |