Team & roles

Invite the staff who work your inbox and callback queue, and give each person the right level of access. Four roles — owner, admin, member, and viewer — decide what someone can see and do.

At a glance

Four roles: owner, admin, member, and viewer, from full control to read-only.
Invite by email; people you add are the ones who receive callback alerts and work the queues.
Least privilege by default — give each person only the access their job needs.
The owner role is protected and controls billing and the account itself.

The four roles

Access is role-based, so you can hand a new front-desk hire the queue without handing them your billing. Each teammate has exactly one role.

SpiderLabs dashboard roles and what each can do
Role	What they can do
Owner	Full access, including billing and deleting the organization. The owner role is protected.
Admin	Manage members and settings, and view all data across the account.
Member	View and respond to the calls and callbacks they work — the everyday front-desk role.
Viewer	Read-only access to calls and contacts, with no ability to change anything.

Give the least access that does the job

A good default: the practice owner or manager is the owner or an admin, front-desk staff are members, and anyone who only needs to look — a consultant or biller — is a viewer.

Inviting staff

Owners and admins can invite teammates from the Team area of the dashboard.

Send the invite
Enter the teammate’s email and choose their role. They receive an invitation to join your account.
They accept and sign in
The teammate creates their sign-in and lands in your provider-neutral dashboard, scoped to your account only.
They start working the queue
Members and above can see the inbox and work the callback queue right away.

Who gets notified

The people you add to the team are the people who receive callback alerts and work the follow-up queues. That is why keeping the team list current matters: a new callback should reach someone who can act on it. See Callback queue for how alerts fire and Analytics for the optional weekly summary.

Changing & removing access

Roles are not permanent. Owners can manage everyone (except other owners), and admins can manage members and viewers — so you can promote a trusted teammate, or remove access the moment someone leaves. Because each person is a distinct account with an audited action trail, you always know who did what.

Access changes matter for compliance

Keeping your team list accurate — removing people who have left, granting only the access each role needs — is part of a sound patient-data posture. Isolation and audited access are covered in Security & compliance.

Keep exploring

Your dashboardA tour of your dashboard: one inbox for calls and chats, transcripts and recordings, the callback queue, appointments, tasks, analytics, team, and notifications.Callback queueThe callback queue as a workflow: how requests are captured, prioritized, worked, and completed, and how staff are alerted so nothing sits unseen.Security & complianceWhat a compliance reviewer needs: the BAA process, audited access to patient data, our data-handling posture, and the live-PHI activation gate.