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

# Use Cases

> See what AI is used for, declare what each service is meant for, and spot use outside that.

## What Are Use Cases?

A use case is the purpose a session served, such as document drafting or code review. Velatir identifies the use cases of every session once it ends. A session can serve several use cases, and each one carries a score for how closely the session matched it.

Use cases appear on [Sessions](/traces/understanding-sessions), in [Insights](/insights/overview), on the **Workspaces** page, in [Reports](/reports/overview), and in an optional summary notification.

## Declared and Undeclared Use

On their own, use cases show what AI is used for. Once you declare what a service is meant for, Velatir also compares each session against that.

| Status | Meaning |
| - | - |
| **Declared** | The use case is declared for the service in the session's workspace. |
| **Undeclared** | The service is used for something it is not declared for there. |
| **Not measured** | The service has no declared use cases yet, so there is nothing to compare against. |

<Note>
  Use is only flagged as undeclared once its service has declared use cases. Until then it shows as **Not measured**.
</Note>

## Declare What a Service Is For

Administrators declare use cases on services that are already declared in the [inventory](/inventory/overview).

<Steps>
  <Step title="Open the service" icon="package">
    Open **Inventory**. On the service under **Declared services**, select **Declared use cases**.
  </Step>

  <Step title="Add use cases" icon="plus">
    The dialog lists the use cases identified on that service so far. Add the ones that fit your policy, or remove ones you declared before.
  </Step>

  <Step title="Save" icon="check">
    Select **Done**. New sessions on the service are compared against the declared set.
  </Step>
</Steps>

Members who can view the inventory but not change it see the same dialog read-only.

<Tip>
  You can also declare a use case straight from a session. See [On a session](#on-a-session) below.
</Tip>

## Workspaces

Workspaces inherit the use cases declared for the organisation, and nested workspaces inherit from the workspace above them. Each workspace can adjust what it inherits:

* **Undeclare** an inherited use case for that workspace.
* **Declare** further use cases for that workspace only.
* **Return to inheriting** to drop its own changes.

To change them, open **Workspaces**, expand a workspace, and select **Edit use cases** on a service under **Declared services**. The dialog groups use cases as **Inherited**, **Inherited but undeclared**, and **Declared for workspace**.

A change made at the organisation still reaches every workspace, unless that workspace changed the same use case itself.

Each service in the list shows which use cases are declared or undeclared for the workspace. Open the badge to see each use case's share of the workspace's sessions on that service.

## Where Use Cases Appear

<AccordionGroup>
  <Accordion title="On a session" icon="messages-square">
    The **Sessions** list has a **Use cases** column. Undeclared use cases are listed first. Select a use case to open the session with its **Session summary**.

    The summary lists the **Identified use cases**, grouped into **Declared for** and **Undeclared for** the session's service. A declared use case shows whether it was declared for the organisation or for a workspace.

    Administrators can declare an undeclared use case from here, and choose whether it applies to the organisation or to one of the workspaces the session belongs to. They can also remove a declared use case at the level it was declared.
  </Accordion>

  <Accordion title="In Insights" icon="chart-line">
    The **General** view has a **Use cases** section. It shows how all use splits across **Declared**, **Mixed**, **Undeclared**, and **Not measured**, which use cases are declared or undeclared, and how the undeclared share compares with the previous period.

    **Mixed** means a use case is declared for some services or workspaces and not others.

    Service cards and workspace cards also have a **Use cases** tab. See [Insights](/insights/overview#use-cases).
  </Accordion>

  <Accordion title="In reports" icon="file-text">
    Reports can include a **Use cases** section. See [Reports](/reports/overview).
  </Accordion>
</AccordionGroup>

## Use Case Summary

Each member can turn on a regular summary of declared and undeclared use. It shows the declared and undeclared shares, how they changed since the previous period, the most undeclared use (use case, service, and workspace), and a link to the matching sessions.

<Steps>
  <Step title="Open the settings" icon="bell">
    Open **Notifications** in the sidebar and select **Settings**.
  </Step>

  <Step title="Choose scope and period" icon="sliders-horizontal">
    Under **In app use case summary**, set the **Scope** to the organisation or a workspace, and the **Period** to every week, every two weeks, or every month.
  </Step>

  <Step title="Choose where it arrives" icon="mail">
    Turn on **In app use case summary** to see it in **Notifications**. For email, turn on **I want to receive e-mails relevant to this organisation** and select **A use case summary**. Then select **Save changes**.
  </Step>
</Steps>

A summary arrives after each period ends. A workspace scope includes the workspaces nested under it. When nothing in the period was undeclared, no summary is sent.

***

<CardGroup cols={2}>
  <Card title="Insights overview" icon="chart-line" href="/insights/overview">
    Use cases alongside activity, risk, and adoption.
  </Card>

  <Card title="Inventory" icon="package" href="/inventory/overview">
    Declare services and what they are for.
  </Card>
</CardGroup>


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