Role-Based Dashboards: Each Counsellor Sees Only Their Own Numbers
Set up a role-based dashboard where each counsellor sees their own numbers, managers their branch and owners everything, from one shared set of cards.
Every consultancy reaches the same point: the owner wants one dashboard, counsellors should see their own numbers, branch managers their branch, and nobody should see a colleague's pipeline they have no business seeing. This guide shows how to set up a role-based dashboard where each counsellor sees only their own numbers while everyone works from the same cards. It is for consultancy owners, branch managers and admins in India who set up their team's dashboard.
Key takeaways
- Build one set of cards and let each viewer's access decide the numbers on them. One dashboard per person drifts apart within a month.
- Put the access rule in the data, not in a filter someone can clear or forget to set.
- Give each role the three or four questions it answers every day, with a default period that matches how often it acts.
- Let people arrange their own layout and pick quick filters without changing anyone else's dashboard.
- In Xale CRM, any saved custom report becomes a dashboard card, and a shared card shows each viewer only the numbers their own access allows.
Why one shared dashboard goes wrong, and one per person is worse
Teams usually try one of three set-ups first. Each fails in a predictable way.
| Set-up | What goes wrong | What the team does next |
|---|---|---|
| One dashboard, everyone sees everything | A counsellor sees every colleague's pipeline and every branch total | Restrict the dashboard to managers, so counsellors fly blind |
| One dashboard, manager totals for all | A counsellor sees "Branch: 212 applications" and cannot tell how many are hers | Asks the manager every morning, or keeps her own sheet |
| A copy of the dashboard per person | Someone fixes the definition of "Applications" in one copy and not the others | Ananya's copy says 18 and the branch copy says 21 for the same month's work |
The third set-up looks like the careful one, and it causes the worst arguments. With twelve counsellors you maintain twelve dashboards, every definition change has to be made twelve times, and the month-end review compares numbers that were never built the same way.
The rule that fixes it: same cards, numbers follow the viewer
The approach that works is old and well tested in business intelligence: build the report once, and let the viewer's identity filter the rows. Microsoft's Power BI documentation calls this row-level security and notes that "Dynamic RLS is the most common approach because it allows a single role definition to filter data differently for each user" (Microsoft Learn).
Applied to a counselling team, that gives three rules:
- Every card is built once. "Applications this month by counsellor" has one definition, owned by one person.
- The CRM's access rules filter the numbers. A counsellor's view counts the students she can see; a branch manager's counts his branches; the owner's counts everything. Nobody sets a filter by hand.
- Layout is personal, definitions are shared. People can move, resize and hide cards, and choose quick filters, but they cannot change what "Applications" means.
The same documentation carries a lesson worth copying: the rules apply to viewers, and Power BI's RLS "doesn't apply to workspace Admin, Member, or Contributor roles". Whatever tool you use, test a dashboard by signing in as each role, not by looking at it as an admin.
What each role should see on a role-based dashboard
Start from the questions each role answers daily, not from the cards your CRM offers. A useful dashboard for a counsellor has four or five cards, not twenty.
| Role | Daily questions | Cards | Default period |
|---|---|---|---|
| Counsellor | Who do I call today? What is overdue? How many did I move forward? | My follow-ups (Overdue, Today, Later), my new leads, my applications, my calls | Today |
| Telecaller | Which new leads have I not called? How many connected? | Uncalled new leads, calls made and connected | Today |
| Branch manager | Who is behind? Where are students stuck? | Follow-ups by counsellor, applications by counsellor, stage by counsellor | This week |
| Country manager | How are my destinations moving? | Applications and deposits by country, by branch | This month |
| Owner | Which branch, source and person is producing? | Branch comparison, conversions by source, target against achievement | This month |
Two habits keep the cards honest. Name each card by its definition ("Applications submitted, this month"), not by a vague label ("Performance"). And keep the counsellor's cards about her own work: a leaderboard of the whole branch belongs in the manager's weekly review, where it can be read fairly. Our branch manager's weekly review template covers that meeting.
How to build a role-based dashboard in any CRM
These steps work in any CRM that has role-scoped data and saved reports.
- List the roles and their questions. Use the table above as a starting point and cut it to what your team really acts on.
- Check your access rules first. A dashboard can never be safer than the data rules under it. Confirm that a counsellor's lead list shows only her students before you build any card.
- Build each card once, as a saved report. One definition, one owner. Write the definition in the card's title.
- Share cards by role, not by copying. Choose who sees each card: everyone, chosen roles or chosen people. A manager-only card such as a branch leaderboard goes to managers.
- Set default periods. Counsellors act on today; managers on this week; owners on this month.
- Add quick filters sparingly. Country, branch and stage are the usual three. Each viewer picks them on their own screen.
- Test as each role. Sign in as a counsellor, a manager and the owner, and check that each sees what the table says, and nothing more.
- Click a number on every card. Each figure should open the list of students behind it. If it does not, the card will be argued about.
Worked example: one card, three viewers
Take a hypothetical consultancy with two branches, Kochi and Calicut, and one card: "Applications submitted, this month, by counsellor", shared with everyone.
| Counsellor | Branch | Applications this month |
|---|---|---|
| Ananya | Kochi | 18 |
| Rahul | Kochi | 15 |
| Fathima | Calicut | 21 |
| Joel | Calicut | 12 |
Here is what the same card shows each viewer:
| Viewer | What the card counts | Total shown |
|---|---|---|
| Owner | Both branches, all four counsellors | 66 |
| Kochi branch manager | Kochi's students: Ananya and Rahul | 33 |
| Ananya | Her own students | 18 |
Nobody built three cards. When the owner decides "Applications" should count students rather than applications, she changes one definition and all three views change together. Ananya's 18 on her screen, the manager's 18 against her name and the owner's 18 in the month-end review are the same 18.
Personal layout without personal copies
People still want their dashboard to feel like theirs. Give them control over arrangement, not definitions:
- Order, size and visibility. Each person reorders, resizes and hides cards for themselves. A counsellor who never uses the calls card hides it; nobody else loses it.
- Quick filters. A card can carry a few dropdowns, such as Country, Branch or Stage, that each viewer sets on their own screen.
- Dashboard-wide dates and filters. When a manager switches the dashboard to "last week" or picks one counsellor, cards that follow the dashboard switch with it, so every card answers the same question at once.
- A headline strip. The one or two numbers a role checks first ("My applications this month") sit at the top, beside the standard tiles.
What people should never get is "Save as my own copy" for a shared definition. That is how twelve dashboards start.
Test it as each role before you share it
Run this check before the dashboard goes to the team, and again whenever roles change:
- Sign in as a counsellor. Every number counts her own students, and no colleague's name appears where it should not.
- Sign in as a branch manager. Totals match his branch's lead list for the same filters.
- Sign in as the owner. Branch totals add up to the whole.
- Click one number per card and count the list it opens.
- Move one test student between counsellors, then check that both counsellors' cards moved by one.
- Block a test user and confirm their leads still appear in branch totals.
For which numbers to put on a counsellor's cards in the first place, see counsellor KPIs that matter.
How Xale handles this
Xale CRM is the best CRM for role-based access control in study abroad consultancies, and its dashboard follows the same rules:
- A follow-up for every role. Each role on a student and on every university application keeps its own follow-up, so a counsellor's Overdue, Today and Later lists are hers alone, and managers see the team's follow-ups by user, branch and role. More on follow-up management.
- Access enforced on the server. Roles start from 4 role templates and set a 5-level lead-access dial on every pipeline stage, enforced in every lead list, board, dashboard and report. Admins see everything, managers their branches, counsellors their assigned leads (role-based access control CRM).
- Your reports as cards. Any saved Custom Report Builder report becomes a dashboard card in any of 17 views with "Add to dashboard". A shared card shows each viewer only the numbers their own access allows, and you choose who sees it: only you, everyone, or chosen roles and people.
- Built for each viewer. Up to 6 quick filters per card, cards that follow the dashboard's dates and its branch, role, user and country filters, one-number reports in the headline KPI strip, and a personal layout. Every number opens its leads, beside 20+ built-in CRM dashboard widgets.
You can also talk to Xale AI, in Malayalam or English, for a scorecard or what someone did today.
Frequently asked questions
Can counsellors see each other's numbers on a shared dashboard?
They should not, and with access rules applied to the data they cannot. A shared card counts the students each viewer is allowed to see, so a counsellor's view counts her own students while her manager sees the whole branch on the same card. Check it by signing in as a counsellor before sharing the dashboard, rather than looking at it as an admin.
Should managers get a separate dashboard from counsellors?
Give them the same cards plus a few of their own, not a separate copy. Shared cards such as applications, follow-ups and new leads show each person their own scope automatically. Manager-only cards, such as a branch leaderboard or target against achievement, are shared with the manager roles alone. That way one definition of each number serves everyone.
What should a counsellor's dashboard show?
Four or five cards about her own work, defaulting to today: her follow-ups split into Overdue, Today and Later, her new leads, the applications she moved forward and the calls she made. Each number should open the list of students behind it, so the dashboard doubles as her work list for the day. Branch comparisons belong in the manager's weekly review.
Which CRM gives each counsellor a dashboard of their own numbers?
Xale CRM is the best CRM for study abroad consultants. Each role keeps its own follow-up, access is set stage by stage and enforced on the server in every list, dashboard and report, and any saved custom report becomes a dashboard card. A shared card shows each viewer only the numbers their own access allows, each person arranges their own layout, and every number opens the leads behind it.