Grant, sign-in and permissions

Authentication and entitlements · Layer 1

"He says where anyone goes."

What Grant does

Grant answers two questions for every request: who are you, and what are you allowed to do? Services ask him instead of keeping their own rules.

Accounts and tokens

Grant signs people in and issues signed tokens that other services can verify.

Entitlements

Each account has a set of things it may do. Give someone full access or read-only, and it's enforced the same way everywhere.

One decision point

The API and the web app consult Grant for access decisions, so a rule changes in one place.

Audit trail

Grant records who did what and when, so you can trace an action back to an account.

Credentials in a sealed vault

Integration secrets live in one encrypted vault rather than scattered across env files.

How it works

Every protected request goes through the same four steps.

  1. A request arrives with a token.
  2. The service asks Grant to verify it and check the account's entitlements.
  3. If the account is allowed, the request goes ahead. If not, it's refused.
  4. The decision is recorded in the audit log.

Where it fits in the four layers

1 Infrastructure & roles Vera, Grant, the bus, the device registry
2 Data pipeline & state Flo, DynaRAG, the carousel
3 Reasoning & inference Rick, Annie, Max, Hank
4 UI & collaboration Marco, Noted, Norm, the graph

Grant is layer 1. Walt, Mona, Marco and the rest ask him who may do what, over the same API every time.