Give engineers access to integrations, finance teammates access to billing, and other teammates a read-only view. Roles apply within each organization, so the same person can have different responsibilities in different teams.
Roles
| Role | Best for |
|---|---|
| Owner | Trusted administrators who manage team access, billing, and every resource. |
| Developer | Engineers who operate integrations, API keys, Managed Subgraphs, and Endpoint Aliases. |
| Billing admin | Finance or operations teammates who manage plans, payment, invoices, and alerts. |
| Viewer | Teammates who need visibility without change access. |
Your role applies equally to the platform, direct API requests, and authenticated support reads. API key records are available to owners and developers. Billing details, credit history, and billing preferences are available to owners and billing admins. Only owners can see team membership and invitation lists. Every member can see usage and technical resources, plus the plan name, remaining credits, and active-key count on Overview.
Choose the narrowest role that covers each person's work. Custom roles and a separate admin role are not available: use the owner role for team administration and the billing admin role for payment responsibilities. The person who creates an organization becomes its owner.
Invite a teammate
- As an Owner, open Organization → Invitations.
- Invite the teammate by email and choose the least-privileged role that matches their job.
- Tell the recipient which organization they are joining and which email you used.
- The recipient signs in with the invited email, verifies it if needed, and accepts the invitation. Creating an account alone does not accept it.
Check the email address before sending. If the role or recipient is wrong, revoke the pending invitation and send a new one; expired, accepted, and revoked invitation links cannot be reused.
Update or remove access
Owners can change roles or remove members from Organization → Members. Review access before sensitive work begins and whenever someone's responsibilities change.
When you remove someone who had access to API key secrets, rotate or revoke the keys they could have copied. Removing a member does not revoke the keys they created.
When your own role changes while the dashboard is open, the next refresh verifies your membership and updates the pages you can use. You remain in the organization; a page outside your new role returns to Overview.