Skip to main content
A Custom Project owner can grant Viewer access through an invitation or share link. Project membership determines who can use its resources; Agent linking determines which Agent can use an accepted Project.

​
Understand viewer access

  • Viewers can read Project Skills and see attached Vault key names.
  • Authorized CLI and Agent runtime paths can resolve the Project’s available Vault values. The dashboard keeps plaintext values hidden.
  • The owner manages the Project’s content, Skills, and Vault data.
  • Global and Agent Projects are personal working spaces; use a Custom Project for sharing.
Share a Project only with someone who should be able to use all its supported resources. Review every attached Vault first. A value hidden in the dashboard remains usable through an authorized runtime read.

​
Invite one person

Open the Custom Project’s Access > Manage sharing, enter the intended account email, and choose Invite. The recipient reviews the invitation in the Notification Center and accepts or declines it. Follow Share a Project for the task steps and expected result. Invite a Viewer contains the CLI alternative. Use Create invite link in the sharing dialog when you intend to distribute access yourself. Treat the active URL as an invitation that can be forwarded. Review Share with a link for CLI creation, acceptance, and secure handling. Revoking a link stops future acceptance through that link. Accepted members retain their membership until you remove it.

​
Use an accepted Project with an Agent

After reviewing the Project, the recipient opens the intended Agent’s Projects section and chooses Link. Confirm the Project appears among that Agent’s linked resources.
The teammate has Viewer membership, and the selected Agent has an explicit Project link. The owner retains control of the source content.
The Agent’s fixed Agent Project remains its default write target. For Connected Agents, use the explicit Skill import workflow to copy a Project Skill to the computer. Availability follows the supported software table.

​
Remove access

Choose the scope that matches your goal: Use Stop sharing for the canonical commands. Afterward, review the member, invitation, and share-link lists and the affected Agent’s Projects to confirm the intended scope. The owner’s Project content remains available to the owner.

​
Review before sharing

  1. Review every Skill and attached Vault; move sensitive resources to a separate Project before inviting someone who should have narrower access.
  2. Use a directed invitation for a known account email.
  3. Label share links so you can identify them later.
  4. Review members, pending invitations, and active links after collaboration ends.
  5. Unlink a Project from any Agent that has finished using it.
Last modified on September 10, 2026