oz0 tenant notify-content
What the tenant's notifications carry: the event's facts (the default), or the call's arguments too.
For: Operators and developers looking up a command.
What the tenant's notifications carry: the event's facts (the default), or the call's arguments too.
facts: the tenant, the agent, the tool, the job's link, the deadline and the step. arguments: also the call's arguments, which then leave OZ to the SMTP relay and to each webhook's endpoint. Whether a tenant may send a call's arguments, which can hold personal data, to a mail relay or a customer's endpoint is an open legal question; setting it takes a reason, which the audit trail keeps.
--inactive-days sets after how many days without a sign-in or a decision the people who may decide an agent's approvals count as inactive (14 by default).
Usage
oz0 tenant notify-content <tenant> [facts|arguments] [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--decision-ref | string | the decision or case the change follows, such as a case number (at most 200 characters) | |
--inactive-days | int32 | days without a sign-in or a decision after which approvers count as inactive (1 to 365) | |
--json | bool | print JSON instead of a table | |
--reason | string | why notifications carry the call's arguments (required to turn arguments on) |
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 |
See all oz0 commands and the global flags.