Skip to main content
Modern engineering teams build and operate MCP servers collaboratively. Karada provides Team Workspaces with granular Role-Based Access Control (RBAC) to ensure developers, DevOps engineers, and security teams have appropriate access to projects, deployments, secrets, and billing.

​
Workspaces Architecture

A Workspace is an isolated multi-tenant environment containing your projects, custom plugins, and gateway endpoints:
  • Multi-Workspace Membership: Join multiple team or enterprise workspaces with a single user login.
  • Context Switcher: Rapidly switch between personal, staging, and production workspaces from the top navigation bar.
  • Centralized Billing: Subscription tiers and resource limits apply at the workspace level rather than per seat.

​
Role-Based Access Control (RBAC)

Karada enforces strict RBAC to prevent unauthorized secret exposure or unapproved production deployments:
​
Highest Privilege
Owners hold full administrative control. They manage payment methods and subscriptions, invite or remove team members, configure gateway domains, and delete workspaces or projects.
​
High Privilege
Admins can create projects, generate Auto-MCP servers, configure plugins, manage runtime environment variables, and trigger deployments. They cannot modify billing or delete the workspace.
​
Standard Privilege
Members can inspect projects, review generated tool catalogs, and query usage telemetry. They cannot expose raw secret values or trigger unreviewed production rollouts.

​
Inviting Team Members

To add collaborators to your workspace:
  1. Open your Workspace Settings.
  2. Select the Members tab.
  3. Click Invite Member.
  4. Enter your collaborator’s email and assign their role (Admin or Member).
  5. The invitee receives a secure link to join your workspace immediately.