Skip to main content
These errors come from workspace scope and roles. First check which workspace is selected in the sidebar: its listings and search show only that workspace’s content, filtered by what your signed-in identity can access. If the message tells you to ask an admin and you are not sure which kind, start with Why can’t I do this.

Why can’t I do this

You are refused an action you expected to be allowed, often with a message that says to ask an admin.

Cause

A refusal has one of four causes, and the fix sits with a different person for each:
  • Role. The action needs a role you don’t hold. Organization roles and workspace roles are separate, so an admin of a workspace is not an organization admin, and an organization admin is not a member of every workspace. See Who can do what.
  • Plan. Your organization’s plan doesn’t include the feature. No role change fixes this.
  • App. The app behind the feature is not installed, not approved, not available in this workspace, or has authoring turned off here.
  • Token. You are calling the API with a key or token that can do less than you can when signed in.

Solution

  1. Match the exact text you see in the table. It names which of the four causes applies.
  2. Ask the person in the Who can fix it column to make the change.
A Builder who can’t create a metric or another app’s content is usually hitting one of the app rows, not a role problem: Builders can create wherever the app is in the plan, installed, approved, available in the workspace, and has authoring on. For the full list of app messages, see Install and manage apps.
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. Select Skills in the sidebar 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. Workspace administrators change roles under Settings → Workspaces → Access → Members.
  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. Atlan Trident 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 Skills in the sidebar.

A workspace above this one is invite-only on join

You select Join workspace on a team workspace, and the join fails with “A workspace above this one is invite-only, so you can’t join this one yourself. Ask an admin of this workspace to add you.”

Cause

The workspace allows self-join, so Join workspace appears. But a workspace above it in the hierarchy does not allow self-join, and that closed workspace above is why the join is refused.

Solution

  1. Ask a workspace admin of the workspace you want to add you with the role you need. Joining the workspace above first doesn’t help: it’s the workspace that doesn’t allow self-join.
  2. Once added, open the workspace and confirm you see its skills.

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.

Workspace actions are unavailable

Workspace settings show “You can view these settings. Only workspace admins can change them.” Controls such as editing the profile, Give access, and Archive workspace are disabled.

Cause

The app enables a workspace’s actions only when the server confirms them for your identity. Without a confirmed answer, it keeps them disabled rather than assuming your access.

Solution

  1. Reload the app and open the workspace again. The app reads your access on it and enables the actions the server confirms.
  2. If an action is still disabled, your role does not include it. Ask a workspace administrator to review your grant. Archiving also requires an empty workspace; see Workspace archive blocked.

Workspace archive blocked

Archive workspace is disabled or the archive is refused.

Cause

Archiving requires permission throughout the subtree. Personal and organization root workspaces are protected. The app also prevents archiving a selected workspace that still contains artifacts.

Solution

  1. Find your symptom in the table and follow the action beside it.
  2. Retry the archive after the blocking item is resolved.
Archive content can finish after the workspace itself archives. See Archive workspace.

Visibility change or move is unavailable

A visibility option or a new parent is disabled.

Cause

A workspace cannot be more open than its parent. The move also needs write access to the destination, a legal tree position, and an eligible workspace.

Solution

  1. Read the reason beside the option.
  2. Make open child workspaces private before making their parent private.
  3. Make the workspace private before moving it into a private parent.
  4. For No access, ask the destination’s administrator to review your role.
An archived workspace can’t be changed. You can’t rename it, move it, move another workspace under it, change its visibility, or add or invite members to it, though its contents stay readable. Archive a workspace only when you no longer need to change it.

See also

Need help

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