Skip to main content
Artifacts turn Tess chat answers into business deliverables: executive reports, dashboards, presentations, internal announcements, and proposals in HTML. Each Artifact has an owner, a version history, and a stable link, and sharing follows the policies your company’s admin defines.
Access to this feature depends on your plan and your role in the workspace. Without that permission, Tess answers in text and does not create the Artifact. To get access, contact your workspace admin.

​
Value for your company

One source per document

The deliverable lives at a stable link. Updates create new versions at the same address instead of new files circulating through email and chat.

Review before release

Edits do not reach people who already have the link automatically. They see the approved version until the owner shares the next one.

Governed sharing

Each person’s reach is set by the admin, per member and per team. By default, nothing opens outside the organization.

Workspace oversight

Authorized managers view the workspace’s Artifacts and can unpublish any of them, including in bulk.
The result is less rework on recurring materials, fewer outdated versions in circulation, and control over what each audience can access.

​
What you can create

Artifacts are HTML pages viewed inside Tess. When the destination requires a file, such as PowerPoint, Word, PDF, or Excel, ask for that format explicitly in chat: Tess generates the file separately.

​
Version control

  • Every edit or restore creates a new version (v1, v2, v3…). Earlier versions are only removed if the owner deletes them, and numbers are never reused.
  • An Artifact separates the latest version, where the owner works, from the shared version, which the audience sees.
  • To update what the audience sees, the owner explicitly shares the new version. The link stays the same.
  • Any earlier version can be previewed, restored (as a new version), or set as the shared version.
In practice, a report can be corrected and reviewed while leadership keeps reading the last approved version.

​
Who has access and what they can do

Only the owner changes an Artifact. Anyone who needs a variation can ask Tess for their own copy, as long as they can also create Artifacts. The original stays unchanged.

​
Sharing levels

  • Specific people in the workspace or, when the workspace belongs to an organization, in its other workspaces
  • Teams the owner belongs to
  • Everyone in this workspace
  • Anyone with the link, as long as they are signed in to Tess, including outside the organization

​
Governance for admins

Creating, editing, and sharing Artifacts are enabled by plan and role. Users without that permission get the answer as text, without the page.
On the members page, the admin sets per member and per team which levels are allowed: organization, workspace, teams, and open link. The default allows organization, workspace, and teams, and keeps the open link off. A member setting with no levels turns sharing off for that person.
When an admin narrows a member’s or team’s levels, access outside the new rule stops at once and the matching shares are revoked automatically. Permissions are checked on every open: anyone who leaves the workspace loses access right away, except to Artifacts open to anyone with the link.
Managers with the Artifacts Manager permission list workspace content by person, view the latest version of any Artifact, and unpublish one or many at once. Unpublishing removes all access. When a manager unpublishes, the owner cannot share that Artifact again.
Even the open link requires a Tess login. Pages are not indexed by search engines and cannot be embedded in other sites.
On the Enterprise plan, Audit Events record creation, edits, publishing, every grant and revocation, views and opens by managers (one per person per day for each Artifact), and changes to sharing restrictions. The company SIEM collects them through the API. Events identify who acted, but do not include the Artifact title or the email of the person who received access.

​
API integration

Artifacts are also available through the Tess public API: create, edit, rename, list and restore versions, publish, unpublish, share, and delete, with the same owner, permission, and sharing-policy rules as the panel. Your systems can generate and refresh recurring reports without going through chat. See the Artifacts API guide.

​
Limits

An Artifact contains the data provided when it was created or edited. Dashboards do not connect to live systems, and page scripts cannot reach the internet. To refresh the numbers, ask for the update in chat and share the new version.
To publish a site that is open on the internet, use Tess Pages. For the step-by-step guide to creating and sharing, see Create and share.