Org admin guide

For an organisation's admins: from your data to dashboards your team uses, in an afternoon. The home page's Get started list follows these steps and ticks them off as you go; Show me on a step points at the control to use. Your team is offered a one-minute tour at their first sign-in (and Tour, next to each person's name, runs it again).

Connect your data

On Data › Connections, add where your data is, and press Test before saving. Connections only ever read, and their passwords and keys are never shown again once saved.

Type	What you need
PostgreSQL, ScramDB	host, port, database, user, password; optionally a schema (where tables are looked up)
BigQuery	project, dataset, a service account's JSON key; every query is checked first against a cost cap
DuckDB (files)	Parquet, CSV, JSON, Avro or Iceberg files, in your organisation's folder or on S3 / Google Cloud Storage, named as tables

Name your main connection warehouse: the platform's models look for that name.

Describe your data: models

A model says which table, what people group and filter by (dimensions: region, day) and what they add up (measures: revenue, count). Dashboards and Explore work on models.

Data › Models › + New model: pick the connection, then the table.
Magnum BI proposes the fields from its columns: text and dates as dimensions, numbers as sums (ids and hours, months and years as dimensions), and a count of rows.
Untick what nobody needs, rename fields the way your team speaks, switch a number between dimension and measure, choose sum or average, and Save model.

Everyone in your organisation can then use it. Your platform may also provide models of its own (shared data, made by its system owners), listed under From the platform: they read your connection of the same name.

Restrictions follow the data. A member limited to some rows (Members) is limited on every model reading the same table. A model on a different table or view is different data: check restrictions after adding one.

Make dashboards

In one click: Data › Models › Starter dashboard makes a dashboard from a model: its main numbers and their trend, activity over time, the top categories and the details. Change anything with Edit.
Chart by chart: in Discover › Explore, drag dimensions and measures in; Magnum BI suggests a chart (17 types: KPIs, trends, gauges, tables and pivot tables, bars, lines, combos, heatmaps, treemaps, funnels, waterfalls, histograms…). Add to dashboard when it's right.
Words and pages: in Edit, + Add text adds a tile of notes (how to read the dashboard, what a number means), and + Tab splits a long dashboard into pages.
Period and filters: a dashboard can have a period with a comparison (previous period or year) and filters everyone can use.
Blends (Data › Blends) join models on shared fields, even across databases (sales with the weather).

Invite your team

Settings › Members › People: add people by email with a role: Viewer (sees dashboards, uses filters), User (also drills down, embeds and downloads the data), Power user (also builds dashboards, explores, shares with guests), Org admin (also manages members, connections, models and sharing).
Personal filters limit someone to some rows ("region is EMEA"), everywhere. They only ever narrow.
Everyone else from your domain (if your platform set one) joins with the default role you choose.
One-time password… makes a password to hand over, for people who sign in with one; they choose their own at their first sign-in.
Check what someone sees with View as (top right): never more than your own role.

Your colours

Themes: start from a theme, set your colours, chart palette, corners and font, and check the readability marks; or import your design team's CSS tokens. Make it your organisation's default (light and dark). Export CSS gives your web team the same colours as design tokens.

Sign-in and single sign-on

Settings › Members › Sign-in, within what your platform allows:

Which ways to sign in your people may use, and whether passwords need an authenticator code.
Your company's single sign-on (Microsoft Entra ID, Okta, Keycloak, Google Workspace…, any OpenID Connect provider): its address, client id and secret, and which provider groups become which roles. It signs in addresses on your organisation's domains only.

Everyone can add passkeys and authenticator codes for themselves under Security.

Email and webhooks

Delivery › Mail server: your organisation's own mail server (host, port, STARTTLS or TLS, a user and password if it needs one, the sender). Send me a test sends a message to you. It's yours alone: other organisations and the platform use their own.
Delivery › Webhooks: Slack or Microsoft Teams incoming webhooks, or any address that takes JSON. Give each a name; Test posts a message.
Passwords and webhook addresses are stored encrypted and never shown again. The addresses must be reachable from the server, over https for webhooks.
Who reports may go to: your members always; add partner domains under the mail server's Reports may also go to these email domains.
Scheduled reports: anyone from the User role up can Schedule… a dashboard (the data, a guest link with a password, or a public link), or set an alert on a number. The Scheduled reports list on Delivery shows them all, by whom, to whom, how the last run went; pause or delete any of them.