Invite your team and keep roles clear
Add admins, operators, and viewers with the least access they need to do their work.
Open Team to see who belongs to the organization. The members table shows names, roles, current status, recent activity, and active conversation counts before you change access.
Use the smallest useful role
An Operator works with conversations. An Admin can also manage the team, settings, and billing. A Viewer has read-only access to the operational areas marked in the permission matrix lower on the Team page. Start with the narrowest role that supports the person's work.
Send an invitation
Choose Invite Operator to open the form. Enter a Display Name, the person's work Email Address, and their Role. The screenshot uses a fictional operator in an isolated Convor workspace. Check the recipient before sending an invitation with organization access.
Set workload, timezone and skills
Use Max Concurrent Chats to limit how many conversations an operator can handle at once. Enter a number from 1 to 100, or leave the field blank for no explicit limit. Choose the person's Timezone. For a TopSoft4U support team in Warsaw, use Europe/Warsaw.
Enter Skills individually, such as billing and api. Skills-based routing matches them against conversation tags. Accepting new conversations controls whether the operator can receive additional work. Review this switch when onboarding someone who should observe conversations before taking assignments. Routing rules still determine which conversations qualify for assignment.
Check the role before sending
The role selector makes the access decision explicit. Review the permission matrix when the choice is unclear. If a teammate later needs broader access, edit the role from the team table instead of sharing an administrator account.
Invite operators through the API
A TopSoft4U personnel system can invite teammates through POST Invite an operator to the organization. Confirm each person's role before granting access to customer conversations. Use List operators and their status to check who already belongs to the organization.
If an operator cannot see the expected conversations
Check the person's role under Team, then verify the selected site. Organization membership and access to particular workspace areas are not interchangeable. If a teammate can view a case but cannot assign it, compare the role with the permission matrix. Sharing an administrator account is not a workaround.
When responsibilities change, also inspect the person's open conversations and your routing rules. Removing access before handing over a live case can leave the receiving team without useful context.
Remove access promptly
When someone leaves the team, remove their access on the same day. Review the member list regularly and reassign their open conversations before removal when needed.
Was this page helpful?