PART 3Keep and share results3.6
Sharing — choose the audience and revoke access
Compare member access, public document and AI context links, HTML shares, and media references; understand live reads, expiry, revocation, and how Project status suspends shares.
Choose what a recipient should be able to read before copying a link. A normal Project URL requires membership. A public share URL grants read access to anyone who possesses it, including an external AI service you paste it into. It does not grant membership or permission to edit or run agents.
Choose a sharing method
| Need | Method and audience | Who manages it / lifetime |
|---|---|---|
| Work together inside the Project | Normal Project/document links; authenticated members and their roles | Manage membership in Projects; a copied URL does not add a member. An unjoined Team member can join from the link with Join and view (Teams) |
| Let an outsider read one deliverable | Public document Markdown link, including supported media referenced by that document | Collaborator/Admin create; creator manages their own document links, Admin all links; UI expiry 7 days |
| Give an external reader broad Project context | Public AI context Markdown link, Project timeline, documents, and Project session transcripts | Admin only; UI expiry 7 days |
| Show an interactive static report | Share HTML, the Project's built HTML surface and its media dependencies; one per Project | Collaborator/Admin; default 7 days, maximum 30, optional generated password, reset or stop |
| Reference an image, video, or PDF internally | Media canonical URL, https://aachat.io/m/<uuid> | Authenticated membership in the owning Project; it is not a public sharing token |
| Invite someone to participate | Project join link | Membership/invitation rules apply; see Projects, not the public read-only share rules |
| Reuse a Project structure or a client entry | Template or connected-repository entry | A separate reuse/start-work flow; see Connected repo |
Publishing a Media asset to a Project does not by itself publish it anonymously. A Markdown or HTML share can expose its authorized media dependencies through that share's delivery path. Review images, PDFs, and video as well as text before sharing.
Creating and managing Markdown shares and Share HTML requires an active Project. Markdown shares are available in ordinary Projects and DMs.
Share one document
- In an active Project where you are Collaborator or Admin, open the saved document in Docs. Check the entire current body, frontmatter, and referenced media.
- Select Create public document link (the globe button). Read the confirmation (Create public document link?) and select Create and copy public link.
- When "Public document link copied. Read-only, expires in 7 days." appears, paste the copied URL into the intended reader or external AI tool. The URL has the form shown below; use the returned URL as-is rather than constructing it.
- Open the link in a signed-out browser to check the recipient's view. It returns read-only Markdown, not the full document editor. WikiLinks and structured blocks do not grant access to other documents or execute work.
https://aachat.io/share/<token>/docs/<kind>/<id>.mdA document share is bound to that document, not to every document linked from it. It cannot read Project context or session transcripts. Supported references to ready Project Media in its current content can be delivered through the share. Removing a current media reference removes that dependency's authorization through this share.
Share Project context with an external AI
An Admin can use Create public AI context link in the Project header, review the warning (Create public AI context link?), and select Create and copy public link. The returned URL ends in /context.md. Read it and follow its document, session, and pagination links before deciding that its scope is appropriate.
This is broad Project read access, not a hand-picked set of documents. The context surface contains Project timeline records and a document catalog, and the token permits reading documents and session transcripts in that Project. Older records are available through pagination. Do not assume that only links visible on the first page define the token's authority. Referenced ready media may also be exposed. A single-document share is the narrower choice for a finished report.
Both Markdown share types perform a live read. Later edits are visible through an existing token, and a context token can reach later Project records. The link is not a frozen export of what you reviewed at creation. Keep future confidential work outside a shared scope, or revoke the link before adding it.
Expiry, listing, and revocation
The WebUI creates Markdown shares for 7 days and has no expiry picker. The create API accepts expires_in_days from 1 to 30, default 7; this does not imply an expiry editor or renewal button in the UI. Markdown shares do not have the HTML share's password/reset/extend controls.
Open Project Settings → Access → Public shares to inspect active links by scope (Project context / Single document) and expiry. Collaborators can see and revoke only document shares they created. Admins can see and revoke all active document and context shares. Viewers do not see the list and cannot create or manage shares. Select Revoke, then confirm Revoke in Revoke Markdown share?; the URL stops authorizing subsequent reads.
Existing URLs cannot be copied again from the list because raw tokens are not stored. If the URL is lost or clipboard copying fails after creation, inspect the active list, revoke the unwanted link, and create a new one. Repeated creation produces separate links; it does not replace the old token.
A revoked or expired token cannot be used to read the share. Revocation cannot retrieve a recipient's downloaded copy or remove content already sent to another service.
Project status and sharing
Markdown shares can be read only while the Project is active.
- Done (completed): existing Markdown shares stop being readable but are not revoked. If the Project returns to active, links that are unexpired and not revoked become readable again. While Done you also cannot list, create, or revoke them; Public shares shows "Markdown shares are unavailable for archived projects." To stop exposure for certain, revoke links before marking the Project Done.
- Archive: when Archive starts, all of the Project's Markdown shares are revoked and its HTML share is removed. Returning to active does not restore them; create new ones if needed.
- Deleting or deleted: not readable.
Members can open Done / Archived Projects read-only (Permissions), but that does not resume access for external readers.
If sharing fails
- A missing or disabled action: check that you are in an active Project and have the required role. Use a document share as Collaborator; context creation requires Admin.
- A reader sees
# Not found: check expiry and revocation in Public shares, Project status (active and not being archived), whether the document still exists, and whether the URL is exact. The share path returns not found for every reason without distinguishing them. A document token cannot be repurposed for context, another document, or a session URL. - Revocation returns "Markdown share not found or cannot be revoked by your account.": the share is already revoked or expired, or you did not create it. Reload Public shares and choose a listed active share. Ask an Admin to revoke another person's share or a context share.
- A media reference fails: check that the current shared content still references a ready asset. Do not paste a short-lived signed storage URL as a workaround.
- The audience needs to edit or operate agents: use Project membership. Public read-only shares cannot provide those permissions.
For where data is stored and where HTML JavaScript executes, see Trust boundary.