> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tess.im/llms.txt
> Use this file to discover all available pages before exploring further.

# Create and share an Artifact

> Generate reports, dashboards, and presentations in chat, review versions, and share them with the right people and teams within company policy.

This guide shows how to generate an Artifact in Tess chat, review its versions, and share it with the right people. For the feature overview and governance rules, see [Artifacts](https://docs.tess.im/en/html-artifacts.md).

> [!NOTE]
>
> Creating Artifacts depends on plan and role. Without that permission, chat answers in text and does not generate the page.

**1. Generate the Artifact**

In chat, describe the deliverable: audience, format, structure, and data. Paste or attach the data the page should show.

```text theme={null}
Create an executive pipeline report for leadership.
Structure: three KPIs at the top (open, committed, and lost
pipeline, with the change versus last week); a table of
opportunities above $50k with owner, stage, and expected date;
at the end, up to five items that need a decision.
Data: [paste the table or attach the file].
```

The Artifact opens in the panel next to the chat as v1.

**2. Review and adjust**

Ask for changes in chat, objectively:

```text theme={null}
Change the committed variation to +12% and move the table
above the KPIs.
```

To change a specific part, use **Select element** in the panel menu (in preview mode), click the element, and describe the change. Every saved change creates a new version. The owner switches between **Preview** and **Code**.

**3. Manage versions**

In **Versions**, each row shows **Latest** (newest version), **Shared** (the version the audience sees), and **Viewing** (the version on screen). You can preview earlier versions, **Restore** one as a new version, or use **Share this version**.

Under **Delete**, in the panel menu, choose between **Delete only this version** and **Delete all versions**. With a single version, the option is to delete the Artifact. Deleting the Artifact ends all sharing. Deleting also requires the workspace content-deletion permission.

**4. Share**

In **Share**:

* **Add people**: search by name or email among workspace members and, if there is one, the organization.
* **Teams**: teams you belong to.
* **General access**: **Everyone in this workspace** or **Anyone with the link** (users signed in to Tess, including outside the organization).
* **Copy link**: the address to send to your audience.

The first share releases the current version. After that, new edits do not reach the people it was shared with until you click **Share vN**. Managers with the Artifacts Manager permission can see the latest version. The confirmation reads **Latest version shared**.

**5. Present, export, or follow up**

On the Artifact page (the one the link opens), **Present** opens it in full screen, **Download** saves the HTML, and **Print** is in the menu. **Start chat** opens a new conversation with a request for the Artifact's highlights already filled in, so recipients can ask questions.

## Sharing and governance

Every share follows rules set by the company, not by the person sharing. The admin decides how far each Artifact can reach, oversees what is circulating and, with the Artifacts Manager permission, can take any Artifact in the workspace offline.

### Who sets the reach

On the Members page, the admin enables sharing levels per member and per team:

| Level | Reach | Default |
| - | - | - |
| Organization | Specific people from other workspaces of the same organization (only when the workspace belongs to an organization) | On |
| Workspace | Specific people or everyone in this workspace | On |
| Teams | Teams the owner belongs to | On |
| Public | Anyone signed in to Tess, including outside the organization | Off |

* **Precedence:** the member's own setting applies first. Without one, the levels of all the person's active teams apply together; a team without its own setting counts as the default. With neither, the default applies.
* **Full block:** a member setting with no levels turns sharing off for that person. To block someone, set it on the member: a team restriction does not apply if the person is in another team with more levels.
* **In the share dialog:** levels that are not enabled appear disabled, with guidance to ask the admin.

### What the platform guarantees

* **Members only:** you can only add active members of the workspace or the organization. No outsider is found in search, not even by exact email. The only way to reach someone external is **Make public**, if the policy allows it.
* **Restrictions apply immediately:** when the admin narrows a member's or team's levels, access outside the new rule stops at once and the matching shares are revoked automatically. When the change removes a level, the screen asks for confirmation before saving.
* **Access checked on every view:** anyone who leaves the workspace or the team loses access immediately, with no manual step. The exception is the open link, which works for anyone signed in to Tess.
* **No internet exposure:** even the public link requires a Tess login. Pages are not indexed by search engines and cannot be embedded in other sites.
* **The audience sees only the approved version:** people with the link never see drafts or the Code tab. They can download the HTML of the shared version, so include only what that audience may see.

### Oversight

* In **Settings > Artifacts**, managers with the Artifacts Manager permission filter by person, see each Artifact's status (private, shared, or published), and open any of them.
* A manager can unpublish one or many at once. Unpublishing removes every grant, and the owner cannot publish that Artifact again.
* Opens by managers are recorded in the audit log as their own event, separate from ordinary views (one per manager per day for each Artifact).

### Audit trail

On the Enterprise plan, [Audit Events](https://docs.tess.im/en/audit-events.md) record each Artifact's lifecycle. The company SIEM can collect these events through the API:

* creation, edits, renames, restores, and deletion of versions and of the Artifact;
* publishing and unpublishing, showing whether the owner or a manager unpublished;
* every grant and revocation; when a revocation comes from unpublishing or a narrowed policy, the event carries the reason (owner, manager, or policy);
* views (one per person per day per Artifact) and opens by managers;
* changes to member and team sharing restrictions, with before and after.

Events identify who acted. Share targets appear as internal IDs, and events do not include the Artifact title or the email of the person who received access.

### Revoking access

To revoke a person's or team's access, use **Remove** in the access list. Turning off **Everyone in this workspace** or **Anyone with the link** revokes that reach. To take everything offline at once, select the Artifact in **Settings > Artifacts** and use **Unpublish**.

## Example requests by team

> [tab] Sales
>
> ```text theme={null}
> Create a sales funnel dashboard for this month: four KPIs at the
> top, a funnel by stage, and a filter by sales team.
> Data: [paste or attach].
> ```

> [tab] Finance
>
> ```text theme={null}
> Create a monthly close report with revenue, expenses, and margin
> by business unit, compared with the budget, highlighting
> deviations above 5%. Data: [paste or attach].
> ```

> [tab] Leadership
>
> ```text theme={null}
> Turn this report into an eight-slide board presentation.
> One topic per slide. The last slide lists the decisions we need
> approved.
> ```

> [tab] HR and Communications
>
> ```text theme={null}
> Create an internal announcement about the new hybrid work policy:
> what changes, starting when, who is affected, and who to contact
> with questions.
> ```

> [tab] Sales proposals
>
> ```text theme={null}
> Create a one-page proposal for [client]: context, scope for the
> first 90 days, what is out of scope, investment, and next steps.
> ```

## Best practices

* **Share the approved version.** Review before you use **Share vN**. Until then, the audience stays on the previous version.
* **Prefer teams and workspace over the open link** for internal content.
* **Keep one Artifact for recurring materials.** Ask for the update in the same Artifact to keep the link and the history.
* **Include only data the audience may see.** Anyone with access sees all of the page content.
* **Ask for the file format when the destination requires it.** For PowerPoint, Word, PDF, or Excel, request the format in chat.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.