Capability

Company data, granted by its owner

On Substrait, the owner of each set of company data approves each tool's access, for a set time. Every call goes through one gateway that holds the credential, checks the grant and records the read, so you can always answer who read what, and why they were allowed.

Last updated

Data groups and data owners

An admin puts APIs, data sets and fields into data groups. Groups follow your business domains, such as finance, operations or HR, not a ladder of levels. Each group has a data owner, who decides every request for its data. A person’s access is the sum of the groups they hold, and there is no deny group.

Two grants for people, one for tools

WhoGrants, in order
The person who builds1. Enrolment: sees which data exists and its shape, no records. 2. Authorisation: reads the data, once the data owner approves.
The tool they buildAuthorisation: its own, approved separately by the data owner. Never wider than the requesting person’s enrolment. Stays with the tool if people change.

A builder can build a tool that reads data they cannot read themselves. The builder saw the shape, the owner approved the tool, and the builder never handles the data or the credential.

Every grant has limits

  • Every authorisation expires after a set time and is requested again.
  • A data owner can cap how often a tool may call, so one runaway tool slows down without affecting others.
  • Grants are made to a whole data group, never tool by tool, so the model stays small.
  • Calls between tools on Substrait are data grants too; the called tool’s owner approves.

One gateway

Every call a tool makes to company data goes through Substrait’s gateway. The gateway holds the credential, encrypted and write-only, and attaches it to the call. An ungranted call is refused with the name of the missing grant. A withdrawn grant refuses the very next call, with no redeploy. Outbound traffic from a tool is denied unless a grant allows it, so the gateway is the only way out.

Data nobody granted you is invisible

A builder sees nothing of a data group they are not enrolled in: no name, no count, no gap. A compromised account therefore exposes no map of your data.

What the gateway reaches

Your systems’ APIs, the tools your people build on Substrait, your data warehouse through reviewed and versioned data sets, your reporting tools, and business systems such as SAP, Salesforce, Oracle, NetSuite, Microsoft Dynamics 365, SQL Server, SharePoint and Microsoft 365.

Substrait console: the groups in an organisation, each with its members and what it grants.
Groups, by business domain. Product UI. Sample data.

Questions and answers

What is a data group?

A data group is a set of APIs, data sets and fields that belong together, such as finance or operations. Each data group has a data owner, who approves every request to read its data.

What is the difference between enrolment and authorisation?

Enrolment shows a person which data exists and its shape, with no records. Authorisation, approved by the data owner, lets a person or a tool read the data. Neither implies the other.

Can access be granted down to a single field?

Yes. A data group can name individual fields as well as whole APIs, so one sensitive column can be kept apart from an otherwise open API.

Related

Start with a result, not a rollout.

Book a demo and bring one real use case. We will show you how a tool your people build goes live on Substrait, with its data approved and its security check passed.