oz0 subject restrict
Restrict processing of one person's data at their request.
For: Operators and developers looking up a command.
Restrict processing of one person's data at their request. Every start of a job about them is refused from then on, whatever starts it: the runtime API, chats, webhooks, events, routines (scheduled ones too) and kept eval cases. Their running jobs are cancelled within seconds. Their data is kept, and left out of governance replays and evals; their own bundle (subject export) still holds it.
--lift ends the restriction: it loosens a governance control, so it takes a reason and, where the tenant has four eyes on, another admin. subject find shows restrictions. The tenant's admins may.
Usage
oz0 subject restrict SUBJECT --reason REASON [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--json | bool | print JSON instead of a table | |
--lift | bool | lift the restriction instead (another admin may need to approve it) | |
--reason | string | why, such as the request it answers (required; default $OZ0_REASON; at most 500 characters) |
Inherited flags
| Flag | Type | Default | Description |
|---|---|---|---|
--context | string | $OZ0_CONTEXT or <config dir>/orchestrator-zero/context.json | CLI context file written by server init |
--log-level | string | info | log level: debug, info, warn or error |
--tenant | string | default | the tenant |
See all oz0 commands and the global flags.