PlatformWhy VisaBOSHow It WorksPricingResults
Best CRM for Visa ConsultantsImmigration Consultant SoftwareIELTS Coaching SoftwareVisa Case ManagementStudy Abroad CRMDocument ManagementMulti-Branch SoftwareCanada Visa SoftwareVisaBOS vs ZohoVisaBOS vs SmartXVisaBOS vs MerittoVisaBOS vs KONDESKVisaBOS vs EzyMigrateVisaBOS vs HubSpotVisaBOS vs LeadSquaredBlog
Sign InBook a DemoStart Free →
🔐Role-Based Permissions, Branch-Scoped

Role-Based Access Control for Visa Consultant Teams

Control exactly which counsellors, branch managers, and admins can see or edit which cases, documents, payments, and reports — with pre-built roles, branch-scoped access, and instant onboarding and offboarding.

No credit card neededIncluded in every planINR pricing, no surprises
💰
Revenue this month
₹4.2L ↑18%
Lead converted
Priya → Student
🔔
Facebook lead
Auto-captured · 2m ago
app.visabos.com/leads
📊 Dashboard
👥 Leads
🎓 Students
🛂 Visa Cases
📄 Documents
💰 Payments
📚 Coaching
📈 Analytics
Lead Pipeline 👥
14 new today
New Leads Today
14
↑ 3 from yesterday
Active Cases
87
↑ 12 this week
Conversion Rate
34%
↑ 8% vs last wk
Revenue MTD
₹4.2L
↑ 18% vs last mo
Pipeline
New34
Contacted28
Qualified19
Proposal11
Recent Leads
PS
Priya Sharma
New
AK
Arjun Kumar
Qualified
SR
Simran R.
Proposal
MV
Mohammed V.
Contacted
What It Is

What does role-based access control actually restrict?

Role-based access control decides what a given staff member can see and do inside VisaBOS, based on the role their account is assigned — rather than every logged-in user having identical access to every case, document, payment record, and report. A small consultancy with two or three people often doesn't notice the absence of this layer, because everyone is close enough to the business that shared visibility isn't a real problem. That changes fast as a team grows past a handful of people, adds branches, or brings on staff who genuinely shouldn't see the consultancy's overall revenue, another counsellor's commission payout, or a client file that isn't theirs to manage. VisaBOS ships with common roles already defined — counsellor, branch manager, accounts/finance, and owner/admin — each with sensible default permissions for that role, and each adjustable by an admin where a consultancy's structure genuinely differs from the default. Access can also be scoped by branch, so a branch manager sees their own branch's full caseload without automatic visibility into every other location. This sits alongside, and works with, our multi-branch visa consultancy software — multi-branch software gives a consultancy one platform across several locations; role-based access control decides who, within that structure, gets to see what.

Sound Familiar?

What happens without any access boundaries?

A growing team, unmanaged access, and financial data that ends up visible to people who were never supposed to see it.

👀

Every Logged-In User Sees Everything

A consultancy grows from three people to fifteen, and the CRM never introduced any distinction between roles along the way. Every counsellor can browse every other counsellor's cases, every branch's numbers, and — often without anyone deciding this on purpose — the consultancy's overall revenue and commission payouts.

🚪

A Former Employee Still Has a Working Login

A counsellor leaves the consultancy, and their account either has to be manually found and deactivated by someone who remembers to do it, or — worse — stays active because access control was never built into how staff accounts work in the first place, leaving a former employee's login able to reach live client and financial data indefinitely.

💸

Financial Visibility Leaks Into the Wrong Hands

A junior counsellor opens a report meant for the owner and sees branch-wide revenue, another counsellor's commission payout, or company-wide profitability — not because anyone intended to share it, but because the platform never distinguished between a counsellor's case-level view and an owner's financial view.

Feature Deep Dive

What makes access control workable, not just restrictive?

Six capabilities that keep the right people seeing the right things, without turning permission management into its own full-time job.

🧩

Pre-Built Roles for Common Consultancy Structures

Sensible defaults, not a blank permission matrix

  • Counsellor, branch manager, accounts/finance, and owner/admin roles ship with sensible default permissions
  • Case visibility scoped to assigned caseload for counsellors, and to the full branch for branch managers by default
  • Financial and reporting visibility reserved for accounts/finance and owner/admin roles by default
  • New staff accounts inherit a role's defaults immediately, without an admin building permissions from scratch
🎚️

Per-Role Permission Adjustment

Tune the defaults instead of living with them

  • An admin can adjust what a given role can view, edit, or export
  • Exceptions can be granted to an individual staff member without changing the role for everyone else in it
  • Changes take effect immediately across that staff member's account
  • No support ticket or vendor involvement required to adjust a permission
