Personal and shared workspaces
Atlan Trident creates one personal workspace for you. It has no member list: nobody else can join it, no API key can be added to it, and you can neither leave nor archive it. You can’t create workspaces inside it.
A shared workspace gives a team a stable home. Its members see the same skills, and their role decides what they can do. Viewers see the workspace without changing it, builders use and contribute to it, and workspace admins also manage its members and settings. See Workspace roles and access for each action.
Visibility
Each shared workspace has a visibility that decides who can find it:
A workspace’s admins can change its visibility in the workspace’s settings. Some workspaces, such as your personal one, have a fixed visibility.
In the workspace switcher, a shared workspace whose visibility is Invited members only shows a padlock after its name; workspaces open to the organization are not marked.
Workspace hierarchy
Shared workspaces can be nested through their Parent workspace setting. A parent can stand for a department or program, with a child workspace for each team that needs its own owner, members, or access boundary. For example, an Engineering workspace can contain Platform and Developer Experience workspaces. A child is never more open than its parent. A new child starts with its parent’s visibility, and a child of an Invited members only workspace can’t be opened to the whole organization. If any workspace above a child is invite-only, Join workspace on the child is refused, and a workspace admin must add you. Any member of your organization can create a shared workspace and becomes its first workspace admin. Changing a workspace’s hierarchy and managing its members are workspace admin actions. See Workspaces.Projects
Workspaces also hold projects. A project gathers the skills, agents, and sources for one piece of work, so sessions in the project start with that context. Your role in its workspace decides what you can do in the project, and someone with the Builder role on the project itself — a project builder — can create, link, and relate artifacts in the project. See How projects work.How skills reach your personal workspace
Atlan Trident Desktop imports the skills installed for your coding agents into your personal workspace:- Claude Code skills in
~/.claude/skills - Codex skills in
~/.codex/skills, or under$CODEX_HOMEwhen you set it - Shared agent skills in
~/.agents/skills
Example
A developer drafts arelease-notes skill in ~/.claude/skills. Atlan Trident Desktop imports it into their personal workspace, where only they can see it. Once the Platform team starts using it, the developer publishes it to the Platform workspace. Platform’s members can now find it, and its builders can update it. The source record still shows it started on that developer’s computer.
What workspaces do not do
- Selecting a workspace does not grant access. Atlan Trident checks your signed-in identity and your role in the workspace before it shows or changes anything. Knowing a workspace’s ID is not enough.
- A workspace does not group skills by source. A Platform workspace can hold a skill synced from GitHub and one published from the CLI. Each keeps its own source.
- A personal workspace is not reachable by automation. API keys can’t be added to it. Publish what CI or a service account needs into a shared workspace.
- A child workspace is not a copy of its parent. It has its own members and access. Add one only when a team needs that boundary.
See also
- Choose where skills live: Pick personal or shared scope, publish, and confirm the right people can find the skill.
- How workspace home works: Find a workspace’s skills, members, activity, and usage.
- Workspace access errors: Fix skills that don’t appear and workspaces you can’t join.