Invite Your Team

Bolti is built for collaboration — designers test agents, engineers wire up tools, and ops folks read call logs, all in the same workspace. This page covers how to add the right people with the right level of access, and how to manage that access over time.

If you haven't read Workspaces & Organizations yet, do that first — the role model only makes sense once you understand the two levels.

Where to invite from

All membership management lives under:

Settings → Members

You'll find three things on that page:

1. An invite form at the top (only visible to org Admins and the Owner)
2. Pending invitations — invites that have been sent but not yet accepted
3. Members — everyone currently in the organization, with their role

Only org Admins and the Owner can send invites or remove members. Editors and viewers can be added to workspaces but can't grow the team themselves.

Sending an invite

The invite form takes three inputs:

Field	What it does
Email	The address to send the invitation to. Doesn't have to be the address they'll sign in with — though it usually is.
Role	Member (default — no special privileges) or Admin (full org access except billing transfer). The Owner role isn't assignable here; ownership is transferred separately.
Workspace	Either All Workspaces for an org-level invite, or pick a specific workspace to scope them to just that one.

Click Send Invite. Bolti emails the invitee a tokenized link.

Org-level invites vs workspace-scoped invites

This is the most common point of confusion, so worth being explicit:

• All Workspaces (org-level) — the user joins the organization and gets your default level of access across every workspace in it. Use this for full-time team members.
• Specific workspace — the user joins the organization but only has access to that one workspace. Use this for clients (when you're an agency), contractors, or anyone who should see only one slice of your account.

You can always upgrade or move someone later by adding them to additional workspaces from Settings.

What the invitee sees

The invitee receives an email with a button that opens a sign-up page at /invite/<token>. There they:

1. Confirm the email shown on the invite (you sent it; they can't change it).
2. Choose a name.
3. Set a password (Bolti enforces 8+ chars, mixed case, a number, and a special character).
4. Click Accept Invite.

That's it — they land in the workspace you invited them to, signed in.

If the invitee already has a Bolti account on the same email, the link signs them in and adds the new org/workspace to their account. They don't have to re-register.

Google sign-in works too

If your invitee prefers Google, the email on their Google account just needs to match the invited address. Bolti links the methods automatically.

Managing pending invitations

Until the invitee clicks Accept, the invitation sits in the Pending Invitations list. From there you can:

• Copy the invite link — useful for sharing in Slack/email if they didn't get the original email or you want to send it through a different channel.
• Resend the email — re-sends the original invitation email (link/token unchanged).
• Revoke — instantly invalidates the invite. Useful if you sent it to the wrong address or changed your mind.

Pending invitations also show:

• The email (or "Link invite" if you generated a shareable link without a target email).
• An expiry date — invites expire after a fixed window. Resend creates a fresh email but the underlying token's expiry date still applies; revoke and re-invite if it's already expired.
• The role that will be assigned on accept.
• The workspace tag if it's scoped, or no tag for org-level invites.

Removing a member

Open Settings → Members, find the person in the list, and click the X icon next to their role. Confirm in the dialog.

A few things to know:

• Only the Owner can remove members. Org Admins can invite people in but can't remove them.
• The Owner cannot be removed. To change ownership, the Owner has to transfer it first (see below).
• Removing a member from the org instantly revokes their access to every workspace in the org. Their personal Bolti account isn't deleted — they can still belong to other organizations.

Transferring ownership

Each org has exactly one Owner, and only that person can:

• Delete the organization
• Transfer ownership to someone else
• Manage billing details that are owner-locked

To hand off the Owner role, the current Owner promotes another existing org member. The new person becomes Owner; the previous Owner stays in the org as an Admin (unless explicitly removed afterwards). Useful when someone leaves the company or hands off a project.

Common patterns

Solo founder

Just you. Skip everything on this page. Come back when you hire someone.

Small team, one product

Org members:
  Founder       → Owner
  Engineer 1    → Admin
  Engineer 2    → Admin

Workspaces:
  production    (everyone has access)

Single workspace, everyone is org Admin. Simplest possible setup that works for a team.

Small team, separate prod & staging

Org members:
  Founder       → Owner
  Engineer 1    → Admin
  Engineer 2    → Admin
  PM            → Member

Workspaces:
  production    → Founder + engineers (Admin); PM (Viewer)
  staging       → everyone (Editor)

Engineers iterate freely in staging. PM watches calls in production but can't break anything. Org Admins can promote a working agent into production themselves.

Agency with multiple clients

Org members:
  You (Owner)
  Account manager     → Admin
  Voice designer 1    → Member
  Voice designer 2    → Member
  Acme contact        → Member  (workspace-scoped)
  Globex contact      → Member  (workspace-scoped)

Workspaces:
  client-acme         → designer 1 + Acme contact (Viewer)
  client-globex       → designer 2 + Globex contact (Viewer)
  internal            → just you and the AM

Each client only sees their own workspace. Designers focus on the client they're assigned to. The AM sees everything.

Enterprise team with multiple departments

Org members:
  Engineering lead    → Owner
  Finance            → Billing
  Engineers (×N)     → Admin
  Stakeholders (×N)  → Member  (workspace-scoped to their dept)

Workspaces:
  support-bot
  outbound-sales
  recruiting

Finance has the Billing role — they can pay invoices and top up credits but can't see agents or calls. Each department's stakeholders get scoped read access to their workspace.

Audit & visibility

• Every invitation records who sent it (invited_by) and when.
• Every workspace member record stores created_at so you can see when someone joined.
• Org Admins and the Owner can see the full Members list at any time.

If you need richer audit trails for compliance (full action logs, login history, etc.), reach out — that's something we expose for enterprise plans.

Done

That's the full team-management surface. You now have:

• An organization with the right people in it
• The right per-workspace scoping for collaborators and clients
• A clear path to remove access or transfer ownership when things change

You've finished the Getting Started section. From here, the natural next stops are:

• Agent Setup → to dial in your agent's behavior, voice, and transcription
• Tool Calling → to give your agent the ability to take action mid-conversation
• Calling → when you're ready to start placing real phone calls