How-to

Invite your team (owner, admin, collaborator)

Last updated: September 8, 2026

An agency console is rarely a one-person job. The Team page lets you bring colleagues into your agency with a role that fits what they do — without them ever creating an agency of their own.

Two rules shape everything on this page:

  • Members never sign up on their own. They enter only through an invite you send. Anyone who registers without an invite gets a brand-new agency, which is not what you want for a colleague.
  • One email, one agency. An account belongs to exactly one agency. If a colleague already owns another GodSetter agency with the same address, the invite cannot be accepted by that account.

The three roles

RoleWhat they can do
OwnerWhoever created the agency. Everything, including managing the team. Cannot be removed or demoted — by anyone, including themselves. There is exactly one owner.
AdminEverything an owner can do, except touching the owner. Can invite and remove members, change their roles and configure collaborators' permissions.
CollaboratorAccess is set area by area by an admin: each area is Disabled, Viewer or Editor, plus a separate Can spend switch. Never manages the team.

Collaborator permissions

The eight areas are the console pages: Calls, Leads, Agents, Clients, Numbers, Connections, Settings, Audit. The Dashboard is always visible; Team appears in the menu only for the owner and admins, and only they can change anything on it.

LevelMeaning
DisabledThe area disappears from the menu; opening it shows "This area is not enabled for you".
ViewerThe area is readable; every change in it is refused.
EditorFull control of the area (create, edit, save, sync…).

Can spend is independent of the areas: it unlocks the actions that cost money — buying a phone number, test web calls and test leads — and it only works together with Editor on the relevant area (Numbers, Agents).

Permissions are enforced on the server: hiding a button is a courtesy, the refusal is the guarantee. A collaborator who somehow reaches a save action on a viewer-only area gets "Your access to this area is read-only: this action requires editor rights (or an admin)."

Step 1 — Send the invite

Open Team in the sidebar (Management section). In the Invite a member card enter the colleague's email and pick Admin or Collaborator — Owner is never an option. For a collaborator the Permissions grid appears: set a level per area (the default is Viewer everywhere) and tick Can spend if needed. Click Send invite.

The invite is refused if the address is already a member, already has a pending invite (use Resend instead), or belongs to the platform operator.

Once created, the page shows "Invite sent to …" and the invite link. The link is displayed only now — it is not stored anywhere, so copy it if you want to share it yourself (chat, another mailbox). If the email could not be sent, the page says so and the link is your fallback.

Step 2 — The colleague accepts

The email carries a link to the invite page, which shows the agency name, the invited address and the role. From there:

  • No account yetCreate an account. The signup form is the usual one minus the agency name (they are joining yours). After confirming their email they land directly on your dashboard.
  • Already has an account → sign in. As soon as they are signed in with the invited address, the invite is claimed automatically.
  • Signed in with a different address → the page explains the mismatch. They must sign out and use exactly the invited email.

For a collaborator the page also lists the areas they will get, with the level of each — so they see exactly what they are accepting.

The invited email is the identity check: the link only delivers the invite, the confirmed email address is what proves who is accepting it. That is also why the address must match exactly.

Invites expire after 7 days.

Step 3 — Manage the team

The Members table lists everyone with their role and join date. For any member except the owner (and except yourself) an admin can:

  • Make admin / Make collaborator — switch between the two invitable roles. Promoting to admin asks for confirmation (they gain full access).
  • Permissions (collaborators only) — opens the same grid used at invite time; Save permissions applies it immediately.
  • Remove — the person loses access immediately.

Pending invites shows what has been sent and not yet accepted, with its expiry and who sent it. Resend revokes the old link and issues a new one (shown once, like the original); Revoke cancels it so the old link stops working. An expired invite is exactly the case Resend is for — only an already accepted or revoked one is refused.

Every action — invite, resend, revoke, role change, permission change, removal, acceptance — is recorded in the agency's Audit log, without ever storing the invite token.

Good to know

  • A removed member who signs in again is treated like any new signup: they get a fresh, empty agency of their own. Re-invite them if that was a mistake.
  • Nobody can change their own role or remove themselves — even the owner. Transferring ownership is not available in this version.
  • A collaborator does not see Team in the menu, but the page itself is readable if they reach it by URL — they simply cannot change anything: every control is hidden and every action is refused server-side.