Visibility
Every architecture and skill in Golden Path has a visibility setting that controls who can access it.
Visibility levels
| Level | Who can see it | Who can use it via MCP | Where it appears |
|---|---|---|---|
| Private | Only you | Only you | Your sidebar |
| Team | You + team members | You + team members | Team members' sidebars |
| Public | Everyone | Everyone (read-only) | Marketplace |
Sidebar indicators
Your sidebar shows the visibility and ownership status of each item at a glance:
| Icon | Meaning |
|---|---|
| π Lock (gray) | Private β only you have access |
| π Fork (gray) | Forked β your independent copy of a marketplace item |
| π₯ Users (blue) | Shared β shared with a team or individual users |
| π Globe (green) | Public β visible to everyone |
Your sidebar is organized into three sections per category (Skills and Architectures):
- Owned (top) β items you created or forked. Full read/write access.
- β Starred β public items you bookmarked from the Marketplace. Read-only, auto-updates when the author publishes changes.
- π₯ Shared β items shared via team membership. Access depends on team role.
Private (default)
When you create an architecture or skill, it starts as private. Only you can see it in your sidebar, use it via MCP tools, and edit it. No one else has access.
Team
Share an architecture with a specific team. All members of that team can see it in their sidebar and use its skills via MCP. See Teams for how to set up teams and manage members.
Sharing works at the architecture level β all skills within a shared architecture are accessible to team members.
Public
Public architectures and skills are visible to all Golden Path users through the Marketplace. Users can star them for read-only access or fork them to create an independent copy.
Publishing an architecture makes all its skills visible on the architecture's marketplace detail page. To publish a standalone skill (not tied to an architecture), set its visibility to public separately.
Star vs Fork
| Action | Access | Updates | Editable |
|---|---|---|---|
| Star | Read-only bookmark | Auto-updates when author publishes | No |
| Fork | Full independent copy | No sync with original | Yes |
Publishing
To make an architecture or skill public:
- Open it in the editor
- Go to Settings (gear icon)
- Under Visibility, select Public
The item becomes discoverable in the marketplace immediately.
Unpublishing
Set visibility back to Private or Team at any time. When you unpublish:
- The item is removed from the marketplace
- All stars on the item are removed β users no longer see it in their Starred section
- Existing forks are unaffected β they are independent copies
Visibility and MCP tools
Your MCP API key determines which architectures and skills the server returns:
get_architecture_detailsβ lists your owned + team-shared + starred architecturesselect_architectureβ can activate any architecture you have access to- Architecture skills β only available after selecting an architecture you can access
Public architectures from other users are not included in your MCP tools by default. Star them from the Marketplace first to add them to your tool list.
What's next?
- Marketplace β discover and star public architectures and skills
- Teams β set up team collaboration
- API Keys β manage your MCP authentication