---
url: /handbook/governance/holdings.md
description: >-
  The access a person already has, one scope at a time, with its source and
  date.
---

# Holdings

A **holding** is one scope a person holds in one system, written as `system/action:object`, with its source and the date it was recorded.

Example: `oracle-ebs/approve:invoice-hold`, source "access export, October 1".

## A ceiling, not a justification

Holdings set the most a human-delegated agent can hold. Rule CEIL-01 removes any scope the owner does not hold.

Being within the owner's holdings does not make a scope necessary or safe. An owner may hold privileged access their task never uses. Whether a scope is needed is a separate question, answered today by the approval chain. A computed check against the Task Cards (CEIL-02) is **Planned**. See [The key join](the-key-join.md).

## Rules for holdings

* **Matched by email or external id, never by name.** Rows that match no person, and access that matches no catalog scope, are reported, not loaded.
* **Per person, not per role.** Two people with the same title can hold different access.
* **As of the export date.** DutyGraph reads the access export you upload. It does not connect to your identity system.
* **Never published as Repo files.** The Repo compiler and DutyGraph Agent do not read holdings. Holdings stay in the database, behind row-level security. Compiling an import receipt (file name, row count and a SHA-256 hash) into the Repo is **Planned**.

## When holdings change

A new export is a new, versioned holdings pack. The old version stays on record.

| What happens | Status |
| --- | --- |
| A pending request's next decision is refused as stale until the reviewer reloads | **Built** |
| Each approving decision and the issue step check the owner's current holdings | **Built** |
| Issued agents are found and recomputed against the new holdings | **Planned**. Today an issued agent keeps its issued scopes until it expires or is revoked. |

The agent builder keeps its own record of each role's access to a system. When that recorded access drops, a saved builder manifest that relies on it turns **Broken**. That is separate from the governance holdings pack.

## Where holdings come from

| Source | Status |
| --- | --- |
| An access-export CSV uploaded in **Agents › Rules › Set up governance** | Built |
| A read-only connection to Okta, Entra ID or Saviynt, set once at the company level | Planned |

::: warning
DutyGraph does not collect employees' own logins to business systems. Planned live connections are read-only service connections with the narrowest scopes each system offers.
:::

::: info
**Status.** **Built**: holdings from an uploaded CSV, matching by email or external id, versioned packs, stale-decision refusal and the CEIL-01 ceiling. **Simulated**: holdings in the sample companies are illustrative. **Planned**: live identity connections, recomputing issued agents when holdings change, and an import receipt in the Repo.
:::
