Personal Workspaces

Personal Workspaces give every organization member a private, organization-managed place to create individualized skills. LocalSkills provisions the folder and access grant automatically; integrations target the semantic personal destination instead of managing folder paths or per-user onboarding automation.

Enable and provision

An owner or administrator opens Organization > Personal Workspaces, chooses a namespace such as individuals, and enables the feature. Existing members are backfilled. Every later membership automatically creates a durable provisioning request.

Each member workspace is a restricted child of the managed namespace with a direct editor grant for that member. Grants never exceed organization-role permissions, so a read-only member remains read-only.

Publish to your workspace

The dashboard exposes My personal workspace. The CLI and MCP use the same semantic destination:

localskills publish ./my-skill --personal

create_skill({
  name: "My Skill",
  content: "...",
  tenantId: "org-id",
  destination: "personal"
})

Personal publications are always private. Responses include the physical folderId, but callers should keep using the personal destination for future creates.

Find personal skills

MCP callers use search_skills with scope: "personal". This keeps discovery in the existing search tool while making the security boundary explicit. The CLI exposes the equivalent filter through localskills list --personal.

Membership and lifecycle behavior

• Joining an enabled organization schedules provisioning atomically.
• Removing a member makes their binding inert; content is retained.
• Rejoining reuses the existing workspace when it remains valid.
• Changing the namespace path preserves child folder and skill IDs.
• Administrators can inspect pending, failed, active, and former-member workspaces.

See Folders & Access Control for the underlying restriction model and MCP Server for complete tool schemas.