Roles, policies and audit
Who may decide, what needs approval, what was done and by whom.
| Role | May |
|---|---|
| owner | everything, including billing and removing the organisation |
| admin | manage members, devices, policies, keys and webhooks; approve production steps |
| member | start and act on work, add devices |
| billing | read and manage credits |
| viewer | read |
Policies
Three are fixed, because they describe how PHRONEN works for everyone: irreversible steps wait for a decision; a device uses only what it was granted; your data is never used for training. One is yours to set: whether production needs an owner or admin.
Audit trail
Approvals, device changes, key and webhook events, credit movements and policy changes are written to an audit trail your organisation’s owners and admins can read in the product and at GET /api/v1/audit.
Was this page helpful?