Skip to main content
Artifact links require authentication to your Runlayer organization. Recipients also need permission to view the artifact; copying a link does not grant access.

​
Share an artifact

  1. Open the artifact and select Share.
  2. Add people, groups, teams, or roles from your organization.
  3. Choose the appropriate permission, then copy the link from the sharing panel.
Replacing or editing file content through Runlayer MCP still requires ownership of the standalone artifact. See Create and update. Under General access, owners and admins can choose Everyone at [organization name] to share with the organization, or Only people invited to limit direct access to invited recipients. Organization-wide access still requires sign-in. Give an artifact a readable address such as https://<your-runlayer-host>/artifacts/kpi-dashboard. Open the artifact, select ⋯ → Custom link, and type a name. Letters are lowercased and spaces or symbols become hyphens, so “KPI Dashboard” saves as kpi-dashboard. Assistants and agents can set one through Runlayer MCP with set_artifact_alias; it accepts only lowercase letters, numbers, and single hyphens.
  • Each custom link is unique within your organization.
  • The artifact’s original link keeps working, and Copy link in the sharing panel hands out the custom link.
  • A custom link grants no access: recipients still need permission to view the artifact.
  • Renaming or removing a custom link frees the old address. Links that used it no longer open this artifact, and they open another artifact if someone later gives it that custom link.

​
Access inherited from an agent

For agent-created artifacts, the originating agent’s Artifact sharing setting also grants access. Open Artifact sharing settings on the agent’s detail page to review it. The artifact creator retains ownership, and administrators with Manage Agents can manage artifacts. Direct artifact shares can grant access in addition to the agent’s setting.
Access is cumulative. Removing a direct invitation does not revoke access someone still has through a group, team, role, organization-wide share, or the originating agent. Review those sources when restricting an artifact.
An artifact your own assistant creates through Runlayer MCP has no originating agent, so its access does not inherit an agent’s sharing setting. When a Runlayer Agent creates an artifact through Runlayer MCP, that agent is the originating agent.

​
Sharing outside your organization

Artifact sharing currently supports authenticated members of your Runlayer organization. It does not provide anonymous public links or access for external stakeholders simply by sending them a URL.
  • Check that they are signed in to the correct Runlayer organization.
  • Review the artifact’s Share panel and, for an agent artifact, the originating agent’s sharing settings.
  • Ask an administrator to check that the recipient has Use Agents or Manage Agents access.
  • Confirm the artifact has not been deleted.
See Roles & Permissions for workspace permissions.