Invite users and manage access to an account or environment

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 guides you through managing user roles and permissions across these environments—ensuring you can maintain strict security governance while keeping your development agile. You will learn which roles propagate automatically, how to handle environment-specific invitations, and what access levels look like in non-production spaces. For the foundational definitions of each role, see Manage user roles & permissions to an account. To learn about multiple environments, see Multiple environments overview.

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).
 

1. 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.
   
2. Go to Account , and then select Users.
3. Select + Invite user.
4. Enter the new user's email address and select their role and permissions. To invite multiple users with the same role, separate their email addresses with a comma.
5. 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.

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.

Edit access permissions

Change a user's access permissions or remove them from an environment.

1. 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.
   
2. Go to Account , and then select Users.
3. Select Actions (...) next to the user, and then select Manage user to modify their permissions.

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.

Remove users

Remove a user's access to an account or environment.

1. 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.
   
2. Go to Account , and then select Users.
3. 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 behave 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.