Invite your team and set roles

Users are managed per instance in Settings → Users, and every user signs in with their own individually invited credentials — shared logins break the audit trail and are not supported. Unlimited seats are a console feature available on every instance regardless of connection state, so there's no cost reason to hold back on inviting your full team.

Unlimited seats, on every instance

Unlimited user seats are a console feature included on every instance, whether or not you take the optional $50/month Arino Core connection. Whether you have three agents or thirty, the cost of seats doesn't change — there is no per-seat or per-agent fee. This is a deliberate design choice: teams often need to flex headcount around seasonal volume or shift work, and per-seat pricing would penalise exactly that flexibility. What does scale with your team's activity is message and conversation volume, billed through your own Infobip account and covered fully on billing and plans. The separate $50/month connection is optional and covers Arino support, management, updates and WebRTC — it has nothing to do with how many seats you can use.

Roles

Assign the narrowest role that lets someone do their job. Most day-to-day team members should be Agents; reserve Administrator for the small group who configure channels and manage other users.

Why unlimited seats matters in practice

Many messaging platforms price per agent seat, which pushes teams towards sharing logins during busy periods to avoid an extra charge — exactly the behaviour that breaks accountability and makes an incident harder to investigate. Because seats in Arino One never carry a per-user cost, there's no financial pressure to under-provision access: bring on seasonal support staff, give every supervisor their own login, and remove people the moment they leave, without checking a seat count first.

Steps

1. Go to Settings → Users in the console.
2. Select Invite user and enter a work email address.
3. Pick a role and the specific inboxes or teams that person should see — access can be scoped per channel or team, not just per role.
4. Send the invitation. The recipient sets their own password on first sign-in and appears in the user list as pending until they do.

Scoping inbox access

Beyond role, you control which channels and teams each user can actually see. Give agents access only to the inboxes they work in: the CDP contact record surfaces personal data alongside every conversation, so narrower access limits exposure without limiting anyone's ability to do their job.

Keeping the user list current

Review the user list on a regular cadence — quarterly is a reasonable default — and remove people who have left or changed role. This review doubles as evidence for your access-control controls if you're ever asked to demonstrate one, and it's recorded in the instance's audit and evidence trail regardless of connection state.

Handling role changes

When someone changes team or leaves an inbox, update their access immediately rather than at the next quarterly review — a supervisor moved to a new team should lose visibility of the old team's contacts the same day, not weeks later. Editing a user's role or inbox access takes effect immediately and doesn't require a new invitation.

Notifying new users

Invited users receive an email with a sign-in link; if it does not arrive within a few minutes, check spam before resending, since resending too quickly can invalidate the first link.

After inviting your team

With users in place, connect a channel if you haven't already and send a test message to confirm everything end to end — see send your first message.

Steps at a glance

1. Open user settingsIn the console go to Settings → Users.
2. Invite by emailSelect Invite user, enter the work email address of each team member, and choose a role.
3. Assign inbox accessChoose which channels and teams each user can see and reply on, so agents only access what their role requires.
4. Confirm the invitationThe user receives an email invitation and sets their own password on first sign-in.
5. Review access periodicallyCheck the user list on a regular schedule and remove leavers promptly; this review is your evidence for access-control audits.

Frequently asked