Configuration

Overview

Configuration in DataGenie - manage users, user groups, roles and permissions, tenants, and the Access Matrix from one place.

Configuration is where you decide who can do what in DataGenie. Users, user groups, roles and permissions, tenants, and the Access Matrix all live in one place, so access is explicit and easy to reason about.


What Configuration covers

Users
Everyone in your account, and exactly what each person can reach.
User Groups
Groups that carry access - add someone to a group and they inherit its role.
Roles & Permissions
What each role allows - view, add, modify, or delete - across every area.
Tenant Management
The tenants you can see, and what lives in each.
Access Matrix
Every person and group against every scope, with the role they hold - grant or revoke in one place.

How access works

Access begins with a role. Each role spells out exactly what it permits - view, add, modify, or delete - and how far it reaches:

ScopeReaches
GlobalThe whole account - users, tenants, roles, and releases.
TenantOne tenant, and every dataset inside it.
DatasetA single dataset or NirvanaSet, one scope at a time.

Built-in dataset roles cover the common cases - Reader (view-only), Editor (tune and save), and Admin (own a dataset) - and you can define custom roles when your structure needs something more specific.

Be deliberate with Editor and Admin access. Changes to KPI definitions, schedules, or group assignments cascade across the stories and analyses downstream.


User groups do the heavy lifting

A user group is more than a mailing list - it carries the access it grants. Put someone in a group and they inherit its role automatically, with no per-person setup. And groups aren't only for permissions: you can share a Brief with a group, and everyone inside gets it.


No access by default

A brand-new user starts with no dataset access - they land on a No Access screen until a Global Admin grants them a role. This is intentional: it prevents any exposure in the window between a user being created and their access being set. For enterprise SSO (Okta, Azure AD / Entra ID, Google Workspace, OneLogin), data residency, and audit, see Security & Trust.


What's next

On this page

Built withsuperlore