Workspace

Row-level data access

Limit people or roles to part of the data — one branch, one sales channel — everywhere DataxLand shows a number, including Si, MCP, chat, reports and alerts.

Included from the Small Business plan. Admins (or any role with the "Data access" permission) set it up in Settings → Data access.

Rules

A rule has a dimension from the semantic model (channel, branch, platform…), the values that may be seen, and who it applies to: members or roles (built-in or custom).

  • Several rules on the same dimension for one person: their values add up (Hanoi + Ho Chi Minh City).
  • Rules on different dimensions: both must hold (Hanoi branch and the Shopee channel).
  • People with no rule: see everything — or nothing, if you turn on People without any rule see no data.
  • By default Owners and Admins bypass rules; untick this to restrict them too. Whoever edits rules must be unrestricted themselves (nobody can widen their own access).

Where it applies

The rule's condition is added to every query DataxLand runs to compute a number, so totals, period comparisons, top-N lists, ratios and "why" analysis are all computed on the allowed rows only — no number is ever computed on everything and filtered afterwards.

WhereComputed with the permissions of
Dashboards, pages, inspector, queries, "why", report previewsthe person viewing
Si in the app; asking Si in a private chat with the bot (Telegram, Slack, Teams)the person asking (linked account)
Telegram groups, Slack channels, Teams channels and group chatsanswers only people who are not restricted (the whole group sees the answer); restricted people are asked to message the bot privately, unless "Allow answers in group chats based on the asker's access" is on
MCPthe person who created the token
Scheduled reports, alertsthe person who created the report or alert (if they leave the workspace, the send is skipped)

Metrics built on a table that doesn't have the restricted dimension (e.g. ad spend not split by branch) are hidden from restricted people by default; switch the rule to "Still show workspace-wide numbers" if you're fine with them seeing those.

Restricted people can't open screens that read raw data: data sources, SQL on sources, data profiles, workspace export — and Si doesn't use the SQL/Python sandbox for them (its extracts take whole tables).

Downgrading

Existing rules keep being enforced (switching them off when a plan ends would expose data); you just can't create or edit them.

Every change to rules and settings is recorded in the audit log.

Markdown