To help your team build and deploy integrations securely without disrupting business-critical workflows, a Celigo account supports a single Production environment alongside one or more non-production environments.
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. To learn what each role can do, see Manage user roles and permissions to an account. To learn about multiple environments, see Multiple environments overview.
Prerequisites: You must be an account owner or have admin access to the Production environment.
Invite users to an account or environment
As an account owner or admin, you can invite users to your account. If you have a Professional or Enterprise subscription with multiple environments, you can invite users to a specific environment (see Multiple environments overview).
Tip: Consider an access policy that keeps your account secure: invite users with specific permissions to specific environments and control access to the Production environment.
-
If you want to invite a user to a specific environment in a multiple environment structure, select the environment from the top of the page.
- Go to Account
, and then select Users.
- Select + Invite user.
- Enter the new user's email address, and then choose their roles & permissions. To invite multiple users with the same role, separate their email addresses with a comma.
- Select Invite.
The user receives an email with a confirmation link that takes them to the sign-in page. If you invite someone who doesn't have a Celigo account yet, the invitation link will direct them to the sign-up page. Once they create their profile, they will automatically have access to your account.
When a user is invited to a specific environment, they're added to that environment's user list with a status of Pending and are treated as an existing user even before they accept. When a user is invited to more than one environment:
- If they accept, they're added to all invited environments and can leave any environment at any time.
- If they decline, they're removed from all invited environments. If they're re-invited to one environment later, they're added only to that environment.
Note: Regional account requirements: Because the regional domains operate entirely independently, anyone requiring access to both a US account (integrator.io) and an EU account (eu.integrator.io) must establish a separate profile within each region.
If the invited user already has a Celigo login
An invited user who fills in the sign-up form with an email address that already has a Celigo login sees "Sign up failed. A user with the given email is already registered." A login can exist from an earlier trial sign-up, from Sign in with Google, or from an earlier invitation the user accepted.
- The user signs in instead of signing up (see Sign in to integrator.io). If they never set a password, they select Forgot password?. If the login was created with Sign in with Google, they sign in with Google.
- Removing a user from the Users list removes their access to your account, not their Celigo login. Removing and re-inviting the same email address doesn’t clear the sign-up refusal.
- After signing in, the user accepts the invitation from Notifications at the top right of integrator.io, or by opening the link in the invitation email while signed in. The user list shows the row as Pending until they accept. A Pending row for someone who has signed in recently means the acceptance step is still missing, not that the email was lost.
- The invitation can’t be accepted while the invited user’s own account still owns integrations or flows, including the free trial’s sample integration. For the full conditions, see Manage user roles & permissions to an account.
Edit access permissions
Change a user's access permissions or remove them from an environment.
-
If you want to edit a user's access to a specific environment in a multiple environment structure, select the environment from the top of the page.
- Go to Account
, and then select Users.
- Select Actions
next to the user, and then select Manage user.
- Change the roles & permissions, and then select Save.
When a user's role changes within one environment, the change applies to all environments the user belongs to. Notifications are sent to the invited user, the admins, and the owner when a user is invited, added, or removed, and when user access changes.
Roles & permissions
The same options appear when you invite a user and when you manage an existing user. For what each role allows, see Manage user roles & permissions to an account.
- Admin — The same permissions as the account owner, except transferring ownership.
- Manage all — View and modify all integrations in the account.
- Monitor all — View all integrations in the account.
- Custom — Access to selected integrations only. Choose them in the Monitor integrations and Manage integrations lists.
- Users can edit retry data — Shown for Monitor all and Custom monitor access. On by default; turn it off to stop the user from editing retry data while fixing errors.
- Allow integration workspace creation — Shown for Monitor all and Custom access. Lets the user create their own integration workspace; their role becomes Custom, with Manage access to anything they create, upload, or clone.
- Security — Require single sign-on or multifactor authentication for this user. MFA applies to anyone who signs in with a password, and you can also require it after SSO when your policy calls for both. See Set up single sign-on (SSO) for an account and Set up and manage MFA for your account.
Note: Only the account owner sees Make account owner under Manage user. See Transfer account ownership to another user.
Invite users to an integration as a non-admin
Users with Manage or Monitor access can invite others to an integration they belong to when an owner or admin has turned on the Invitations setting (see Let non-admins invite users to an integration).
- On the Home page, select the integration.
- Select Users, and then select + Invite user.
- Search for an existing user or enter a new user's email address, and then select Monitor or Manage. To require multifactor authentication for the user, turn it on under Security.
- Select Save.
The user receives an email with a confirmation link. To change the user's access later, select Actions next to them on the integration's Users page, and then select Manage user.
Tip: When you assign a flow step's errors to someone who isn't yet a user of the integration, you can invite them from the Errors list.
Remove users
Remove a user's access to an account or environment.
-
If you want to remove a user's access to a specific environment in a multiple environment structure, select the environment from the top of the page. If you want to remove them from the account, select Production as the environment.
- Go to Account
, and then select Users.
- Select Actions
next to the user, and then select one of the following:
- Remove user from environment - Remove a user from an environment in a multiple environment account.
- Remove user from account - Remove a user from an account that only contains a production environment.
How owners and admins work across environments
Production environment owners and administrators retain unique privileges that extend across your entire account. When a new environment is created, the Production environment owner and admins are automatically assigned the exact same roles within it. However, certain actions remain restricted to the Production environment itself: an owner can only manage security policies for a Production admin from within the Production space, and account ownership transfers must be initiated by the Production owner to another user within that same environment (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 admin of the Production environment. For example, a user can be an Admin in non-production Environment A and a Manage user in non-production Environment B. Access levels can also differ per environment — a user might have Manage access in Production and Monitor access in a Staging environment.
| 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 also lose admin status in all non-production environments. |
| Admin | No | Yes | An admin in a non-production environment isn't granted the admin role in the Production environment. They can be invited to the Production environment as a user with Manage, Monitor, Custom, or Admin access. An admin in a non-production environment can't change the roles or permissions of a Production-environment admin who was automatically granted the same permissions there. |
| User with Manage, Monitor, or Custom permissions | Yes | No | A user with these permissions in the Production environment isn't automatically granted the same access in non-production environments. The owner or admin must invite them to each non-production environment. |
| User with Manage, Monitor, or Custom permissions | No | Yes | A user with these permissions in a non-production environment isn't automatically granted the same access in Production. The owner or admin must invite them to the Production environment. |
Delete your Celigo account
To permanently delete your account and remove all associated data:
- Delete all resources used by any flow or integration in your account.
- Delete all integrations and flows in your account.
- Delete all user profiles and account information.
- Delete any remaining resources.
- Notify Celigo Support of your request to delete your account and remove all associated data.