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

# Library Status Design

> How to structure workspace file statuses so teams can scan progress quickly.

## Overview

The **Library** tab controls whether file statuses are visible in the workspace and how the status catalog is designed.

<Frame caption="Workspace library settings and status catalog">
  <img src="https://mintcdn.com/tessact/Zj4-sgOsBzzd_RXr/images/admin/admin-workspace-library-live-v2.jpg?fit=max&auto=format&n=Zj4-sgOsBzzd_RXr&q=85&s=dfa9e989935991954691e1639973cc3e" alt="Workspace library status settings" width="1600" height="1000" data-path="images/admin/admin-workspace-library-live-v2.jpg" />
</Frame>

***

## What The Library Section Controls

* whether **Show file status** is enabled
* which status types exist
* the order in which statuses appear
* the default status for new uploads

This is how admins turn status from a vague concept into a visible workspace system.

***

## Guide: Create A Clean Status Catalog

<Steps>
  <Step title="Enable status visibility">
    Turn on **Show file status** if teams should see progress directly in the library.
  </Step>

  <Step title="Create the status types the workspace actually needs">
    Use **New status** to define the label, icon, color, and optional default behavior.

    <Frame caption="New-status flow inside the workspace library settings">
      <img src="https://mintcdn.com/tessact/Zj4-sgOsBzzd_RXr/images/admin/admin-workspace-new-status-live-v2.jpg?fit=max&auto=format&n=Zj4-sgOsBzzd_RXr&q=85&s=e42d815c79cda376fbc517a12cf80f16" alt="Create a new workspace status" width="1600" height="1000" data-path="images/admin/admin-workspace-new-status-live-v2.jpg" />
    </Frame>
  </Step>

  <Step title="Keep the catalog readable">
    Use a small set of durable statuses rather than many overlapping labels that teams will ignore.
  </Step>
</Steps>

***

## Good Status Design Looks Like

* names that imply action or state clearly
* a small enough catalog that people can scan it quickly
* color and icon choices that help, not distract
* a sensible default for newly uploaded files

***

## Best Practices

* Build the catalog around real handoffs in the workspace.
* Keep status names short and operational.
* Retire statuses that are no longer meaningful.
* Review status design whenever the workspace workflow changes.

***

## Next Steps

<Card title="Rolling out file statuses" arrow="true" horizontal href="/admin/workspaces/library-rollout">
  Use a rollout checklist before making statuses part of team process.
</Card>

<Card title="Status systems and limits" arrow="true" horizontal href="/admin/workspaces/policies">
  See where library design fits in the wider workspace policy model.
</Card>
