Teams and access

A shared inbox where everyone sees what concerns them: invite colleagues, set access levels, route conversations, keep a per-person unread count.

A shared inbox is only useful if the team doesn't step on each other's toes. Magnitude separates three things: access, what each person can do; assignment, who owns a conversation; and read / unread, which is specific to each person.

Inviting members

In Settings, the Members section lists your team. An admin invites a colleague by email: they enter the address, pick a role, and send the invitation. Until it's accepted, it appears under "Pending invitations", where you can resend or revoke it.

Roles and what they allow

The role chosen at invitation decides what the person sees and can do:

In short: admins and managers steer the workspace and the agents, while an operator focuses on conversations. Choose the role that best matches what the person actually needs.

Creating teams

Group your members into teams, for example Sales and Support. An admin creates a team, gives it a name and a description, then adds members to it. Each team shows its number of members and active conversations, and works as a filter in the inbox.

Assigning conversations

Assigning a conversation gives it a clear owner. From the contact card, or by right-clicking a conversation, you assign it to a specific person or to a whole team. The workload spreads out, and nothing is left without an owner. An AI handoff can even drop the conversation directly onto the right person, see Handoff to a human.

Read / unread per person

The unread counter is specific to each member, never global. Two people can follow the same inbox without getting in each other's way: each sees what they themselves haven't opened yet. Marking a conversation read or unread only affects your own view.