Data access and governance

Governance your own administrators run, without raising a ticket

Decide which groups see which tables, how people sign in, which devices may be used and how long content is kept. The rules are set by the organization and applied by the service to every question, chart and report.

Table access groups

Who sees which tables, decided by the organization

An administrator places members in groups and gives each group the tables it may use. The rule applies wherever data appears: chat, charts, dashboards, scheduled reports and suggested questions. A member who asks about a table outside their access is told so, rather than answered from another table.

Groups, members and tables managed on one settings page
"View as" a member, to confirm what that person can reach
Charts and conversations built on tables a member cannot see are hidden from that member
Finer control

Each group sees only the rows that concern it

Enabled per plan

Where a table is shared but its rows are not, a group may be limited to the rows that concern it, such as one region or one business unit. Where your own database already sets limits for a team, those limits can be honoured as well. The control is checked before it is switched on.

01
The same question returns each group its own rows
02
Limits already set in your database can apply too
03
Checked for readiness before it takes effect
Sign-in

Two-factor sign-in, required for all where the organization so decides

Members may protect their accounts with an authenticator app, and an administrator may require it for the whole organization. Single sign-on with Microsoft or Google is by invitation only, so that an account exists only because someone invited it. Passwords may be reset and changed by the user.

  • Authenticator-app codes, with a guided set-up for members who have not enrolled
  • Administrators see who has enrolled and may reset a lost device
  • No self-service sign-up into an organization: membership begins with an invitation
Sessions and devices

Each person sees their own sessions; administrators set the device policy

Every user may see where their account is signed in and end any session. For the mobile app, administrators decide who may use it, see each member’s devices, end a device’s session and approve new devices. These are policies the organization sets for its members.

  • A list of signed-in sessions with recent sign-in activity
  • Mobile access per member, device approval and a limit on devices
  • Restriction by country, and question text hidden on the lock screen
Audit and retention

An audit log the organization’s administrators read themselves

Sign-ins, membership and role changes, connection changes, policy changes, exports and scheduled-work changes are recorded and may be read by the organization’s own administrators. The organization also determines how long question content is retained.

  1. 1Entries are written by the service, not by the browser
  2. 2Records identify what changed without holding credentials or recipient addresses
  3. 3A retention period set by the organization, with an on-demand purge
How it goes

Introducing access control without disruption

An organization begins open and tightens deliberately.

1

Begin open

By default every member may use every connected table, which suits a small first team.

2

Define groups

Create groups, add members and select the tables each group may use.

3

Check with "view as"

Look at the platform as a given member would, and see who would lose access before anything changes.

4

Switch to restricted

From that moment the service applies the groups to every question, chart, dashboard and report.

Also under the organization’s control

Smaller controls that complete the picture

Each is set by the organization’s administrator and takes effect without a request to Facgure.

01

Feature visibility by role

Choose which roles see the SQL panel, the result table, data export, email sharing and the data catalog.

02

Idle sign-out

Sign users out after a period of inactivity, with a warning beforehand. On mobile, an idle session may lock behind the device’s biometrics instead.

03

Removal takes effect at once

When a member is removed, their access to the organization’s data ends immediately and their personal alerts stop.

04

Personal data masked

Columns marked as personal data are masked before results are used to compose an answer, and in catalog previews.

05

Account deletion by the user

A member may delete their own account. What the organization uses passes to an administrator, and personal content is removed.

06

Announcements

Administrators send notices to all members or selected roles, with a record of what was sent and by whom.

Questions

Questions about this feature

Does table access apply to charts and reports, or only to chat?

It applies wherever data appears: chat, pinned charts, dashboards, scheduled reports, alerts, suggested questions and the data catalog. A report recipient whose access does not cover the figures receives a notice instead of the numbers.

What does a member see when they ask about data outside their access?

They are told that the data is outside their access. The platform does not answer from a different table and present it as though it were what was asked.

Are administrators exempt from two-factor sign-in?

No. When the organization requires it, it applies to administrators as well, and an administrator must have enrolled before turning the requirement on.

Are row-level filters included for every organization?

Row-level filters are enabled per plan. Table access groups are available to every organization and are managed by its own administrator.

Who can read the audit log?

The organization’s administrators read the entries of their own organization within the product. No request to Facgure is required.

Answer your most demanding question

Request a 30-minute session. We will connect a sample of your data and put genuine decision questions to it, in Thai or English.