Team Members

Team Members adds staff accounts to your dashboard. Without it, your platform has one operator. With it, you can give each person exactly the areas they need and nothing else.

Find it at Settings > Members once the add-on is active.

Role presets

Start from a preset. They are built around real jobs, and you can narrow one further with a custom role if you need to.

Owner and Admin are the built-in full-access roles. They are not offered as presets because you should not be handing out full access casually.

Permission groups

Custom roles are built from these groups, so you can see at a glance what any role touches.

Inviting someone

1. Open Settings > Members and select the invite action.
2. Enter their email.
3. Pick the preset that matches their job, or select an existing custom role.
4. Review the permission list shown before you send. It is the fastest way to catch an over-broad choice.
5. Send the invitation. They set their own password when they accept.

Start narrow. Widening a role later is a two-minute change; discovering someone had payout access for six months is not.

Custom roles

Use a preset unless one genuinely does not fit. When you do need a custom role:

1. Start from the closest preset rather than an empty list.
2. Remove what they do not need instead of adding one permission at a time.
3. Name it after the job, not the person.

Roles marked protected cannot be edited, which keeps the presets intact as a reference point.

Guardrails

The system prevents the mistakes that lock you out of your own platform:

• The last owner or admin-capable member cannot be removed.
• You cannot demote yourself if you are the last admin-capable account.
• Roles are always scoped to your own organization.
• A duplicate active invitation is blocked until the existing one is cancelled or accepted.

Audit

Every invitation, role change, suspension, removal, and permission update is recorded. Check it after any access change, and during any offboarding.

Using the Members API

Member endpoints require both Team Members and the Enterprise Delivery API add-on to be active. If only one is active, those endpoints return an add-on access error even with a valid credential.

In API requests, use the documented preset values and the permission keys returned by the member permissions endpoint. The names in the table above are display labels.

Common questions

Does a member count as one of my customers? No. Staff accounts and customer accounts are separate.

Can a member see other organizations? No. Roles are scoped to your organization only.

What happens if I deactivate the add-on? The Members area leaves the sidebar. Existing staff accounts and roles are retained, so reactivating restores them.

Someone left the company. What do I do? Suspend or remove them in Members, then check the audit trail for anything they changed recently. If they held API credentials, rotate those too.