## pyre admin

Operator commands: hubs, users, tenants

### Synopsis

Operator commands, available to the account listed as operator on the
control plane (on the SaaS: daniel@pyredata.io). A customer's token gets
"not found" here. Use "pyre auth whoami" to see whether the saved token
is an operator's.

```
pyre admin [flags]
```

### Options

```
  -h, --help   help for admin
```

### Options inherited from parent commands

```
      --api string       API base URL (default from the profile, or https://api.pyredata.io)
      --ca-cert string   PEM file with an extra CA to trust (self-hosted managers)
      --insecure         skip TLS certificate verification (lab use only)
  -o, --output string    output format: table, json or plain (default "table")
      --profile string   config profile to use (see: pyre config)
  -q, --quiet            print results only, no notices
      --token string     API token (default from the profile; prefer PYRE_TOKEN in scripts)
  -y, --yes              answer yes to every confirmation (for scripts)
```

### SEE ALSO

* [pyre](pyre.md)	 - Pyre: disaster-recovery backup as a service
* [pyre admin diagnostics](pyre_admin_diagnostics.md)	 - Error reports the apps sent: versions, the failing step, a redacted trace
* [pyre admin exports](pyre_admin_exports.md)	 - Export downloads: list, create for any tenant, remove, set up a hub's endpoint
* [pyre admin hubs](pyre_admin_hubs.md)	 - Add, build, promote, demote and remove hubs
* [pyre admin tenants](pyre_admin_tenants.md)	 - List tenants with usage
* [pyre admin tokens](pyre_admin_tokens.md)	 - Every tenant's API tokens: list, revoke, remove, prune
* [pyre admin users](pyre_admin_users.md)	 - Approve, reject, inspect and delete users

