Skilder Logo
Concepts

Workspaces & Roles

How Skilder organizes resources into workspaces with role-based access control, API keys, and team hierarchy.

Everything in Skilder lives inside a workspace — MCP servers, skills, hats, API keys, integrations, and AI provider configs.

Workspace Hierarchy

Members and Roles

Every workspace has members, each with a role that controls what they can do.

RoleCapabilities
AdminFull control. Manage members (invite, remove, change roles), configure MCP servers, create and edit skills, hats, API keys, integrations, and AI provider configs.
EditorCreate and edit skills, hats, and tools. Cannot manage members, API keys, or workspace settings.
ViewerUse the Studio, browse skills and hats, view resources. Cannot modify anything.

Invitations

Admins invite users by email with a role assignment (Admin, Editor, or Viewer).

  • Invitations expire after 7 days.
  • New users create an account when accepting. Existing users are added directly.
  • Admins can revoke pending invitations from workspace member settings.

Core Resources

MCP Servers

Tool providers. Each server exposes one or more tools agents can call. Install from the registry or add custom configs. See Tools.

Skills

Bundle related tools with instructions, scripts, and assets. See Skills.

Hats

Group skills into role-based collections. Assign to API keys to control agent access. See Skills.

Organization Units

Hierarchical team structure (up to 10 levels) for organizing hats by department, team, or function. Manage from Organization Settings on the Hats page.

API Keys

Key TypePrefixScope
Workspace keysWSK_Workspace scope. Created by admins in Workspace Settings > API Keys.
User keysUSK_User scope. Created from Profile > API Keys. Tied to your identity.

Each key grants access through the hats in the workspace.

Integrations

OAuth connections to external services (Google, Microsoft, Zoho). Admins configure the provider; users connect personal accounts. See OAuth Integrations.

AI Provider Configs

Credentials and settings for AI model providers (Anthropic, OpenAI, etc.). See AI Providers.


Profile

Users manage personal settings from the Profile page (avatar menu, top-right):

TabPurpose
ProfileDisplay name and password
API KeysPersonal user keys (USK_)
IntegrationsPersonal OAuth accounts
ConnectDevice and agent connections

How It All Fits Together

API Key → Workspace → Hats → Skills → Tools
  1. Install MCP servers to bring tools into your workspace.
  2. Create skills that bundle the right tools for specific tasks.
  3. Organize skills into hats that represent roles.
  4. Generate API keys and assign hats.
  5. Connect your agent via MCP (STDIO or Streamable HTTP) — it discovers exactly the capabilities defined by its hat.