Docs/Team & roles6 min read

GUIDE

Team & roles with real RBAC.

Invite your team, give each person exactly the access they need, and keep ownership controls locked down — enforced on every API route and socket event.

§ 01Inviting teammates

Invite from Settings → Team with an email and a role. EasyLiveChat sends a single-use link that sets a password and drops the new agent straight into the inbox. You can also invite over the API.

bashInvite an agent over the API
curl -X POST https://acme.livechattools.com/api/tenant/agents \
  -H "Authorization: Bearer $EASYLIVECHAT_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "email": "noor@acme.test", "name": "Noor Al-Saadi", "role": "ADMIN" }'

§ 02System roles

Three system roles cover most teams.

  • Owner — full access, including billing and workspace deletion
  • Admin — everything except billing and destructive workspace actions
  • Agent — handle conversations, with no administrative access

§ 03Granular permissions

Beyond roles, access is a catalog of 34 permissions assigned per agent. Save common bundles as reusable presets.

  • 34 permission keys across conversations, contacts, team, analytics, billing and more
  • Assigned per agent; presets are an optional shortcut
  • Owner-locked keys (roles and billing) cannot be granted away by accident
  • Enforced on both HTTP routes and socket events

§ 04Staying in control

Admins have the tools to manage a real team.

  • Force-logout an agent — revokes their token and drops every device
  • Reset a password or deactivate an account
  • Seat counts are capped by your plan

Was this guide useful?

Suggest an edit ↗