> ## Documentation Index
> Fetch the complete documentation index at: https://grandcentral.backbase.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Manage your team
> Invite members, set roles, and control runtime access for your Grand Central installation.
Team management lets you control who can access your installation and what they can do. You invite people, assign them a role, and give them access to the runtimes they need. Team management is available to members with the **Admin** role.
## How your team gets access
Access to your installation grows from a single starting point:
* The Grand Central team sets up the first **Admin** for your installation. This one-time step is the only invitation that Grand Central handles.
* After that, your admins invite the rest of the team from the console. You don't contact Grand Central to add more people.
To keep access controlled, invitations for people who are new to Grand Central use a two-admin flow: one admin sends the invitation, and a second admin approves it. For more information, see [Invite a member](#invite-a-member) and [Approve or reject a pending invitation](#approve-or-reject-a-pending-invitation).
To join an installation that's already set up, ask an **Admin** on your team to invite you. An admin adds new members, not the Grand Central team.
## Open team management
To manage your team, go to **Settings** and open the **Team members** tab. The tab lists everyone in your installation, along with their role and status.
The member list shows the following columns:
| Column | Description |
| :------ | :----------------------------------------------------- |
| Name | The member's name. |
| Email | The email address the member signs in with. |
| Role | The member's role in your installation. |
| Status | Whether the member is active, invited, or deactivated. |
| Actions | Options to manage the member. |
## Roles
A role controls what a member can do. The following table describes the roles.
| Role | What the member can do |
| :----------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **GC Admin** | The highest-level role. In addition to team management, a GC Admin manages the connector pack catalog, such as creating, versioning, and releasing packs. |
| **Admin** | Manages team members and runtime access within your installation. |
| **Viewer** | Views the dashboard, connector health, and marketplace without making changes. |
## Invite a member
To add someone to your installation, invite them by email. Members with the **Admin** role can send invitations.
Go to **Settings** and open the **Team members** tab.
Select **Invite member**.
Enter the person's email address, choose a role, and add an optional message.
Send the invitation. What happens next depends on whether the person already has an active Grand Central account.
What happens after you send an invitation depends on the person you invited:
* If the person already has an active Grand Central account, such as an internal user or a guest who accepted an earlier invitation, they're added right away with the role you chose. No approval and no email are needed.
* If the person is new to Grand Central, or was invited before but hasn't accepted yet, the invitation waits for a second admin to approve it. No email is sent until the invitation is approved.
You can't approve your own invitation. A different admin must approve invitations for people who are new to Grand Central. This keeps a second person in the loop before access is granted.
## Approve or reject a pending invitation
Invitations that are waiting for approval appear in the **Pending invitations** section of the **Team members** tab, with the status **Pending approval**. Any admin except the one who sent the invitation can act on it.
* To approve an invitation, select **Approve**. Grand Central sends the invitation email and grants the role. The person then accepts the email and signs in.
* To decline an invitation, select **Reject**. No email is sent.
* To withdraw an invitation you sent yourself, select **Cancel invitation**.
If a member hasn't accepted their emailed invitation yet, you can select **Resend invitation** from the member's actions.
## Member statuses
A member's status tells you where they are in the access process. The following table describes the statuses.
| Status | Meaning |
| :------------------- | :---------------------------------------------------------- |
| **Active** | The member has accepted and can sign in. |
| **Invited** | The member has an invitation email but hasn't accepted yet. |
| **Pending approval** | The invitation is waiting for a second admin to approve it. |
| **Deactivated** | The member no longer has access. |
## Assign runtime access
Members see only the runtimes they're assigned to. To give a member access to a specific environment, assign them to that runtime from the member's actions. To remove access, unassign them from the runtime.
If a member reports that a runtime is missing after they sign in, check their runtime assignments first. A missing assignment is the most common cause.
## Next steps
Return to the Grand Central console overview.
