Everyone Sees Exactly What Their Role Allows
Role-based access controls who can open a dataset, who can change a definition and which rows a person is entitled to see — enforced centrally, so permissions do not depend on who remembered to restrict a file.
Data Scoping
Policy Control
Access Trail
Why Role-Based Access Matters
Access control is usually implemented once, during implementation, and then quietly erodes. People change roles, projects end, contractors leave, and permissions accumulate because removing them is nobody's job. The eventual audit finding is never a surprise to the team that lived through it.
Role-based access in Mimasa AI is defined centrally against roles rather than individuals, so a change in someone's responsibilities changes what they can see everywhere at once. Row and column level rules mean a single dashboard can serve a national leadership team and a regional one without maintaining two versions of it.
Every access decision and data action is logged, which turns compliance from a reconstruction exercise into a query. For regulated industries and public sector deployments this is frequently the capability that determines whether a platform can be used at all, regardless of how good its analysis is.
What You Get
The capabilities behind role-based access in Mimasa AI.
Roles And Permissions
Define roles once — viewer, analyst, owner, administrator — and assign people to them.
Row-Level Scoping
Restrict a role to its own region, entity or business unit so one dashboard serves everyone safely.
Central Policy Enforcement
Rules apply to dashboards, reports, exports and conversational answers alike — no side doors.
Access Audit Trail
See who accessed which dataset and when, ready for an internal or external review.
How It Works
From connected data to a working outcome, in four steps.
Define Roles
Set the roles your organisation actually uses.
Attach Data Rules
Scope each role to the rows and datasets it may see.
Assign People
Add users to roles, individually or by group.
Review The Trail
Audit access periodically from the activity log.
Why It Matters
Sensitive Data Stays Contained
Salary, margin or customer detail is visible only to the roles entitled to it.
One Dashboard, Many Audiences
Row-level scoping removes the need to maintain a separate copy per region or entity.
Audit-Ready
Access history answers the compliance question without a manual reconstruction.
Where Teams Use It
Why Access Control Has To Be Centralised, Not Habitual
Most access problems do not start with a bad decision; they start with a reasonable one that nobody revisits. A contractor is given broad access to finish a project quickly, a role change leaves someone with permissions from their previous job, an old integration is never fully decommissioned. None of these choices looks wrong at the time, but a year of them accumulating produces exactly the exposure an audit eventually flags. Mimasa AI addresses this by defining access against roles rather than individuals, so a single change to what a role is permitted to see applies immediately to everyone holding that role, instead of requiring someone to remember and update every affected person's individual permissions.
Row and column level scoping is what allows one dashboard to safely serve very different audiences without maintaining separate copies for each. A national leadership team and a set of regional managers can open the identical dashboard, with each regional manager automatically restricted to their own territory's rows while the leadership view remains unrestricted. This removes a specific and common source of drift, where a regional copy of a dashboard is cloned, then edited independently, and quietly stops matching the definitions used at the national level.
The audit trail exists for the moment access actually gets questioned, which for most organisations is not a hypothetical — it is a recurring compliance requirement, a customer security review, or an internal investigation. Rather than reconstructing who could see what at a given point in time from scattered records, Mimasa AI keeps a continuous log of access to datasets and reports, so answering that question is a matter of querying the log rather than assembling evidence after the fact.
Common Questions
Does scoping apply to exports too?
Yes. Exports and conversational answers respect the same row-level rules as dashboards.
Can I assign access by group?
Roles can be assigned individually or to a group so joiners inherit the right access.
Is access logged?
Access to datasets and reports is recorded and reviewable.