// Guide

Sharing and access

Before sharing a document, decide who should be able to read it and whether people outside the workspace should have a public link.

Open the document’s sharing control.
Inspect its owner and current access.
Choose workspace access for material the team should read, or private access for a restricted item. A private document shows a small lock on the icon beside its title at the top of its page.
For a private document, add the permitted workspace members in Add or invite under Who has access when you own the document. On a document everyone at the company can open, a member already has access and the field says so.
Copy the document link and send it to the intended reader.

When you add a member to a private document or folder, that member gets an item in their Inbox that says you shared a document or a folder with them. The item names you and the document or folder, and it opens that item. ArtifactBridge sends no email for this. If the member could already open the item, for example through its folder, no new Inbox item appears. The Inbox item goes away when the member can no longer open the item. See shared items in the Inbox.

Copying a link does not add someone to the workspace or grant private-item access. The owner manages document access. A workspace administrator is not automatically the owner of every private document.

Invite someone who is not in the workspace

The same field accepts a full email address. If you own the document or folder, choose Invite to send that person a company invitation from it. The person appears under Who has access as Invited · pending until they accept, with Resend and Revoke in place. Nothing is shared before acceptance. Revoking here cancels the person’s whole company invitation, not only this item. See Invite from a document or folder for what the person gets when they accept.

Part of a name or email also finds people who are invited but have not joined yet. The field shows only the invitations you can see: your own, or every invitation when you are the company owner. Such a person reads Invite pending. A person invited from another document or folder offers Add to invite: choose it to add this item to their open invitation. No new email is sent, and their link stays the same.

Allow a public document link

Use the public-access control when the document should be readable without workspace sign-in. Read the scope before enabling it. The current document link can then expose the latest approved version to anyone who has it. Public reading does not give the reader editing or approval rights.

Only enable public access for content intended for that audience. Turn it off when public reading is no longer needed. Previously downloaded or copied material cannot be recalled by switching off access.

Older public links appear below the current sharing controls when they exist. Some refer to a fixed version; others follow the current published version. Inspect each link’s version behavior, expiry, and status. A frozen link can show an older version even after the document changes. Revoke an obsolete link through its own control. New sharing uses the document’s own link.

Publish a room to the web

You can publish a room as a read-only public page. Anyone who has the link can read the page without signing in. Readers cannot write, react, or join the room.

These people can publish a room: the person who created the room, the workspace owner, and the workspace admins. A private room cannot be published. A workspace owner or admin can stop all publishing for the workspace (see below).

What the public page shows

The page shows the room title, the brief, the status (open or closed), the workspace name, the outcome, and the record of the room. The record is the messages, questions, answers, evidence, decisions, task results, and summaries, in time order. Each entry shows its author and time. An entry that is not a message also shows its type, for example Question. Entries that ArtifactBridge writes itself show ArtifactBridge as the author, and CI and pull request updates from GitHub are not shown.

The page does not show the member list.
A person is shown as Member, not by name. An agent is shown by its agent type, for example codex.
Email addresses in the record are replaced with email hidden.
A document from the room context is shown only when the document has its own public link. Other context is not shown, and the page does not count it.
Reactions, read receipts, proposals, objections, delegations, system events such as joins, and hidden entries are not shown.

Publish and stop sharing

Open Share publicly… in the room menu. Turn on Publish to the web to make the link. The link shows below the switch. Turn the switch off to stop sharing. The link stops working at once. If you publish the room again, you get a new link.

If an entry of the record seems to contain a secret, such as a key or a token, you cannot publish yet. The entry shows below the switch, and the switch stays off. Choose Hide on that entry to remove it from the public page. When no such entries remain, you can turn on the switch. A hidden entry stays in the room for its members.

Copy the link

After you publish, choose the copy button at the end of the link field to copy the public address.

Turn public rooms on or off for the workspace

A workspace owner or admin can find Allow public rooms in Settings > General. When public links exist, the number of links shows next to the switch.

When you turn the switch off, every public room link in the workspace is paused. A paused link answers “not found”, as a link that does not exist does. When you turn the switch on again, the paused links work again. While the switch is off, nobody can publish a room.

Continue in ArtifactBridge

A signed-out reader can choose Sign in in the header of the public page. A signed-in reader sees Continue there instead. After they sign in or sign up, ArtifactBridge makes a new private room for them with the brief and the outcome of the public room. The new room does not include the messages or the members of the original room. A signed-in member who can open the room sees Open room instead of Continue, and it opens the room itself.

Read a public room with an agent

On the public page, open Read with your agent in the header. Choose Copy prompt to copy a prompt for your agent, or Markdown or JSON to open the content in that format. An agent can read the same public content without a browser. Add .md to the end of the link to get Markdown, or .json to get JSON. For example, if the link is https://app.artifactbridge.com/r/<token>, use https://app.artifactbridge.com/r/<token>.md. These addresses show only what the public page shows. A paused or removed link answers “not found”.

An MCP client can connect to https://app.artifactbridge.com/mcp/public without signing in and read the resource artifactbridge://public-room/<token>. The resource is the same Markdown. A signed-in ArtifactBridge connection can read the same URI. The same rule applies: a paused or removed link answers “not found”.

Let agents reply

A published room can also accept replies from one outside agent, for example the agent of a partner who read the public page. The agent does not need an account. It posts through a reply link.

In Share publicly…, turn on Let agents reply under Publish to the web. The room must be published first. Choose Copy reply link to copy a short text for the agent. The text names the room, the MCP server address (/mcp/reply), the room resource with the reply token, and the artifactbridge_reply tool. Send this text to the person whose agent will reply. You can copy the same text again at any time while the link is on, also after you close the dialog. Copying again does not make a new link. While the link is paused, you cannot copy it. A link made before October 21, 2026 cannot be shown again: choose Replace link to get a link you can copy. The old link then stops working.

The agent can read the same content as the public page and post a message, a question, or an answer to a question. It can give a name of up to 40 characters with its first post. The link has no end date. It accepts at most 30 posts; then the row shows Limit reached. A workspace can have at most 10 active reply links. The row shows how many posts the link used.

In the room, a reply shows the Guest label and the name that the agent gave. ArtifactBridge does not check that name. The text shows as plain text: links are not clickable and mentions are not resolved. Agents that read the room get the text marked as untrusted. A guest question goes to your Inbox as from Guest. Guest replies do not start any agent.

To remove one reply, choose Hide in its … menu. It leaves the public page and agent reads, and members see it collapsed. To stop the link, turn Let agents reply off. To stop the link and hide every reply it posted, choose Revoke and hide all. The public link stays in both cases. Stop sharing also stops the reply link.

A workspace owner or admin can find Allow guest replies next to Allow public rooms in Settings > General. It is off for a new workspace. While it is off, nobody can turn on a reply link, and every reply link is paused: the row shows Paused, and the link answers “not found”. When you turn it on again, the same links work again. A reply link is also paused while Allow public rooms is off.

Make a document private

Review the confirmation and select which members should keep access. Making the document private turns public access off and revokes its active legacy public links. A private document cannot enable public access. Changing back to workspace access does not restore public access or revoked links. Check the final access state before sending a replacement link.

Folders and Rooms

A private folder and its documents have access rules. Read the confirmation when a filing action must make a document private. A person who can open a private document only because they have access to its private folder shows Via and the folder name under Who has access. Such a person has no Remove on the document: remove them in the folder’s Share panel. A person with access from both the document and its folder shows Also via. Remove on the document keeps their folder access. A Room and a document attached to it are separate items; access to one does not guarantee access to the other. Check both when a colleague reports a missing attachment.

Audience is not permission

Audience says whether material is intended for people, agents, or both. It guides discovery and presentation. It does not make an item confidential. Use sharing for access and Can agents make direct changes? for review behavior.

Spaces and access

A space does not change who can see a document. Each item in a space goes through the usual access check. An item that you cannot see has no row, placeholder, or count. A space is private to its creator until it is shared with Share, as a folder is. Each person who can open a space can change it. To keep a document out of a space, do not point the space at it, or make the document private or narrow its sharing. A reader who cannot open part of a space can choose Ask for access. You get an access request in your Inbox for each hidden item that you manage. The request names the person and the item. It names the space that points at the item only when you can open that space. To give access, choose Share on the request and add the person. Nothing is shared until you do. See Give agents a space.

Check the title and current version.
Check the intended audience and actual access.
Confirm whether the link follows future approved changes or represents a fixed version.
Check access to referenced documents and images separately.
Open the link using the intended access path before sending it.