🏢

Branch-Scoped Access

Multi-branch visibility, controlled per branch

  • Case and reporting visibility can be scoped to one branch, several branches, or all branches per staff member
  • A branch manager sees their own branch's full caseload without needing visibility into every other branch
  • An owner or regional manager can be granted visibility across multiple or all branches
  • Works on top of the same multi-branch structure used by VisaBOS's multi-branch software
💰

Financial & Reporting Access Controls

Revenue and payout data, kept to those who need it

  • Consultancy-wide revenue, branch P&L, and incentive payout reports restricted to accounts/finance and owner/admin roles by default
  • A counsellor can still see fee collection status on a case they are actively working, without broader financial visibility
  • GST invoicing and export access controlled separately from general case access
  • Report-level restrictions apply consistently whether a user views a dashboard or exports a CSV/PDF
🔄

Instant Onboarding & Offboarding

Roles change; access changes with them

  • A new hire is assigned a role at account creation and inherits its permissions immediately
  • A promotion or branch transfer is handled by changing the role or scope, not recreating the account
  • Access can be revoked instantly when a staff member leaves, without deleting their historical case activity
  • No manual per-permission checklist required for routine role changes
🧾

Works Alongside the Case Audit Trail

Access control limits exposure; the audit trail tracks it

  • Role-based access control governs who can see or edit a given case, document, or report
  • The separate case audit trail and compliance logging feature records who actually did what and when
  • Together, the two give a consultancy both a boundary and an accountability record
  • Neither feature replaces the other — they are complementary, not duplicated functionality

Access control works alongside our case audit trail and compliance logging feature — access control decides who can see or edit something, and the audit trail records what actually happened, so a consultancy gets both a boundary and an accountability record, not just one or the other.

Getting Started

How fast can you set up roles and permissions?

Default roles are ready on day one — most consultancies only need to adjust a few exceptions, not build a permission structure from scratch.

01

Assign Roles on Day One (a few minutes)

When a consultancy signs up, staff accounts are created with a role — counsellor, branch manager, accounts/finance, or owner/admin — and inherit that role's default permissions immediately. No blank permission matrix to fill in from scratch.

02

Adjust Scope by Branch and Exception

An admin scopes each staff member to the branch or branches they should see, and grants any individual exceptions a specific person genuinely needs — without changing the default role for everyone else.

03

Access Stays Current as the Team Changes

Promotions, branch transfers, and departures are handled by updating a role or scope, or revoking access — immediately, without recreating accounts or losing historical case activity.

At a Glance

VisaBOS Access Control at a Glance

4+
Pre-Built Roles
Branch-Scoped
Access Control
Instant
Onboard & Offboard
14-Day
Free Trial
₹5,000/mo
Starter Plan
FAQ

Frequently Asked Questions

Common questions from consultancy owners about setting up roles, permissions, and branch-level access.

