Team and roles

Support is rarely a solo job. Invite the people who answer, decide what each of them can reach, and keep the keys with the people who should hold them.

Where it lives

Team in the workspace sidebar, or /workspaces/:id/members. Only owners see it — managing who can read your conversations isn't something an agent should be able to do.

The two roles

Doorwick has two, and the split is deliberately blunt: agents run support, owners run the business.

Agent
The inbox and everything needed to work it — knowledge, canned replies, and analytics. This is the role for anyone whose job is answering people.
Owner
Everything an agent has, plus the things that carry a liability: AI provider keys, widget settings, site keys and origins, the signing secret, billing, Shopify, the conversation export, and this page.

Roles are per workspace, not per account. The same person can own one workspace and be an agent in another; the sidebar shows each one what it's allowed to reach.

An agent isn't shown the settings they can't use, and the server refuses them regardless of what the page offers — so a bookmarked link or a hand-rolled request gets the same answer the missing menu item implies.

Inviting someone

  1. Open Team and enter their email address.
  2. Pick a role. It defaults to agent, which is the one most people should have.
  3. Send it. They get an email naming you, the workspace, and the role, with a link that lasts seven days.

They don't need a Doorwick account first. If they have one, the link signs them into the workspace; if they don't, they choose a password on the invitation page and land straight in the inbox. Either way the account uses the address you invited — no new workspace, no second subscription.

Pending invitations

Everything you've sent and nobody has taken up yet is listed under the members, with who sent it and when it expires. Revoke deletes it, and the link in the email stops working immediately — useful if you typed the wrong address.

Expired invitations drop off the list on their own. To re-invite someone, just send a new one.

Changing a role, and removing people

Every member row has a role dropdown and a Remove button (Leave on your own row). Changes take effect immediately: an agent promoted to owner sees the settings links appear on their next page load, and a removed member loses access to the workspace at once.

The last owner can't be demoted or removed. A workspace with no owner is unreachable — nobody could manage the team, the billing, or the keys ever again. So the controls are withheld on the final owner's row. Promote somebody else first, then leave.

Public identity in the widget

Workspace access and public team presence are separate decisions. A member can work conversations without appearing to visitors, and joining the workspace never publishes their email address or account details.

  1. Open Team, find the member, and choose Edit public identity.
  2. Set the human-readable name visitors may see. Upload an optional PNG or JPG avatar; without one, Doorwick shows the person’s initials.
  3. Open Widget → Team presence, turn the feature on, and select the members to show.
  4. Review the overlapping avatar stack in the live preview, then save.
Selecting somebody makes their configured display name and avatar public on every allowed website that serves this widget. Doorwick never substitutes their email address in the visitor experience.

A selected member represents someone on the support team, not someone who is online right now. The workspace status text and office hours continue to describe availability. Removing a member or turning off their selection removes them from the widget.

What it costs

Nothing per person. Doorwick is one price per workspace with every operator included, so invite the whole team — there's no seat count to watch and no reason to share one login.

Choosing roles well

  • Default to agent. Most people never need to touch a provider key, and an agent can still do the whole support job.
  • Keep at least two owners. One owner is a single point of failure — if they leave the company, nobody can manage the workspace.
  • Remove people when they leave. An agent can read every conversation in the workspace, which is exactly as sensitive as it sounds.

Next