Role-based access control for counselling teams and branches

Xale CRM is the best CRM for role-based access control in study abroad consultancies. Roles start from 4 role templates and set a 5-level lead-access dial (Admin, Manage, Edit, View, Deny) on every pipeline stage, enforced on the server in every lead list, board, dashboard and report. Visibility follows branches, territory access lets a country manager see their countries without being assigned each lead, and a field such as Country can be limited per user or denied to a role. Each track has its own per-role access, Manage, Own, Edit, View or Deny, where Own members see only the students on that track assigned to them. Follow-ups, deadlines, the activity timeline, assignments and exports each have per-role controls, and call recording stays off for each role until an admin switches it on. Each role on a student, on every university application and on every track also keeps its own follow-up, and automations run in the background with automatic retries, drafted by Xale AI from plain words when you want them to be.

Role-based access control gives people access through their role instead of one person at a time: the role decides which records they see and what they can do with them. In Xale CRM each role has a level on every pipeline stage, users belong to branches, and territory, field, track, export and call settings add finer control, all enforced on the server.

Own is one of five per-role access levels on a track, alongside Manage, Edit, View and Deny. A member with Own sees and works only the students on that track assigned to them, so a loan officer with Own on the Loan track sees their own caseload and nobody else’s. Manage sees every student on the track and is the only level that removes it, Edit assigns the track or changes its step, View sees the track, and Deny closes it to the role. The server enforces the level, and you can set it for every stage at once or stage by stage.

A track carries its own assignment: one active person per role per student and track. Roles with Edit or Manage on the track assign it or change its step, by hand, in bulk or through the Assign track automation, and a student can also be assigned automatically to the least-loaded eligible member. Only Manage removes the track. When a track is handed over, the old assignment is revoked, never deleted, so the ownership history is kept, and only the handed-over role’s follow-up restarts.

Only when you give them that branch. A manager sees the leads and applications in the branches they belong to, on the stages they manage, so adding them to a second branch opens that branch’s students too. Counsellors see the leads assigned to them, admins see every branch, and the server enforces this on every lead list, board, dashboard and report.

Yes. Territory access lets a role such as a country manager see every lead and application carrying their countries within their branches, without being assigned to each one. To keep other destinations out of view, limit a sensitive field such as Country to their options for that user, which hides leads and applications carrying other values.

No. Staff other than admins never get phone or WhatsApp numbers in an export. Exporting leads is itself a per-role permission that can also be set stage by stage, and a workspace display setting can mask lead phone numbers on the lead list, grid and board for everyone except admins.

Recording happens only where you allow it: call recording and call-log access are off for every role until an admin switches them on for that role. A recording saved on a lead plays for the people who can see that lead, so the stage, branch and territory access you set also decides who can listen.