Teams and roles
Your company's people on orgasm.dev, as Admins, Developers and Billing members. Covers invitations and requests to join, who owns keys and endpoints, rolling keys and webhook secrets, and the activity log.
A company on orgasm.dev is its domain. The first person to sign in with an address at it becomes its Admin. After that, people join only when an Admin lets them in. Credits, API keys, webhook endpoints, live sessions and your own GPUs belong to the company, not to whoever made them, so they stay when someone leaves.
Roles
| Admin | Developer | Billing | |
|---|---|---|---|
| API keys: create, roll, revoke | Yes | Yes | No |
| Webhook endpoints: add, edit, roll the secret, delete | Yes | Yes | No |
| Live sessions and usage | Yes | Yes | Usage only |
| Credits and the balance | Yes | Yes | Yes |
| Prices, costs in dollars, the statement, CSV exports | Yes | No | Yes |
| Billing keys | Yes | No | Yes |
| Your GPUs | Change | Read | No |
| The team | Manage | Read | Read |
| The activity log | Yes | No | No |
A Developer sees how many credits the company has and what each session counted, not what they cost. A Billing member's console opens on Billing; it has no Overview, sandbox or secret keys.
Joining
- Invitations. In the console's Team tab, an Admin invites an address at the company's domain with a role. orgasm.dev emails the invitation link to the address, and the console shows the link too, to send yourself if the email doesn't arrive. The link works for 14 days, and only for that address, whatever its case. The person joins with the role when they sign in with Google or Apple as that address. An Admin can withdraw an invitation until then.
- Requests. Anyone else who signs in with an address at your domain is asked to request to join, and the company's Admins get an email about it. The request waits in the Team tab, where an Admin lets them in with a role or declines; the person gets an email with the answer. Someone declined may ask again.
- Only the domain. Only addresses at the company's domain can be invited or join. Personal addresses (Gmail, iCloud, Hide My Email) cannot sign in at all.
Changing roles and removing people
An Admin changes anyone's role, their own included, and removes members; anyone may leave. The company always keeps an Admin: the last one cannot leave or give up the role until someone else is an Admin.
Removing someone takes effect on their next request. Keys they made stay with the company and keep working, marked with who made them. If the person had a key's secret, roll it. Someone removed can be invited again.
Rolling a key
Every key shows who made it and when it was last used, and any Admin or Developer can roll or revoke any of the company's keys. Rolling makes a replacement with the same name and mode, shows its secret once, and lets you choose when the old key stops working: at once, in an hour, a day or a week. Until then both work. After that the old key is refused with 401, saying when it stopped. Roll from the key's menu in the console, or with rollApiKey:
curl -s https://orgasm.dev/v1/api-keys/key_9d2f5g8h1j4k7l0z3x6c/roll \
-H "Authorization: Bearer $ORGASM_KEY" -H "Content-Type: application/json" \
-d '{ "expiresInS": 86400 }'Rolling a webhook secret
An endpoint's menu edits it (its URL, its events, a description, or pausing it), rolls its signing secret, or deletes it. The API equivalents are updateWebhookEndpoint and rollWebhookSecret. After a roll, the new secret signs every delivery. For 24 hours each delivery also carries a signature made with the previous secret: webhook-signature lists both, separated by a space. Your receiver keeps verifying while you switch it to the new secret. The verifier in the webhooks guide, like any Standard Webhooks library, accepts a delivery when any signature matches.
Billing keys
A billing key (rk_live_…) is for a finance or data system. It reads getCredits, getUsage and listCharges; every other request is refused with 403 permission_denied. It cannot start a session or change anything. Admins and Billing members make billing keys in the Billing tab, and roll and revoke them there.
What the charges carry, and how to break your costs down by your own users and sessions, is in Cost attribution.
The activity log
Admins see the company's last 100 changes in the Team tab, each with who made it and when:
- keys made, rolled and revoked;
- endpoints added, edited, rolled and deleted;
- your GPUs asked for, routed and withdrawn;
- people invited, let in, declined, given a new role, removed, or leaving;
- purges by user reference.
A change made with an API key shows the key instead of a person.