> ## Documentation Index
> Fetch the complete documentation index at: https://platform.atlan.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To act on Atlan objects, use the Atlan MCP server at https://api.atlan.com/mcp or the atlanai CLI; `atlanai --map json` prints its command map. Run a read-only identity check before any write.
> The docs MCP server at /mcp searches these docs only. It cannot read or change Atlan objects.
> SDK packages: Python `atlanai` (PyPI) and TypeScript `@atlanai/sdk` (npm). Show Python first, then TypeScript.

# Workspace access errors

> Fix skills that do not appear, workspaces you cannot join, and skills you cannot add to a team workspace.

These errors come from workspace scope and roles. First check which workspace
is selected in the sidebar: Browse and search show only that workspace's
content, filtered by what your signed-in identity can access.

## Skill does not appear in Browse or search

You expect a skill, but it is missing from the list or search results.

### Cause

What you see comes from your signed-in identity and its workspace
permissions. The skill may belong to a different workspace than the one
selected, to another person's personal workspace, or to a team workspace you
are not a member of. A workspace identifier in a link or request does not grant
access on its own.

### Solution

Find the skill in the right scope, or get access to the workspace that holds
it.

1. Confirm the workspace selected in the sidebar.
2. Open **Browse** in that workspace and search for the skill. Search matches a
   skill's name or description in the current scope.
3. If the skill is in a team workspace you cannot read, open that workspace and
   select **Join workspace** when it is offered. Joining adds you as a
   **Builder**.
4. If **Join workspace** is not shown, ask a workspace admin to add you.
5. Search again. The skill appears in the list.

***

## Move dialog shows "Only admins can add skills"

When you move a skill, the destination workspace is marked **Only admins can
add skills**.

### Cause

Adding a skill to a workspace needs permission to contribute. The
**Viewer** role can view a workspace but cannot make changes.

### Solution

Get a role that can contribute, or choose another workspace.

1. Ask a workspace admin of the destination workspace to change your role to
   **Builder**. Admins change roles on the workspace's **Members** tab.
2. Open the move dialog again. The workspace now shows **You can add skills**.

***

## Join workspace is not available

You cannot find **Join workspace** on a team workspace you need.

### Cause

**Join workspace** appears only when a workspace allows self-join. Agent Registry does
not provide a request-access workflow for other workspaces.

### Solution

Ask for access directly.

1. Ask a workspace admin of that workspace to add you with the role you need.
2. Open the workspace again. Its skills appear under **Browse**.

***

## Teammates cannot see your skill

A skill appears for you, but a teammate cannot find it.

### Cause

Your personal workspace is visible only to you. A skill in a team workspace is
visible only to that workspace's members.

### Solution

Put the skill where your teammate has access.

1. Open the skill and check its workspace. If it is in your personal workspace,
   move it to a team workspace with **Share** → **Move**.
2. If the teammate is not a member of that team workspace, ask a workspace
   admin to add them.
3. Ask the teammate to search for the skill. It appears in their results.

## See also

* [How workspaces work](/registry/workspaces/index): How personal and team workspaces scope skills and access.
* [Workspace roles and access](/administer/workspaces/references/roles-and-access): What each role can do and how joining works.

## Need help

If you need assistance after trying these steps, contact support.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.