Team and roles
Invite organization members and assign Owner, Technical admin, Editor, or Viewer access.
Loading documentation…
Powered by heyo
RestoreTrust uses organization roles for people and project-scoped API keys for automation. Give each person the lowest role that supports their responsibilities.
| Role | Read organization and projects | Manage project resources | Manage organization and members | Manage billing |
|---|---|---|---|---|
| Viewer | Yes | No | No | No |
| Editor | Yes | Yes | No | No |
| Technical admin | Yes | Yes | Yes, except owner changes | No |
| Owner | Yes | Yes | Yes, including owners | Yes |
Project resources include sources, secret metadata, schedules, notification channels, workers, API keys, checks, and reports as permitted by the plan. Owners retain responsibility for subscription and billing decisions.
Membership and roles apply to every project in the organization. There is no separate project-member list. Project-scoped API keys restrict automation to one project, but do not restrict a person's organization membership.
Open Organization and Members in the intended organization. Check current user capacity under Plan/Quotas.
Enter the member's email address and select the appropriate role. Use Viewer for audit or read-only review and Editor for routine project configuration.
The invited person accepts with the intended account. Invitations and sensitive membership or role changes can require a code sent by email.
Confirm the resulting role, then periodically remove people who no longer need organization access.
Project-writing roles can change sources, secret metadata, workers, schedules, channels, and API keys. A user who only needs to inspect outcomes should be a Viewer.
Do not use a shared human account for integrations. Create a separately scoped, expiring API key in the project instead.