A Celigo platform account supports multiple environments: production and non-production environments. The roles and permissions of account users across environments are explained below.
Owner: An owner has full access to all environments and can invite users, create integrations, and manage resources, including adding, modifying, and removing them in both production and non-production environments. An owner can enable security for an admin of the production environment, but only from within that specific environment.
Transfer of account ownership: The owner of the production environment may transfer ownership of the account to a user in the production environment only. When the owner of an account transfers ownership to a user in the production environment, the current owner will lose ownership in all environments, but retain manage-all access in the production environment. The new owner will gain ownership to all environments. For more information, see Switch account ownership to another user.
Admin: An admin has the same permissions as the owner, except that the admin cannot change the permissions of the owner and cannot transfer ownership of the account.
Tip
When any new non-production environments are created in the account, the owner and admin of the production environment are automatically added to the user list of these environments with the same roles.
Users: A user can have multiple roles and permissions across environments and integrations in the platform, provided the user is not the owner or administrator of the production environment. For example, a user with the "Admin" role in a non-production Environment A can also be a "Manage all" user in another non-production Environment B.
Given below is how user roles work across multiple environments.
|
User role |
Production environment |
Non-production environment |
Notes |
|
Owner |
Yes |
Yes |
An owner in the production environment is automatically granted ownership in non-production environments. |
|
Admin |
Yes |
Yes |
An admin in the production environment is automatically granted the admin role in non-production environments. If an admin is removed from the production environment or their role is changed to a user, they will also lose their admin status in all non-production environments. |
|
Admin |
No |
Yes |
An admin in a non-production environment is not granted the admin role in the production environment. But, the admin can be invited to the production environment as a user with Manage/Monitor/Custom/Admin access. An admin assigned to a non-production environment cannot modify the roles and permissions of an admin from a production environment, who was automatically granted the same permissions in the non-production environment. |
|
User with Manage/Monitor/Custom permissions |
Yes |
No |
A user with any of these permissions in the production environment is not automatically granted the same access in non-production environments. They must be invited by the owner or admin to the non-production environment. |
|
User with Manage/Monitor/Custom permissions |
No |
Yes |
A user with any of these permissions in the non-production environment is not automatically granted the same access in production. They must be invited by the owner or admin to the production environment. |
For more information, see also Manage account and integration permissions.
Tip
Consider creating an access policy to keep your account secure. Based on the policy, invite users with specific permissions to environments and control access, as required, to the production environment. For more information, see "Account Management" in Security guidelines for integrator.io.
An owner or admin should invite new users to an environment in the Celigo platform account. New users will receive an invitation link via email to access the environment for the first time.
-
If a user is new to the Celigo platform, they must click the invitation link and sign up to create their account.
-
If the user has already signed up and created an account in the Celigo platform (for example, a free trial user), they can click the invitation link and sign in to the new account using their credentials.
In the case of a TPP account (Partner) where a user can be part of multiple Celigo platform accounts, each having production and non-production environments, the user will receive invitations when invited to an environment in a new account.
-
When a user is invited to an environment, the details are added in the user list of that environment. The user is now considered an existing user, even if the user has not yet accepted the invitation, and the status shows as Pending.
-
When a user is invited to more than one environment, then
-
if the user accepts the invitation, they will be added to all the invited environments. They can choose to leave an environment at any time.
-
if the user declines the invitation, they will be removed from all the invited environments. If they are re-invited to an environment, they will only be added to the invited environment.
-
-
When a user's role is changed within an environment, the change applies to all environments the user is a part of.
Typically, when a user is invited, added, or removed in an environment or a stack, notifications are sent to the invited user, admins, and the owner of the environment. Likewise, any change in user access is also notified. The owner and admin are notified when integrator.io API tokens are created or deleted.