Joyst

PERMISSIONS & AUDIT TRAIL

Permissions and audit trail for skills, prompts, MCPs, secrets and agents

Enterprise AI governance often stays at the level of policy. Operations teams still need real controls on the items people use: who can view, use or manage a prompt or skill, permissions set in bulk by folder, and a central audit trail. Joyst gives you those controls for your skills, prompts, MCP servers, secrets and agents. It is not a general GRC suite, and it does not do IDP scorecards.

dash.joyst.app
Permissions and audit controls in Joyst admin

ENTERPRISE AI GOVERNANCE

Permissions on AI assets for enterprise AI governance

  • Why permissions matter

    Skills, prompts, MCP servers, secrets and agents change how work gets done. Without permission levels, everyone can edit everything, or nobody can tell who published the live version.

  • Permissions by group and folder

    Set rights on folders and groups, so you are not changing items one by one for every team change.

  • One model for all five

    The same permission model covers skills, prompts, MCP servers, secrets and agents. Governance applies to the items themselves, not only to a policy document.

PERMISSION LEVELS

View, use and manage.

  • View

    See an item and its notes without running or editing it. Useful for reviewers and new starters.

  • Use

    Use approved prompts, skills, MCP servers, secrets and agents without the right to edit or publish.

  • Manage

    Edit, share and publish. Manage stays with owners, so more people can use an item without more people editing it.

  • Groups and folders

    Set view, use and manage rights on folders and groups, so large catalogues stay easy to run.

AUDIT

Central audit trail

  • Who changed what

    See who changed permissions, published items or adjusted sharing levels. You have an answer when operations or security asks.

  • Across all five

    One trail covers skills, prompts, MCP servers, secrets and agents, so governance is not rebuilt for each tool.

  • Covers secrets and MCP servers

    The secrets vault and the private MCP catalogue follow the same organisation controls. Keys and servers do not sit outside them.

  • Beside permissions

    The audit trail sits next to view, use and manage rights. Who can change an item and who did change it stay linked.

RELATED

Keep exploring.

  • Beside your IDP

    How Joyst works beside your IDP.

    Open
  • Prompt management

    A team prompt library with versioning and sharing levels.

    Open
  • Skills registry

    Manage, version and move skills across AI tools.

    Open
  • MCP catalogue

    Connect, document and approve MCP servers.

    Open
  • Secrets vault

    Keys kept out of model context.

    Open
  • Agents

    Package skills, prompts, MCP servers and secrets into reusable setups.

    Open
  • AI governance framework

    Five practical controls, with a checklist.

    Open

Permissions and audit trail FAQ

View, use and manage. You can separate who uses an item from who can edit or publish it.

A central audit trail records relevant changes, so operations and security teams can see who did what.

No. Joyst provides permissions and an audit trail for skills, prompts, MCP servers, secrets and agents. It does not replace a compliance framework.

No. Joyst sits beside developer portals. IDPs catalogue software. Joyst catalogues your AI tools and content.

Yes. Folders and groups let you set rights without changing items one by one.

Start with team permissions, or book an enterprise demo.

Create an organisation account and bring skills, prompts, MCP servers, secrets and agents into one private catalogue.

  • Private to your organisation
  • Draft, then publish
  • Limited open beta
Start free beta