← All posts

Members: invite your team with a link, not a mail server

Vocion deployments are multi-user from day one — a Members page to see everyone, manage roles, and mint one-time invite links that need zero email infrastructure.

Vocion Teamvocion-v1.51.0

An agent platform is a team surface: the review queue only makes sense if the right humans can get to it. Until today, adding a second person to a Vocion deployment meant a database insert. Now it's a page.

Members

Dashboard → Settings → Members lists everyone in the account — name, email, role, join date. Admins change roles and remove members inline; members see the roster read-only. The server enforces the two rules that keep you out of lockout territory: no removing yourself, and no demoting the last admin.

Invites without a mail server

Most products bolt invites onto an email dependency, which means a fresh self-hosted deployment has broken invites until someone configures SMTP or an API key. We inverted it:

  1. Invite member → email + role → Vocion mints a one-time link.
  2. Copy the link and share it wherever your team already talks — Slack, DM, a sticky note.
  3. The invitee opens it, sets a password, and lands in the dashboard with the right role.

Each link is bound to the invited email, single-use, and expires in 14 days. Re-inviting an address revokes the old link and mints a new one. Pending invites sit on the same page with copy and revoke controls. If you wire up a mailer later, the token flow doesn't change — email becomes a transport, not a dependency.

Also in this release

Docs: Members.