Account & Team
User roles & permissions
Everyone you add to your Pendra organisation is either an owner or a member. Both roles can send API requests and run inference on every model your workers serve — the difference is administration. Owners manage the organisation itself: who's on the team, billing, and the workers and models behind your endpoints. Members get the same day-to-day access to inference and usage, without those admin controls.
What each role can do
| Action | Owner | Member |
|---|---|---|
| Send API requests / run inference on any endpoint | ✓ | ✓ |
| Create and manage your own API keys | ✓ | ✓ |
| View workers, installed models, and usage | ✓ | ✓ |
| View organisation name and team members | ✓ | ✓ |
| Invite or remove members, and change their roles | ✓ | — |
| Rename or delete the organisation | ✓ | — |
| Manage billing and your plan | ✓ | — |
| Add workers and install, remove, or configure their models | ✓ | — |
| Create or revoke worker connection keys | ✓ | — |
| Require end-to-end encryption for the organisation | ✓ | — |
API keys belong to the organisation, but each member manages their own: members can create keys and revoke the ones they created, while owners can revoke any key in the organisation.
Changing a role
An owner changes a teammate's role from the console under Settings → Members. The new role takes effect the next time that person signs in or switches into the organisation.
Every organisation keeps at least one owner, so you can't remove or demote the last remaining owner. Promote someone else to owner first if you need to step down.