account_admin can do everything data_admin can, which can do everything data_engineer
can, and so on down to public, the baseline every member holds.
Built-in roles
You can create custom roles that inherit from any of these, or from each other, and grant them any
subset of the privileges below.
platform_admin is not one of these roles. It’s a flag the platform administrator console asserts
for a small number of people who support the whole platform, not a role your tenant assigns.
A platform admin gets the same bypass as account_admin/data_admin on every tenant, but you
won’t find platform_admin in your roster or your role list.No built-in role reaches another member’s workspace database in Trino. The owner gets a grant on
their database’s catalog automatically; anyone else, admins included, needs a share or a grant that
names that catalog. The broad grants below (
analyst reading every table, data_engineer writing
every catalog) and the admin bypass don’t apply to it. That narrows an admin’s access only:
admins are exempt from the row filters and column masks on their roles, including on workspace
databases they own or are granted; an app’s own filters and masks still apply.viewer holds it, and every staff
role inherits it: analyst, data_engineer, data_admin and account_admin. A custom role without
Catalog read cannot browse or search discovery metadata; it still sees Explore and its SQL editor
when it holds Query engines → Read.
Per-object permissions still limit which results you can see.
What each resource supports
The Roles & permissions page, under Settings → Roles & permissions, shows a grid of resources down the side and privileges across the top. A cell you can toggle means some role grants it; the table below names the least-privileged built-in role that already holds each one. Use the Agent registry, Agent installs and Agent tasks rows to grant permissions for publishing, consent and task execution. Installation consent is limited to your selected role when using Act as. Agent management and task execution are currently API-only. A task’s conversation is visible to its launcher or a data admin after the task read check; a colleague can send a follow-up without acquiring that view. The Marketplace installs row covers the Marketplace: Read lets a role browse listings and see the Installed tab, Create lets it install a listing as drafts, and Delete lets it remove an install record; there is no Update, because an install is never changed, only removed. The drafts an install creates are then governed by the Semantic models and Concepts rows like any other. Adding a pipeline listing needs Create on Marketplace installs and on Pipelines together, adding an agent listing needs it on Marketplace installs and on Agent registry, and adding an app listing on Marketplace installs and on Data apps.
Agent task reads are limited to the immutable launcher or a
data_admin (including inherited
account_admin and platform_admin authority) even when a role grants
AgentTask/read. Agent task updates require AgentTask/update and still obey review and input gates.
The Git repositories row is the complete repository role model. viewer can fetch, data_engineer
can create repositories and push ordinary refs, and data_admin can manage protected refs. Dippr
does not add per-repository members or grants. Selecting a narrower act-as role cannot retain the
wider role’s push permission.
* Delete on a workspace database is bounded to your own database, or a shared one you own — never
a colleague’s. Ownership is checked on every request; the role only says whether you may have
workspace databases at all.
† Own personal database covers only the member’s own personal workspace database: create it,
read it, and load data into it. It never reaches a shared database or another member’s
database, and it gives no invite or delete. It is on by default for viewer and everything that
inherits it, and an admin can switch it off (see
Turn off personal databases for viewers).
Member directory is the list of colleagues’ emails and roles that member pickers show (sharing a
workspace database, choosing an owner). It is separate from Members, the administrator’s grant to
manage people. viewer holds it, so every built-in role above it does too. A custom role that does not
inherit viewer cannot list the tenant’s members unless it holds Members → Read, which also
allows the list because Settings → Users needs it.
Two rows appear on the grid but aren’t control-plane CRUD in this sense:
- Catalogs —
viewercan read catalog metadata, but creating, altering or dropping objects inside a catalog is governed by the Data grants tab (table, schema, column and function privileges), not by this grid. - Queries —
viewercan read the query log;publicalone cannot. The console Queries page and thesearch_queries/get_queryMCP tools both resolve to the sameQueryEngineread grantviewerholds — a member whose roles grant noQueryEngineread (noviewer, and no custom role that grants it directly) is refused both.analystcan submit new queries. There is no separate update/delete privilege here — a saved query is governed by who owns it.
Own-app permissions
The matrix also offers two narrow permissions, separate from broad Create, Update and Delete:
An administrator can choose Allow or Deny for these settings on
viewer, analyst and
data_engineer. On analyst, data_engineer and custom roles, Default removes the role’s own
override and follows its parents. The displayed status includes inherited effects. Deny wins across
effective roles, so an inherited deny cannot be
cancelled by an allow on a child role. These settings survive upgrades.
Turning a setting off also disables the narrow cleanup actions it covers. Broad app permissions
remain independent, and data_admin, account_admin and platform administrators retain admin
access. The controls show Allowed (admin) instead of promising to revoke that access. Local
preview remains separate. See Own-app role settings.
Verbs that surprise people
- Changing an installed app’s version requires Manage own apps or App installs → Update. Manage own apps covers your own static versions. A Data admin can change any app’s version; for broad access on a custom role, grant Update on App installs. See Changing version.
-
Local app preview is available from
viewer.dip app devcreates your own local-development sandbox. Only its developer can obtain query credentials or delete it. Preview does not grant publishing or install permission: queries still need your own data grants and must fit the app’s declared capabilities. Your row filters and column masks apply. A stock viewer has no table data grants. The Preview own apps column applies only to Data apps. For a custom role, choose Allow or Deny to set its preview permission, or Default to follow its parents. Deny overrides inherited access for roles without admin access. A role that inheritsdata_adminoraccount_adminshows Allowed (admin), and its Deny option is disabled because admin access takes precedence over preview denies. Local preview also needs Query engines → Read to find an engine; grant that separately or inheritviewer. Without engine read, an allowed preview cell shows Preview also needs Query engines: read. See Configure roles and Run an app locally. -
DROPon a schema or catalog reaches the tables inside it. Data grants apply to everything under the ref, so a role withSchema · DROPonsales.stagingcan drop or rename that schema and also drop any table or view in it. GrantDROPon individual tables when that’s all you mean. -
Testing a connection counts as
update, notread. Probing an integration dials the external system with its stored credentials, which is an authoring action — a read-only role can see that a source is registered but can’t use it as a probe. - Managing who holds a role is a different privilege from defining what a role means. Assigning or removing a member’s role, and the reads the roster page needs (list roles, list who holds which), are all gated on Members. Only changing what a role itself grants — its privileges, its inheritance — is gated on Roles. A custom role can be trusted to manage the roster without ever being able to redefine what any role is allowed to do.
- Invitations waiting for acceptance are not on the member list. Every member can see who the members are. The tenant’s list of people who were invited and have not accepted yet is shown only to someone who can read Members, and withdrawing one of those invitations needs Members delete. The invited person sees their own invitation once the invite link has been opened and they have signed in, whatever roles they hold elsewhere. See Invitations.
-
Certifying a semantic model or concept is its own privilege, not part of
update. Someone who can edit a draft metric or a business concept can propose a new version; onlydata_admincan certify it as the definition the whole tenant trusts, or deprecate one that’s currently relied on. The split exists so an author — human or an agent acting as one — can never bless its own work. -
The tenant’s audit log is admin-only by default, on purpose.
account_adminholds the one explicit grant for it (audit logread, so the console shows the Access log tab and the grant can be given to a custom auditor role); onlydata_admin,account_adminand platform admins can see it, though anyone can see the lifecycle history of an engine they can already read (that’sviewer, since it’s the same information as the engine itself). -
Query visibility defaults to your own queries. Anyone who can read the query log at all (see
Queries, above —
viewerand up) can read their own; seeing the whole tenant’s queries — every member’s full SQL, which can hold literals, secrets and restricted table and column names — takes the tenant-audit permission on query engines, held bydata_adminandaccount_admin(and grantable to a custom role, so a support or query-monitor role can see all queries without being a full admin). It widens the console Queries page, the live running-query view, and thesearch_queries/get_queryMCP tools to the whole tenant; without it, all of them show only the queries you ran. Cancelling another member’s running query is a separate, operator-level permission (manageon query engines), not implied by audit. -
Dangerous connector routines are denied by default, even with a wildcard routine grant. Raw-SQL
passthrough (
system.query,raw_query) needs the dedicatedFunction · PASSTHROUGHverb, and storage-mounting procedures (Icebergregister_table,add_files,migrate) needProcedure · MOUNT— both held by no built-in role, admin-grantable to lift, and never available through a data app. Destructive table procedures (expire_snapshots,vacuum,optimize, …) are authorized against theTable · DELETE/UPDATEthey perform, soSELECTaccess alone does not let you run them and a table deny blocks them. See Roles & permissions.
Act-as (not in the current release)
The act-as role switcher — a top-bar control that let you narrow into a single one of your roles to see the tenant the way that role does — is parked for the MVP and is not available in the current release. Your effective access combines every role you hold, including inherited roles. For roles without admin access, a deny wins over an allow. Selecting a narrower role keeps denies from all your held roles. See Act as a role for how access is gated today and how to request it.Related
OAuth scopes
Every scope Dippr issues, what it lets a client do, and who can hold it.
Entitlements
Which features and engine sizes your tenant’s plan unlocks.
Routine confirmation
Analysts can save and start personal work withAgentTask · create and AgentTask · update. An explicit personal start through MCP or dip needs a verified person but no console confirmation. Editing, scheduling, deleting, confirming and discarding work uses AgentTask · update. Changing Read only or May propose changes uses the same update grant and is owner-only; widening is logged. May propose changes never approves execution.
Legacy draft confirmation and per-person subscription still require signing into the console within the last 10 minutes. Scheduled write approval requires the owner in a valid console session, with no additional ten-minute freshness requirement. A dip or MCP bearer is refused even with review scope. Administrators cannot confirm or approve another person’s work, and MANUAL task review is unchanged.
Viewers with AgentTask · read can subscribe to an active owner-access routine from a fresh console sign-in. They can see that it ran and its status; item views for people other than the run owner are coming. This creates no execution grant. Authorizing a per-person run additionally requires AgentTask · create (analyst or equivalent). Summary prose and steps built with someone else’s access remain hidden.
The built-in routine runner can read a workspace database when the person whose access the run uses can read it, within installation consent. Ordinary role wildcards and app consent still require a named workspace-database grant. Sharing a workspace database grants read access; it does not grant writes. After an unshare or revoke, subsequent queries refuse access once the policy update arrives. Already retained results and model input are not recalled.