Skip to content

PlatformGovern

Users and roles

Everyone sees and does only what they need

Create roles with the permissions you choose and assign them to people, grouped in teams if you like. When someone leaves the company you deactivate them and their sessions end.

Company settings

Roles

  • AnalystRead and edit datasets
  • ViewerRead only
  • AdministrationUsers and settings

Teams

  • SalesTeam
  • Management controlTeam

Illustrative example

Permissions built for a company, not an installation

  • Custom roles

    Build a role by choosing, permission by permission, what it can read and what it can change.

  • Never more than you hold

    Whoever edits a role cannot add permissions they do not have: writing a role is not a shortcut to more access.

  • Teams

    Group a company's people in teams, and find every member in a list with filters and export.

  • Deactivating ends sessions

    Deactivate a person and their open sessions end at once. API keys they issued stay valid until you revoke them.

Who can do what, in three steps

  1. 01

    Create the roles

    Start from what each job needs and choose the permissions one by one.

  2. 02

    Add the people

    Create the user, give them one or more roles and, if needed, a team.

  3. 03

    See what changes

    Every change to users, roles and teams lands in the audit log.

In detail

Roles
Custom per company, with separate read and edit permissions.
Assignment
A person can have several roles and belong to a team.
Several companies
A person can belong to more than one company.
Lists
Users and teams can be filtered, grouped and exported to xlsx.
Deactivation
Ends the person's sessions at once.

Frequently asked questions

No. When a role is written, Muvia refuses any permission the person editing it does not hold.

Bring us a question you can't answer today.

We start from a real question your business has and walk the path from source to dashboard with your systems, not a demo dataset.