> ## Documentation Index > Fetch the complete documentation index at: https://docs.condense.io/llms.txt > Use this file to discover all available pages before exploring further. # Invite Members > Invite members to a Condense organization and set their roles and environments before they sign up, so they have access the first time they sign in. Use the Members page in Condense Console to create an organization, invite people, and give them the roles and environments they need. ### **Creating an Organization and Becoming Organization Admin** 1. Sign up or create a new organization in Condense Console [https://console.condense.zeliot.in/signUp](https://console.condense.zeliot.in/signUp) ![Condense Console sign-up page](https://mintcdn.com/zeliot/KDEvnCExK8Q07qbD/images/condense/v2.4.0/condense-guide/condense-console/rwKRGO3QthZ6EMqqYblg%252Fblobs%252FJ4wWXaLFahV1z6wLIf9U%252Fimage.png?fit=max\&auto=format\&n=KDEvnCExK8Q07qbD\&q=85\&s=082ba1e94e096adcaa12ad0f7e24ebdf) 2. The creator automatically becomes the **Organization Admin** ![Organization created with the creator as Organization Admin](https://mintcdn.com/zeliot/KDEvnCExK8Q07qbD/images/condense/v2.4.0/condense-guide/condense-console/rwKRGO3QthZ6EMqqYblg%252Fblobs%252Fq27pMxg6KS3bAIGPKWsP%252Fimage.png?fit=max\&auto=format\&n=KDEvnCExK8Q07qbD\&q=85\&s=9de4551c3180375a60d22d086edb923b) 3. Environment(s) can now be linked to the organization ![Linking an environment to the organization](https://mintcdn.com/zeliot/KDEvnCExK8Q07qbD/images/condense/v2.4.0/condense-guide/condense-console/rwKRGO3QthZ6EMqqYblg%252Fblobs%252FHuIV9Fj1r08FHp6MXdKk%252Fimage.png?fit=max\&auto=format\&n=KDEvnCExK8Q07qbD\&q=85\&s=da1b1105ff85e7756119503e94614a3d) ### **Inviting Members** As Organization Admin or Account Admin: 1. Go to **Members** 2. Select **Invite Member** 3. Enter the email addresses, then choose the roles and environments ![Invite Member form](https://mintcdn.com/zeliot/KDEvnCExK8Q07qbD/images/condense/v2.4.0/condense-guide/condense-console/rwKRGO3QthZ6EMqqYblg%252Fblobs%252FfNDim7ZD6nX2yHinn0Y6%252Fimage.png?fit=max\&auto=format\&n=KDEvnCExK8Q07qbD\&q=85\&s=4f5b65f3c9cd7aad943370a44174c858) 4. Send invite Once accepted, the member appears under the organization. ![Members list showing the invited member](https://mintcdn.com/zeliot/KDEvnCExK8Q07qbD/images/condense/v2.4.0/condense-guide/condense-console/rwKRGO3QthZ6EMqqYblg%252Fblobs%252FGl5snN5VMjFtcOtDRUXR%252Fimage.png?fit=max\&auto=format\&n=KDEvnCExK8Q07qbD\&q=85\&s=2e64046d79735dbad32adeecc1038c6e) ### **Inviting Existing Condense Users (New in v2.4.1)** Starting with **Condense v2.4.1**, users who already have a Condense account can be invited to additional organizations using the same email address. When the invitation is accepted: * No new Condense account is created. * The new organization is added to the user's existing account. * Existing organizations remain unchanged. * Roles and permissions are managed independently within each organization. > [!NOTE] > > A single Condense account can belong to multiple organizations while maintaining separate members, environments, workspaces, and permissions for each organization. 5. Select the member and assign one of the Organization-level roles: * Organization Admin * Account Admin * Billing Admin * Environment Admin (for selected environments) * Environment User (for selected environments) ![Role assignment for a member](https://mintcdn.com/zeliot/KDEvnCExK8Q07qbD/images/condense/v2.4.0/condense-guide/condense-console/rwKRGO3QthZ6EMqqYblg%252Fblobs%252FctD33xsfBC7wOLDmZdc5%252Fimage.png?fit=max\&auto=format\&n=KDEvnCExK8Q07qbD\&q=85\&s=88d03c696f9dd66c3d393bc6b752f31f) > [!CAUTION] > > You cannot assign any role to member if there is no Environment is associated to organization ### **Set Up Access Before the Person Signs Up (New in v2.6.0)** Until now, giving a new person access took four steps in a fixed order, and the last three could only start after they signed up: **Invite → Wait for signup → Assign environment → Assign roles** Starting with **Condense v2.6.0**, you choose roles and environments in the same step as the invitation, and you can adjust them while the invitation is still waiting to be accepted: **Invite → Assign roles and environments → Person signs up → Immediate access** #### What you set up before signup What you can choose depends on your own role. | Your role | What you can choose for the invited person | | :- | :- | | **Organization Admin** | Organization roles: Organization Admin, Billing Admin, Account Admin. | | **Account Admin** | Environment roles: Environment Admin, Environment User or Kafka Admin, for the environments you have access to. | | **Environment Admin** (in Condense Core) | Workspace role (Maintainer, Developer or Viewer) and the workspaces the person can work in. | The invited person shows as **Pending** until they accept the invitation and complete signup. #### Invitation rules * You can invite **up to 20 email addresses** in one invitation. * Gmail addresses and work email addresses are accepted. **Temporary email addresses are not.** * If the same combination of email address, role and environment is added more than once, Condense highlights **Already added** in red and does not add it again. #### Where you see a pending invitation | Where | What you see | | :- | :- | | **Condense Console**, Members page | The invitation under **Pending Invites**, with the email, the roles and the assigned environments. | | **Condense Console**, an environment's page | The invitation under **Pending Invites** for that environment. | | **Condense Core**, Members page | The person under **Pending Invites**, showing **No roles assigned** and **No workspaces assigned** until an Environment Admin sets them. | | **Condense Core**, a workspace's page | The person under **Pending Invites** for that workspace. | An Environment Admin sees pending invitations only for the environments they manage. #### What you can change while the invitation is pending | Action | Who can do it | Where | | :- | :- | :- | | Change roles and environments, then **Save Changes** | Account Admin, Organization Admin | Console | | **Resend** the invitation | Account Admin, Organization Admin | Console | | **Cancel** the invitation | Account Admin, Organization Admin | Console | | Set the workspace role and workspaces | Environment Admin | Core | Changes to a pending person's roles are recorded in the Activity Auditor. #### What happens when the person signs up When the person accepts the invitation and signs in, Condense applies the access you prepared: their Console role, their Core environments, and their workspace role. They land on a working environment instead of an empty dashboard, and no one has to be told that they signed up. > [!NOTE] > > Pre-configured access works the same way as access assigned after signup. The same roles and the same limits apply. ### **Assigning Organizational Roles** Organization Admins can assign: * Organization Admin * Account Admin * Billing Admin These roles control access in Condense Console. ### **Assigning Environment Roles** Account Admin can: 1. Select a member 2. Choose **Add to Environment** 3. Select an environment 4. Assign either: * Environment Admin * Environment User This determines the member’s access level inside Condese Core. ### **Manage People from an Environment's Page (New in v2.6.0)** An environment's page in Condense Console lists its people the same way the Members page does, in three tabs: * **Active Members**: people who have signed up and have access to this environment. * **Pending Invites**: people who were invited to this environment and have not signed up yet. * **Revoked Access**: people whose access was revoked. Only Account Admins and Organization Admins can use the actions below. | Tab | Actions | | :- | :- | | **Active Members** | **Edit** (change the person's roles in this environment, at least one role must stay assigned), **Remove Member** | | **Pending Invites** | **Edit**, **Resend Invite**, **Cancel Invite** | | **Revoked Access** | **Restore Member** | #### Remove a member from an environment **Remove Member** takes the person out of **this environment only**. Their roles in other environments and their other mappings stay as they are. To remove someone from the whole organization, use the Members page. #### Restore a member **Restore Member** brings the person back into the organization with **no roles and no environments**. Because they have no environment yet, they do not appear under **Active Members** on an environment's page. They appear under **Active Members** on the Members page, where you can assign their roles and environments again. ### **Assigning Workspace Roles (inside Condense Core)** Only **Environment Admins** do this. It works the same for people who have signed up and for people whose invitation is still pending. For an Environment User: 1. Navigate to **Members** in Condense Core 2. Find the person under **Active Members** or **Pending Invites** 3. Choose **Edit** 4. Select a role: * Maintainer * Developer * Viewer 5. Select one or more workspaces 6. Choose **Save Changes** Both the role and the workspaces are optional. Until you set them, the person shows **No roles assigned** and **No workspaces assigned**. > [!NOTE] > > **Kafka Admin** is chosen in Condense Console when the person is invited, together with their environment role. It is not set in this step. > **Note** The role selected applies to all selected workspaces. Later additions must use the same role. ## **Example Scenario** #### **Setup** **Environments**: Production, Testing **Workspaces**: FleetTracking, ColdChain, Sandbox #### **Team** | Name | Org Role | Environment Role | Workspace Role | | - | - | - | - | | Anita | Organization Admin | Env Admin (Prod, Test) | — | | Bharat | Account Admin | Env User (Prod) | Kafka Admin — FleetTracking | | Divya | — | Env Admin (Test) | Maintainer — Sandbox | | Eshan | — | Env User (Prod) | Developer — FleetTracking, ColdChain | | Farah | — | Env User (Test) | Viewer — Sandbox | #### **User Experience** * **Anita** Full authority across both environments and all workspaces. * **Bharat** Sees Production only. Sees only FleetTracking because of the Kafka Admin role. * **Divya** Sees all workspaces in Testing. Can deploy and manage connectors in Sandbox. * **Eshan** Sees Production. Sees FleetTracking and ColdChain as Developer. * **Farah** Sees Sandbox with read-only access. #### **Behavior** * Environment Admins see and operate across **all workspaces** of their environments * Environment Users only see the workspaces they have a role for * Workspace roles for an Environment User always remain uniform across all selected workspaces ## Capability **Overview** | Capability | Env Admin | Env User (Workspace Role) | | - | :-: | :-: | | Access all Workspaces | ✅ | ❌ | | Access only assigned Workspaces | Not applicable | ✅ | | Create / delete Workspaces | ✅ | ❌ | | Manage Workspace members | ✅ | ❌ | | Deploy connectors | ✅ | Maintainer only | | Develop applications | ✅ | Developer only | | Kafka operations | ✅ | Kafka Admin only | | View everything | ✅ | Viewer only | Condense RBAC provides a structured, predictable access model across three layers: * **Organization Layer** : governs who administers the organization and who can assign access * **Environment Layer** : determines seniority and visibility for operations * **Workspace Layer** : controls fine-grained operational capabilities Environment Admins manage the entire environment and all workspaces. Environment Users gain workspace access only through explicit workspace-role assignments using a consistent role across selected workspaces. This model keeps permissions clear, secure, and scalable, supporting diverse teams collaborating across multiple environments and workspaces. ## Lifecycle Guide ## Lifecycle Guide The following lifecycle illustrates how a user is onboarded into an organization and granted access to Condense resources. ### 1. Create an Organization A new user signs up for Condense and creates an organization. The creator is automatically assigned the **Organization Admin** role. **Outcome:** * Organization created * Organization Admin assigned * Ready to link environments *** ### 2. Link an Environment The Organization Admin links one or more Condense environments to the organization. **Outcome:** * Environment becomes available for member assignment * Environment roles can now be configured *** ### 3. Invite Members The Organization Admin or Account Admin invites users by entering their email address, choosing roles and environments, and sending an invitation. The user receives an invitation email and joins the organization after accepting it. You do not have to wait for them to accept. Steps 4, 5 and 6 can be completed, and changed, while the invitation is **Pending**. **Outcome:** * Invitation sent * Roles and environments assigned, before or after the person accepts *** ### 4. Assign Organization Roles Assign one of the available organization-level roles based on administrative responsibilities. Available roles include: * Organization Admin * Account Admin * Billing Admin **Outcome:** * Administrative permissions configured *** ### 5. Assign Environment Roles Assign users to one or more linked environments. Available roles include: * Environment Admin * Environment User * Kafka Admin **Outcome:** * User gains access to the selected environments *** ### 6. Assign Workspace Roles For Environment Users, assign workspace-level permissions within Condense Core. Available workspace roles include: * Maintainer * Developer * Viewer Workspace roles determine what actions users can perform within their assigned workspaces. **Outcome:** * User receives access to the required workspaces > [!NOTE] > > Roles and environments assigned before signup take effect the first time the person signs in. *** ### 7. Start Working Once all required roles have been assigned, members can: * Access their assigned environments * Open authorized workspaces * Build and deploy pipelines * Manage connectors and transforms (based on role) * Monitor Kafka resources and applications *** ### 8. Ongoing Administration Organization Admins can continue to manage the organization by: * Inviting new members * Updating member roles * Removing members * Linking additional environments * Managing organization settings * Restoring members whose access was revoked Starting with **Condense v2.4.1**, users can also belong to multiple organizations and switch between them without creating separate accounts. Each organization maintains its own members, environments, workspaces, and permissions independently. ## **Frequently Asked Questions (FAQs)** ## Frequently Asked Questions (FAQs) ### Q1: Who can invite members to an organization? Organization Admins and Account Admins can invite members. Organization Admins assign organization-level roles. Account Admins assign environment roles and environments. *** ### Q2: What happens after a member accepts an invitation? Once the invitation is accepted, the member is added to the organization. If you already assigned roles and environments while the invitation was pending, the member has that access on first sign-in. Otherwise, an Organization Admin or Account Admin can assign the appropriate roles after they join. *** ### Q3: Can I invite someone who already has a Condense account? Yes. Starting with **Condense v2.4.1**, existing Condense users can be invited to additional organizations using the same email address. The new organization is added to their existing account without requiring a new registration. *** ### Q4: Can a user belong to multiple organizations? Yes. A single Condense account can belong to multiple organizations. Users can switch between organizations while maintaining separate roles, permissions, environments, and workspaces for each organization. *** ### Q5: Do I need a different email address for each organization? No. The same email address can be used across multiple organizations. Each organization manages access independently. *** ### Q6: Can I assign roles before linking an environment? Organization-level roles can be assigned without an environment. However, **Environment Admin** and **Environment User** roles can only be assigned after at least one environment has been linked to the organization. *** ### Q7: What is the difference between Organization, Environment, and Workspace roles? * **Organization Roles** control administrative access to the Condense Console. * **Environment Roles** determine access to specific Condense environments. * **Workspace Roles** provide fine-grained permissions within individual workspaces in Condense Core. *** ### Q8: What happens if I remove a member from the organization? Removing a member revokes their access to the organization, including all associated environments and workspaces within that organization. Their access to other organizations remains unaffected. *** ### Q9: Can an Environment User access all workspaces? No. Environment Users can only access the workspaces to which they have been explicitly assigned a workspace role. *** ### Q10: Can an Environment Admin access every workspace? Yes. Environment Admins have access to all workspaces within the environments they administer and can manage workspace resources and members. *** ### Q11: Can workspace roles be different across multiple workspaces? For Environment Users, the same workspace role is applied to all workspaces selected during assignment. If additional workspaces are assigned later, they must use the same role. *** ### Q12: Can I change a member's role later? Yes. Organization Admins can update organization roles, environment roles, and workspace assignments at any time, provided they have the necessary permissions. *** ### Q13: What happens if a user belongs to multiple organizations? When signing in, users can switch between organizations using the organization selector. Each organization maintains its own members, environments, workspaces, roles, and permissions independently. *** ### Q14: Is there a limit to the number of members or organizations? The number of members and organizations depends on your Condense subscription and deployment configuration. Contact your Condense administrator or Zeliot Support for details. *** ### Q15: Why can't I assign Environment Roles? Environment roles can only be assigned after an environment has been linked to the organization. If no environments are available, link an environment before assigning **Environment Admin** or **Environment User** roles. *** ### Q16: Can I assign roles before the invited person signs up? Yes. Starting with **Condense v2.6.0**, you choose roles and environments when you send the invitation, and the access is available the first time the person signs in. *** ### Q17: What does the Pending state mean? Pending means the invitation has been sent but the person has not accepted it and completed signup yet. The access you configured is held for them and takes effect when they sign in. *** ### Q18: Can I change or remove access while the invitation is pending? Yes. In Console, an Account Admin or Organization Admin can edit the roles and environments of a pending invitation, resend it, or cancel it. In Core, an Environment Admin can set the person's workspace role and workspaces. Once the person has signed up, they appear under **Active Members** and you manage them from there. *** ### Q19: Where do I see people who have not signed up yet? Under **Pending Invites**, in the Members page and in each environment's page in Condense Console, and in the Members page and each workspace's page in Condense Core. *** ### Q20: Can I remove the last Account Admin? No. The last Account Admin role in an organization cannot be removed. Assign the Account Admin role to another member first. *** ### Q21: What is the difference between removing a member from an environment and from the organization? **Remove Member** on an environment's page removes the person from that environment only, and keeps their other roles and environments. Removing a member from the organization revokes their access to every environment and workspace in that organization. *** ### Q22: What happens to a member I restore? A restored member returns to the organization with no roles and no environments. Assign their roles and environments again from the Members page. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.