Sharing lets an agent owner give other users access without admin involvement. Pinter supports two sharing methods: Both methods create a grant with one of two privilege levels:

Share directly with a user

Open the agent in the builder and select Share Agent in the canvas header.
1

Open the Direct Share tab

The dialog opens on the Direct Share tab.
2

Enter the recipient

Type the recipient’s exact email or username. Pinter does not offer a user directory to browse, so the identifier must match exactly.
3

Select the privilege

Choose Use Only (Read-Only Builder) or Edit & Co-own (L1/L2 Only).
4

Share

The recipient receives an approved grant immediately.
Backend endpoint:

Share with a claim code

Claim codes let recipients redeem access themselves. Codes use the format PIN-SHR-XXXX-XXXX.
1

Open the claim code tab

In the Share Agent dialog, switch to the claim code tab.
2

Choose the audience

Select Team/Group to let members bind the grant to a role group, or Peer User for individual claims.
3

Set privilege, claims, and expiry

Choose Use Only or Edit & Co-own, the maximum number of claims, and an expiry of 1 hour, 24 hours, 7 days, or never.
4

Copy and distribute the code

Copy the generated code and send it to your recipients.
Backend endpoint:

Redeem a claim code

Recipients redeem codes from the app sidebar.
1

Open the redemption dialog

Select Redeem Claim Code in the sidebar.
2

Enter the code

Type the code in the PIN-SHR-XXXX-XXXX format. Pinter validates the code, its expiry, and the remaining claims.
3

Confirm

Review the agent name and privilege. For team codes, select the target role group before confirming. Confirmation creates an approved grant and decrements the remaining claims.
Backend endpoints:

Sharing Knowledge Hub Documents

Knowledge Hub documents follow a collaborative chat-share pattern:
  • General Access:
    • Restricted (private): Only the owner, L1 admins, and explicitly specified users and role groups can view or use the document.
    • Organization (internal): every user in the same application/organization domain with Knowledge Hub access (L1–L3) can view the document. Only an L1 admin can publish a document this way.
  • Permission Levels (one per recipient, so each person or group can differ):
    • Can view (view): read chunks and search the document, but not download it or attach it to agents.
    • Can view and use (use): adds download and attaching to their own agents.
    • Can manage (manage): adds editing metadata, changing share settings, and deleting the document.
  • Grantee Selection:
    • Direct sharing to individual users or entire user groups.
  • Expiration Controls:
    • Access expiration presets: 1 hour, 24 hours, 7 days, 30 days, or never.
  • Revocation Protection:
    • When restricting permissions from use to view or changing visibility to private, the system alerts the owner if other users’ agents currently have this document attached.
  • Shareable Link:
    • Share link format: /share/d/{documentId} allowing direct inspection of shared document chunks and metadata.
Backend endpoints:

Sharing Knowledge Hub Collections

Collections use the same share dialog as documents (and chat). A collection can be Restricted (private, with explicit users and role groups) or Organization (internal); there is no anonymous public link.
  • Sharing a collection gives recipients view-only access to every document in it. It never grants download or the right to attach documents to agents, even if a document was shared with use permission by its owner.
  • Only the collection creator or an L1/L2 admin can edit or share a collection.
  • Only owners (or L1) can add their documents to a collection, so a collection cannot be used to re-share someone else’s document.
  • Share link format: /share/k/{collectionId} (login required).

See who has access

An agent’s creator can list every active grant on it, including L3 designers who cannot reach the admin mapping view:
Each item’s id is the grant id to pass to the revoke endpoint below. The response also carries is_public — when true, everyone can use the agent regardless of the grants listed, so revoking them will not restrict access. Authorised with the same check as revoking, so anyone who can see a grant here can also revoke it.

Revoke a shared grant

Owners and Super Admins can revoke an existing grant:
An edit grant lets the recipient change the agent for every user who runs it. Prefer use grants unless the recipient co-owns the agent.
Sharing covers owner-driven access. For admin-driven access requests and approvals, see Authentication and access control.