Team members and 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.

• The Admin role. Other roles can see the team but can’t change it.

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.

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.

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

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.

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.

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.

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.

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

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.