> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended**:
> ```bash
> npx @scalekit-inc/cli setup
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Team members and roles

Invite teammates to your Scalekit workspace, give them the Admin, Developer, Member or No Access role, override a role per environment, or create custom roles.
Invite your team to the Scalekit dashboard and give each person a role that matches their work. A role applies to every environment in the workspace unless you override it for one environment.

## Before you start

- The **Admin** role. Other roles can see the team but can't change it.

## Roles

| Role | For |
| --- | --- |
| **Admin** | Full access to everything, including members, roles and billing. |
| **Developer** | Build and configure AgentKit. Can't manage members, roles or billing. |
| **Member** | Read-only access to settings and logs. |
| **No Access** | Can't open the dashboard. Use it to suspend someone without removing them. |

What each role can do in AgentKit:

| Area | Admin | Developer | Member |
| --- | --- | --- | --- |
| Connections: view | Yes | Yes | Yes |
| Connections: create and edit | Yes | Yes | No |
| Run tools in the **Playground** | Yes | No | No |
| Connected accounts: view and create | Yes | Yes | No |
| Connected accounts: view credentials and revoke | Yes | No | No |
| API credentials: view, generate and delete secrets | Yes | Yes | No |
| Tool call logs | Yes | Yes | Yes |
| Webhooks: view | Yes | Yes | Yes |
| Webhooks: create and edit | Yes | Yes | No |
| Environments: create | Yes | No | No |
| Environments: rename | Yes | Yes | No |
| Billing | Yes | No | No |
| Team, roles and environment access: view | Yes | Yes | Yes |
| Team, roles and environment access: change | Yes | No | No |

**No Access** can do none of these.

## Invite a teammate

1. Open **Workspace** > **Team Members** and select **Invite**.

2. Enter their **Email**, choose a **Role**, and select **Invite**.

The person appears in **Team Members** with the role you chose.

## Change a role

In **Team Members**, open the member's menu and select **Edit role**. Choose a new **Workspace role** and select **Save**.

### Give a different role in one environment

Under **Environment access** in the same drawer, select **Set override** next to an environment and choose the role for that environment only. For example, make someone an Admin in Development and a Member in Production. **Reset to Default** removes the override.

## Remove a teammate

In **Team Members**, open the member's menu, select **Remove Member**, and confirm with **Delete**. To block access but keep the person's record, give them **No Access** instead.

## Create a custom role

When the four roles don't fit, open **Workspace** > **Roles** and select **Create role**. Give it a **Role name** and **Description**, then choose its **Permissions**, or start from a preset such as **Support** or **Billing Owner**. You can only grant permissions your own role has.

Custom roles appear in the **Role** list when you invite or edit a member.

## Check it worked

Ask the teammate to sign in. They see only the pages their role allows: for example, a Member doesn't see **API Credentials**, and a Developer doesn't see **Billing**.

## Common problems

### I don't see **Invite** or **Edit role**

Your role can't change the team. Ask an Admin.

### A Developer can't run a tool in the Playground

Running tools uses a user's live credentials, so only Admins can. Give the person the Admin role in a Development environment with an environment override, or create a custom role that includes it.

## Next

  - [Environments and regions](/agentkit/environments/): Development and Production, and how to create Production.
  - [Security and compliance](/agentkit/security/): What Scalekit protects, and what your app is responsible for.


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |