Definitions for terms used in Clarity. If you encounter an unfamiliar word while working with Databooks or Reportbooks, look it up here.
The rules determining who can view, edit, or manage a Databook or Reportbook. Clarity uses three permission levels: Viewer, Editor, and Owner. Access can be set at the item, folder, or row level.
A saved set of Global Filter values in a Reportbook. Applying a bookmark restores that filter state instantly.
A full copy of a Databook or Reportbook, including all content, settings, and bookmarks. The clone is independent - changes do not affect the original.
Use cloning for:
A field within a Databook table. Each column has:
A visual element on a Reportbook page: chart, table, KPI tile, or text block. Each component connects to a Databook table as its data source.
A validation rule on a Databook column that restricts what values can be entered.
Types:
A container for one or more related tables in Clarity. Databooks store reference data, configuration, hierarchies, and manual input tables.
Features:
The Databook and table that a Reportbook component pulls data from. Each component has one data source; columns are mapped to visual elements.
A folder holding deleted Databooks and Reportbooks. Items can be restored from here.
Important: Items are permanently purged after 30 days.
A permission level allowing view and edit access. Editors cannot manage settings or permissions.
The context menu (...) on Databooks and Reportbooks. Provides access to Clone, Snapshot, Delete, Rename, Move, and Manage Permissions.
An organizational container for grouping Databooks or Reportbooks. Folders can be nested. Permissions set on a folder are inherited by items inside.
A filter at the top of a Reportbook that applies to all pages. When set, every component using that field updates.
Options:
A parent-child relationship in a Databook table. Uses two columns:
Creates a tree structure viewable in hierarchy mode.
A Reportbook component displaying a single metric prominently, often with trend indicators or comparisons.
Tracking of data origins and dependencies.
A constraint linking a column to values in another table. The column only accepts values that exist in the source table - like a foreign key.
The highest permission level. Owners can view, edit, manage settings, and control permissions for other users.
Best practice: Every Databook and Reportbook should have at least two Owners.
A single canvas in a Reportbook containing components. Pages are listed in the sidebar and can be grouped into Sections.
The three access tiers in Clarity:
| Level | View | Edit | Manage |
|---|---|---|---|
| Viewer | Yes | No | No |
| Editor | Yes | Yes | No |
| Owner | Yes | Yes | Yes |
A collection of report pages that displays data from Databooks.
Features:
A single record in a Databook table. Each row has one value per column.
A permission model where users only see rows they are authorized to access, based on a designated column value.
A named group of pages in a Reportbook. Sections appear as collapsible containers in the sidebar. Organizational only - no effect on data or permissions.
A read-only copy of a Reportbook at a specific point in time. Data is frozen as it was when the snapshot was created.
Use for:
Difference from Clone: Snapshots are read-only with frozen data. Clones are editable with live data.
A grid of columns and rows in a Databook. Each table has a defined structure (columns with types and constraints) and stores data. A Databook can contain multiple tables.
Analytics showing how Reportbooks are used: page views, unique viewers, frequency, user breakdown, and timing patterns.
A predefined set of allowed values for a column. Users select from a dropdown rather than typing free text.
Automatic tracking of all changes to a Databook or Reportbook. Records who changed what and when.
The most limited permission level. Viewers can see data and apply filters but cannot make changes.