---
title: "Personal Workspaces"
description: "Managed private workspaces provisioned automatically for every organization member."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.localskills.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# 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

> **Note**
>
> Personal Workspaces are rolling out to selected organizations. If the page
> below is not in your Organization tabs, the feature is not yet available for
> your organization. Contact support to be included.

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.

> **Note**
>
> The namespace and member workspaces are managed objects. Rename or move the
> namespace, retry provisioning, and repair access from the Personal Workspaces
> page—not from generic folder controls.

## Publish to your workspace

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

```sh
localskills publish ./my-skill --personal
```

```js
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](/folders) for the underlying restriction model
and [MCP Server](/mcp) for complete tool schemas.

Source: https://docs.localskills.sh/personal-workspaces/index.mdx