# Lineage Permissions

Source: https://userguide.qualytics.io/lineage/deep-dive/permissions/

Lineage is governed by [user roles](https://userguide.qualytics.io/settings/access/users/roles/overview/), the platform-level roles that apply across the deployment. [Team permissions](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/) decide which containers the graph shows, and they apply to editing connections, to reading the job details an OpenLineage producer sent, when you leave the graph to open a container, to a datastore's own lineage and impact analysis, and to the operations that produce lineage. The details are under [Team Permissions](https://userguide.qualytics.io/lineage/deep-dive/permissions/#team-permissions) below.

## User Roles

| Action | Member | Manager | Admin |
| --- | --- | --- | --- |
| Open a container's Lineage tab and read the graph | Allowed | Allowed | Allowed |
| Expand the graph and focus on a field | Allowed | Allowed | Allowed |
| Open a datastore's Lineage tab, its map and its read-only canvases | Allowed | Allowed | Allowed |
| Run an impact analysis and export it | Allowed | Allowed | Allowed |
| Open a connection and see where it came from | Allowed | Allowed | Allowed |
| Copy the name of a node | Allowed | Allowed | Allowed |
| Add an upstream or downstream connection | Editor on both datastores | Editor on both datastores | Any datastore |
| Add a field-level connection | Editor on both datastores | Editor on both datastores | Any datastore |
| Edit a connection (API only) | Editor on both datastores | Editor on both datastores | Any datastore |
| Delete a connection | Editor on both datastores | Editor on both datastores | Any datastore |
| Send OpenLineage events | Editor on every affected datastore | Editor on every affected datastore | Any datastore |
| Read an OpenLineage connection's job details (run, transformations, SQL or source code) | Viewer on every datastore | Viewer on every datastore | Any datastore |

## UI Behavior Without Permission

| Scenario | What the User Sees |
| --- | --- |
| A Member or Manager without Editor permission on a node's datastore opens its menu | The menu still opens and **Copy Name** works, since copying needs no write access. **Add upstream** and **Add downstream** are not listed. |
| A Member or Manager without Editor permission on the datastore of either end hovers a connection | The connection's badge shows where it came from, and no delete control appears beside it. |
| A user whose team permission on a datastore is Reporter opens its Lineage tab | The tab is shown, and the map does not load. A datastore's lineage needs the **Viewer** team permission on that datastore. |
| A user with Editor permission opens a datastore's Lineage tab | The map, the lineage between two datastores and the all-containers canvas show no **+** buttons and no delete control. Editing is offered once a single container's lineage is open. |
| A container belongs to a datastore the user's teams do not cover | The container is not drawn, and neither are its connections. Counts, maps and impact analysis leave it out, and opening its lineage directly answers that the container was not found. |

## Team Permissions

The graph shows Members and Managers only the containers of datastores their teams cover, as the container listing does. A container in any other datastore is left out with its connections, so the graph, the field lens, the counts on each node, a datastore's map and impact analysis never name it or walk through it. A chain that passes through such a container stops at it. An **Admin** sees every container, since the Admin role carries access to every datastore.

Seeing a connection does not grant permission to edit it. **Open this table's lineage** on a node opens that container's own Lineage tab, which is part of the container's page and requires at least the **Reporter** team permission on its datastore. The same applies to the arrow beside another datastore's name on a datastore map card, and to **View table** in an impact analysis.

Adding, editing, and deleting connections requires **Editor** permission on every datastore associated with the connection, for both **Members** and **Managers**. A cross-datastore connection requires Editor on both ends. Fields inherit the requirement from their container's datastore. **Admins** can edit lineage in any datastore. An Admin restricted to a team follows that team's permissions.

Sending OpenLineage events follows the same rule: an event changes a connection only when the caller has Editor on the datastore of every container it touches, on both sides of a cross-datastore connection. That covers the connections an event retires as well as those it creates, whether a `COMPLETE` run or job definition no longer lists them or a `DROP` or `RENAME` retires them.

OpenLineage events resolve each dataset to the matching datastores the caller can edit. If two datastores point to the same host, database, and schema, a caller with Editor on one and Viewer on the other changes only the Editor datastore. Metadata, retirement by an authoritative event, and DROP or RENAME follow the same scope. Existing connections involving a datastore outside that scope stay unchanged.

A table that has not been catalogued yet still requires Editor when its identifier matches a known datastore. If none of the matching datastores grants Editor, the event is denied rather than treating the table as an outside asset. A denied event applies no changes. Sent on its own it returns `403 Forbidden`. In a list, the request answers `201 Created` with the denial in that event's status, and the other authorized events still apply.

The UI offers editing based on the datastores of a connection's ends, and **Add upstream** or **Add downstream** lists only the datastores where you have Editor. An end outside Qualytics adds no requirement in the UI, but when an OpenLineage connection's outside end names a dataset that matches a catalogued datastore, the API still requires Editor there and the delete control shows why it was refused.

Seeing a connection from OpenLineage does not show everything its producer sent. The record of who asserted it keeps its attribution for anyone who can see the connection: the producer, the kind of event, and when. The job's identity, run, datasets, transformations, submitter, and SQL or source code can quote values from your data, so they are shown only to users with the **Viewer** team permission on the datastore of every container the connection touches. Unrestricted Admins always see them.

A datastore's own lineage is the exception. Its map, the lineage between two datastores, the all-containers canvas and the ranking in impact analysis read out the whole datastore, so they need at least the **Viewer** team permission on that datastore. A user whose team permission there is **Reporter** can open the datastore's page, but its **Lineage** tab is refused. The impact analysis of a single container lists everything that container reaches, so it needs the **Viewer** team permission on the datastore the container belongs to. Its **Export** is hidden in deployments where downloads are turned off.

## Deleting Is Not Limited to Manual Connections

A connection can be deleted whatever created it, and the delete control does not depend on its category. What differs is whether it stays deleted:

- A **manual** connection stays gone, because nothing else produces it.
- A **data catalog** connection comes back on the next sync of that data catalog, since the data catalog is the source of truth for it.
- A **collected** connection comes back the next time a collection observes the relationship again.
- A **Qualytics managed** connection comes back when the computed container is saved again, or when the operation writes the table again.
- An **OpenLineage** connection is retired rather than removed, so who asserted it stays on record. It comes back when a job asserts it again.

Deleting is the right move for a relationship that is genuinely wrong. For one that is merely no longer wanted, remove it where it is produced: in the data catalog, or in the pipeline the source records.

## Lineage Qualytics Produces

The connections Qualytics generates itself carry no separate permission. They follow the operation that produces them: whoever can save a computed container, or run a materialize or a scan, produces the lineage that comes with it. **Collect lineage** on a Sync is available to whoever can run that Sync.

This is why a Member who cannot add a connection by hand can still cause connections to appear, by running an operation that writes one.

## See Also

- **How It Works**

  The connection model, the two levels of granularity, the rules a connection has to obey, and how to find the containers that have one.

  [How It Works](https://userguide.qualytics.io/lineage/deep-dive/how-lineage-works/)
- **Lineage Sources**

  The five categories a connection can come from, and how each is created, updated, and removed.

  [Lineage Sources](https://userguide.qualytics.io/lineage/deep-dive/lineage-sources/)
- **Reading the Graph**

  Direction, nodes, assets outside Qualytics, where a connection came from, and expanding the graph.

  [Reading the Graph](https://userguide.qualytics.io/lineage/deep-dive/reading-the-graph/)
- **Datastore-level Lineage**

  The datastore map, the lineage between two datastores, and every container of a datastore that has lineage.

  [Datastore-level Lineage](https://userguide.qualytics.io/lineage/deep-dive/datastore-level-lineage/)
- **Field-level Lineage**

  Expanding field lists, field metadata, and the focal field workflow.

  [Field-level Lineage](https://userguide.qualytics.io/lineage/deep-dive/field-level-lineage/)
- **Impact Analysis**

  What a container feeds and what feeds it, ranked across a datastore and exportable as CSV.

  [Impact Analysis](https://userguide.qualytics.io/lineage/deep-dive/impact-analysis/)
- **Examples**

  Enrolling a warehouse, a medallion pipeline across datastores, a remediation output, and a hop only a person can record.

  [Examples](https://userguide.qualytics.io/lineage/deep-dive/examples/)
- **Best Practices**

  Which source to lean on, how to run collection, and how to keep a graph you can trust.

  [Best Practices](https://userguide.qualytics.io/lineage/deep-dive/best-practices/)

*Last updated: November 9, 2026.*
