Team & Roles

Roles

Every member holds exactly one role per organization. The same person can be an Owner of their own organization and a Developer in yours — roles do not carry across.

Owner is the account holder: one per organization, and the only role that can never be removed or demoted. Admin runs the team and the keys but cannot spend money. Developer is the day-to-day integration role — full control of API keys, including creating, rotating and revoking them, but no access to billing or members. Billing is the mirror image: it can top up, manage the payment method and download invoices, but cannot touch keys or people. Viewer is read-only.

The Playground follows key access rather than its own permission, because the calls it makes are real and billed to the organization. Roles that cannot hold a key do not see it in the sidebar.

Inviting someone

Owners and Admins can invite from Organization → Members. You enter an email address and pick a role, and we email them a single-use invitation link that expires after 7 days.

1. The invitation names the organization, who invited them, and the role they will get.
2. Clicking the link does not sign anyone in.
3. If they already have a Renidly account, they confirm with their existing password. If they are new, they set a name and a password there and then.
4. Once accepted, they appear in your Members list and the invitation is spent.

Pending invitations are listed alongside your members. You can resend or revoke one at any time before it is accepted; revoking takes effect immediately, even if the email has already been delivered.

What a new member gets

• Access to your organization at the role you chose — shared keys, shared balance.
• Their own login. They are never given your password or a shared account.
• Their own empty personal organization, so removing them from yours never leaves them locked out of Renidly entirely. It receives no free credits.

Removing access

Removing a member takes effect on their next request — there is no grace period. Keys they created keep working, because keys belong to the organization rather than the person. If you need those keys gone as well, rotate or revoke them from API Keys.

Members can also leave on their own from Organization → Settings. The Owner cannot leave, since an organization must always have someone who can administer it.

Activity log

Owners and Admins can see recent invitations, role changes, removals and key actions under Organization → Activity, with who did what and when. It is useful for answering “when did this key change?” during an incident.