Share an artifact with the right people

Give your department direct access to a document, publish a version to the company Marketplace, and understand why sending a link never grants access on its own.

Artifacts are private to you until you say otherwise. There are exactly two ways to let someone else in, they do different jobs, and doing one never does the other.

Open the artifact and choose Share in the header. The dialog has both.

Direct access: let your department open this one

Use this when specific colleagues need to read this exact piece of work.

In the Direct access section, choose your department instead of Private.
Choose Copy link.
Paste the link wherever your team is: Slack, Telegram, email.

What the recipient gets is deliberately narrow. They sign in, they open the exact version you linked, and they read it. No editor, no history, no restore, no archive, no render, no sharing controls of their own.

Copying the link never widens access. If you paste a link before changing the audience, the person clicking it gets nothing. Change the audience first, then copy.

Direct access offers Private and your active department. Company wide direct access is not an option, and there is no public link. Sharing outside your workspace is not something an artifact can do; anyone opening the link must be a signed in member of your workspace.

Marketplace: let the whole company reuse it

Use this when the artifact is a template other people should start from, not a document two people need to read.

In the Marketplace section of the same dialog, list the current version.
Coworkers now find it under Marketplace and add their own private copy.
When you improve the artifact, come back and choose Update listing to v4 (or whatever version you are on). The listing is frozen at the version you published, so editing the artifact does not silently change what everyone else sees.
Remove takes the listing down. Your artifact is untouched.

A listed artifact shows In the Marketplace on its row so you can tell at a glance.

The two are independent

Publishing to the Marketplace does not give anyone direct access to your live artifact.
Giving your department direct access does not put anything in the Marketplace.
Whatever you do, ownership stays yours.

Web apps are different

A web app can be given department direct access and opened read only through its link. It never goes to the Marketplace and it is never public. If you download the HTML and open it outside TalentOS, it loses the sandbox that keeps it isolated, which is why the download warns you.

A worked example

Your department needs to review a customer briefing, but the rest of the company does not. Set Direct access to your department, copy the version link, and send it in the team channel. Later, if the structure is useful as a reusable template, publish a clean version to the Marketplace. The review link and the reusable listing remain separate.

What to check

A coworker says the link is dead. The audience is still Private, or they are not in the department you shared with, or they are signed into a different workspace.
You have no department to choose. Ask an admin to put you in one. Direct access has nothing to widen to until then.
Share is unavailable for a moment. A version you just saved has to finish committing before it can be shared, so the link cannot go out under the wrong label. Wait a beat and reopen the dialog.
An old link says Company. Company wide direct access grants made before this rule still open, but you cannot create new ones. Move that artifact to the Marketplace instead.