enumeray access decide

Approve, reject or withdraw a model access request.

Use when: A model administrator has reviewed a pending request, or its submitter wants to withdraw it.

Role and prerequisites: Model administrator for approved/rejected; requesting user for withdrawn. Install enumeray, configure the API and log in. Use an account or delegated token with the required permissions. Example IDs must be replaced with IDs from your service.

Example

enumeray access decide scalar-double 33333333-3333-4333-8333-333333333333 approved
# The requesting user can instead withdraw their own pending request:
enumeray access decide scalar-double 33333333-3333-4333-8333-333333333333 withdrawn

Inputs and options

Input	Meaning and use
<MODEL>	Stable model ID from model list/get or supplied by the author. An unlisted model can be addressed by ID, but still requires access.
<REQUEST>	Access-request ID from access requests or access request. The submitter may withdraw their own request; model admins decide approved/rejected.
<DECISION>	approved or rejected for a model administrator’s decision; withdrawn for the requesting user. Withdrawal does not grant access.

Every command also accepts the profile, API, JSON and timeout options.

Result and next step

approved grants the requesting account model access; rejected denies the request; withdrawn closes the submitter’s pending request. A request that is already decided cannot be changed to another decision.

Inspect requests or model get; execution still requires a current available publication.

Exact syntax, defaults and accepted values

Approve, reject or withdraw a model access request

Usage: enumeray access decide [OPTIONS] <MODEL> <REQUEST> <DECISION>

Arguments:
  <MODEL>     Stable model ID from model list/get or supplied by its author
  <REQUEST>   Access-request ID from access requests or access request
  <DECISION>  approved/rejected for a model administrator; withdrawn for the requesting account [possible values: approved, rejected, withdrawn]

Options:
      --api <API>          User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --profile <PROFILE>  Named local user API/login profile; host/runner commands use explicit configuration [default: default]
      --config <CONFIG>    Private user profiles file; defaults to $XDG_CONFIG_HOME/enumeray/profiles.json or ~/.config/enumeray/profiles.json
      --json               Emit user API results as JSON (NDJSON for following logs) and runtime errors on stderr; host/runner output follows its own protocol
      --timeout <TIMEOUT>  User API HTTP timeout in seconds; live logs use it for read inactivity. Does not limit execution time [default: 60]
  -h, --help               Print help