Members and roles
An organization is the unit that owns API keys, usage, and billing. The Members tab on console.mathpix.com controls who can see and change it.
Roles
There are three roles.
| Capability | Admin | Manager | Member |
|---|---|---|---|
| View keys, usage, results, invoices | yes | yes | yes |
| Use the Playground | yes | yes | yes |
| Create an API key | yes | no | no |
| Enable or disable an API key | yes | no | no |
| Configure usage alerts | yes | no | no |
| Invite members and manage invites | yes | no | no |
| Change a member’s role | yes | no | no |
| Remove a member | anyone | members only | no |
The pattern is that anything which can change what you are billed is admin-only — creating keys, turning keys on and off, and setting alert thresholds. Managers help run the roster; members are read-and-use.
Everyone in the organization can read the API keys, including the
app_key values. Treat membership as equivalent to handing out credentials, and prefer separate keys per workload so a single key can be disabled without disrupting everyone.Inviting people
On the Members tab, click Invite Members, enter one or more email addresses, and send. Invitees do not need a Mathpix account first — the invite walks them through signup.
Pending invitations appear in a Pending invites table, where you can Resend invitation or Cancel invitation. Use the email filter to find someone in a long roster.
New members are added with the member role. To change it, open the role dropdown on that person’s row in the Members table.
Removing people
Removing a member revokes their access to the organization. It does not disable any API keys they used, and it does not delete usage history. If someone leaving had an
app_key in their possession, disable or rotate that key as well — see Managing your keys.Who gets alert emails
Usage alert recipients are chosen from the organization roster, per key. Adding someone to the organization does not automatically subscribe them to anything — an admin has to add them to a key’s recipient list. Removing someone does clean up: their address is dropped from the recipient list of every key in the organization.
Because at least one recipient is required to save an alert, check that a key still has someone listed after removing a member who was its only recipient. See Usage alerts.