Files
lancedb/docs/web/governance/authorization.mdx
T
Brendan ClementandClaude e2501b0dab docs: update example names (#4887)
Use neutral placeholder names and values in a few code examples in the
docs and Python docstrings. Text-only; no behavior change.

---
_Generated by [Claude
Code](https://claude.ai/code/session_019iqZdtD3ZMnvTMeoNsULgX)_

---------

Co-authored-by: Claude <noreply@anthropic.com>
2026-11-06 11:32:48 -08:00

53 lines
2.0 KiB
Plaintext

---
title: "Authorization"
sidebarTitle: "Authorization"
description: "Who may do what: an overview of LanceDB Enterprise's access control model."
icon: shield-halved
keywords: ["authorization", "authz", "privileges", "rbac", "access control", "grant", "revoke"]
availability:
embedded: unavailable
enterprise: available
---
[Authentication](/enterprise/authentication) establishes who is calling.
Authorization decides what they may do.
An access control entry grants **one privilege** on **one object** to **one
subject**. Everything on the Principals and Privileges pages is a
consequence of that shape.
## Granting a privilege {#granting}
`GRANT` and `REVOKE` cover every object in the catalog -- system, database,
schema/namespace, table, view, materialized view, secret, function, and
storage integration. A Secret, the one a day-to-day user shares most
often, looks like this:
<CodeGroup>
```sql SQL icon="database"
GRANT USAGE ON SECRET platform.`model-api-key` TO ROLE research
REVOKE USAGE ON SECRET platform.`model-api-key` FROM ROLE research
```
</CodeGroup>
The caller must already hold `OWNERSHIP` on the object being granted (`GRANT`
additionally requires the object to already exist; `REVOKE` does not, so an
entry left on a dropped object can still be removed). A role need not exist
beforehand, but a `USER` or `GROUP` name must resolve to exactly one identity
in your identity provider, or the statement fails.
See [Privileges](/governance/privileges) for the full statement syntax and
every privilege each operation needs. See [Principals](/governance/principals)
for who a grant can name.
## What to read next {#next}
<CardGroup cols={2}>
<Card title="Principals" icon="user" href="/governance/principals">
Users, groups, and roles -- where each comes from, and how a grant names one.
</Card>
<Card title="Privileges" icon="key" href="/governance/privileges">
Every object's privileges, and the GRANT/REVOKE syntax that covers them.
</Card>
</CardGroup>