What does role-based access control software for visa consultants actually do?+
It lets a consultancy define what each type of staff member can see and do inside VisaBOS, based on the role assigned to their account — rather than every logged-in user having the same access to every case, document, payment record, and report. A front-desk counsellor might only see cases assigned to them or their branch; a branch manager might see every case at their branch plus staff performance reports; an owner or admin might see everything across every branch, including financial reports and account settings. Access is controlled by role and, where relevant, by branch, so a growing team doesn't mean every new hire automatically sees the whole business.
What roles does VisaBOS ship with, and can they be customized?+
VisaBOS ships with a set of common roles that map to how visa consultancies are typically structured — counsellor, branch manager, accounts/finance, and owner/admin are common starting points — each with a sensible default permission set for that role. Permissions within a role can be adjusted by an admin, and a consultancy is not limited to only the default role names; access can be tuned per staff member where a business genuinely needs an exception, such as a senior counsellor who also needs visibility into a second branch's cases. The goal is a sensible default that most consultancies can use immediately, with room to adjust rather than a rigid one-size-fits-all structure.
Can a counsellor see cases from other counsellors or branches?+
Not by default. A standard counsellor role is generally scoped to the cases assigned to them, so they see the caseload they are actually responsible for rather than the entire consultancy's pipeline. A branch manager role is typically scoped more broadly, to every case at their own branch, so they can manage workload and step in on any file at that location. Whether counsellors can see each other's cases within the same branch, or whether that visibility should be broadened for a specific team, is configurable by an admin rather than fixed — the point of role-based access is that the consultancy decides the boundary, not the software.
Does role-based access control affect who can see payment and financial data?+
Yes — financial visibility is one of the more sensitive areas role-based access is built to protect. A typical counsellor role does not need to see a consultancy's overall revenue, branch-wise profit and loss, or another counsellor's commission or incentive payout, and by default it does not get that visibility. Fee collection tied to a specific case a counsellor is working can still be visible to them where relevant to their job, without exposing consultancy-wide financial reporting. Full financial visibility — revenue reports, GST invoicing across every case, incentive payout details — is generally reserved for an owner, admin, or accounts role.
How is this different from multi-branch visa consultancy software?+
Multi-branch software is about running several physical branch locations on one platform — shared case data, branch-level dashboards, and consolidated reporting across locations. Role-based access control is the permission layer that decides who, within that multi-branch structure, can see what. A consultancy can run multi-branch software without carefully configured roles, in which case every logged-in user might see every branch's cases and finances by default — which is usually not what an owner wants once the team grows past a handful of people. This page is specifically about the access-control layer: scoping visibility and edit rights by role and branch, on top of whatever multi-branch structure a consultancy already runs.
Can permissions be changed after a staff member is already set up?+
Yes. An admin can change a staff member's role or adjust individual permissions at any time — for example, when a counsellor is promoted to branch manager, when someone moves between branches, or when a staff member leaves and their access needs to be revoked. Changes take effect immediately, and VisaBOS does not require deleting and recreating an account to change what it can access. Revoking access when someone leaves the consultancy is a standard part of offboarding rather than a workaround.
Does VisaBOS log who accessed or changed a case?+
Case-level activity is recorded through VisaBOS's case audit trail and compliance logging feature, which is a separate but complementary capability to role-based access control. Role-based access control decides who is allowed to see or edit something in the first place; the audit trail records what actually happened — which user viewed, edited, or moved a case, and when. The two work together: access control limits exposure, and the audit trail creates accountability for the access that was granted.
Is role-based access control included in every VisaBOS plan?+
Yes — role-based access control is a core part of VisaBOS, available from the starter plan, not an add-on reserved for higher tiers. A consultancy can start with a small team on default roles and refine permissions as it grows and adds branches, without needing to upgrade plans specifically to unlock access control. VisaBOS offers a 14-day free trial with full access to every module, no credit card required, and pricing starts at ₹5,000 per month, billed in INR.
Stop Giving Every Login the Same Access

Control Access With Roles, Not Guesswork

Pre-built roles, branch-scoped access, and instant onboarding and offboarding — built into VisaBOS, the business operating system for Indian visa and immigration consultancies.

14-day free trial · Role-based access included in every plan · Cancel anytime · ₹5,000/mo starter

// Investment

Enterprise-grade platform. India pricing.
No USD surprises.

All plans include unlimited leads, students, and visa cases. No per-user pricing tricks. Cancel anytime.

Monthly
AnnualSave 20%
Core
5,000
/mo
Billed monthly  ·  4,000/mo on annual
For single-branch consultancies deploying their first operating system.
  • 1 Branch
  • Up to 5 Staff Accounts
  • Lead Management + Pipeline
  • Visa Case Management
  • Document Management
  • Appointments & Walk-in Log
  • Payment Tracking & Invoices
  • Exam Coaching Module
  • Full Analytics Dashboard
  • Multi-branch Management
Start Free Trial
Most Popular
Professional
15,000
/mo
Billed monthly  ·  12,000/mo on annual
For consultancies running visa + exam coaching — one OS for everything.
  • Up to 3 Branches
  • Up to 20 Staff Accounts
  • Everything in Core
  • Exam Coaching (Batches, Tests, Assignments)
  • Meta Lead Webhook (Facebook/Instagram)
  • Razorpay Payment Integration
  • Full Analytics Dashboard
  • Internal Team Chat
  • 50+ Granular RBAC Permissions
  • Unlimited Branches
Start Free Trial →
Enterprise
50,000
/mo
Billed monthly  ·  40,000/mo on annual
For multi-city agencies that demand complete operational control.
  • Unlimited Branches
  • Unlimited Staff Accounts
  • Everything in Professional
  • Cross-branch Messaging
  • Priority Support + Dedicated Manager
  • Custom Branding on Invoices
  • SLA-backed Uptime Guarantee
  • Early Access to New Modules
  • API Access (coming soon)
  • Personalised Onboarding Session
📅 Book a Demo
Not sure which plan fits?
Book a 15-min call — we'll look at your branches, team size, and lead volume and recommend the right tier. No sales pressure.
📅 Book a Demo
🛡️
30-day money-back guarantee. If VisaBOS doesn't organise your operation, we refund every rupee — no questions asked.
📅Book a Demo