Manage semantic permissions
As an administrator, you can control which semantic layers users and groups can query, and how much of each layer they reach. You can give them access to the full model, or only to the domains you choose. This guide explains how to set those permissions and how to check a user's access.
Available in Coginiti Team and Coginiti Enterprise only.
How domain access works
Permissions are set on one semantic layer at a time, and within a layer on individual domains:
| Piece | Where it lives | Who sets it |
|---|---|---|
| The domains — the governed schemas themselves | The semantic model, in SMDL | Whoever writes the model |
| The access mode — whether the layer is governed at all | Coginiti, on each layer | An administrator |
| The grants — what each user or group may query | Coginiti, on each domain | An administrator |
The model declares domains, but it never names a user or a group. Access is administered in Coginiti, so granting or revoking it does not mean editing and redeploying the model.
A user who has not been granted a domain can neither list it nor query it. The semantic layer registers only the schemas that user may read, so the domain does not appear when a BI tool browses the connection, and a connection that names it is refused:
domain 'emea_sales' is not available: it does not exist, or you have not been granted access to it. Ask an administrator to grant you access
One message covers both causes, so the refusal does not disclose the names of your domains. The JDBC guide shows where a connection names a domain.
The semantic layer applies these permissions, so a client that reaches the warehouse another way is not constrained by them: a direct database connection or a BI tool with its own credentials reads the tables as the warehouse allows. To restrict those paths as well, configure warehouse-native policies such as row-level security separately.
Prerequisites
- Coginiti Team or Enterprise, and an account with the Admin role
- A project published to the Project Hub whose manifest declares a semantic layer. See Project Hub
- Optionally, domains declared in that layer. See Domains in the Semantic Model Reference
You can administer a layer that declares no domains. Its ungoverned public
schema can still be granted or withheld; there is nothing finer to grant
alongside it.
Step 1: Open the Permissions screen
- Open Admin Settings.
- Go to Semantic Layer → Permissions.
The left-hand list shows every semantic layer you can configure, with a Search layers box for long lists. A layer appears here when a project you can view is published to the Project Hub and declares a layer in its manifest.
Only published projects can be governed. A project in someone's home folder is reachable only by its owner, so its layers never appear on this screen.
Step 2: Choose the access mode
Select a layer. Access mode is at the top of the details pane:
| Mode | What it means |
|---|---|
| Open to everyone | Everyone who reaches this layer can query the public schema and every domain |
| Granted explicitly | A user can query only what they, or a group they belong to, have been granted |
A layer nobody has configured is Open to everyone, including every layer that existed before domain access. Selecting Granted explicitly turns governance on for that layer alone. Administrators see everything in either mode.
If you select Granted explicitly before granting access, every non-administrator loses access to the layer, including the people you are about to grant. Grant access first in Step 3, then change the mode. Grants on a layer that is open to everyone are stored without being enforced, so you can write them in advance.
Switching a layer back to Open to everyone suspends its grants instead of deleting them, so selecting Granted explicitly later enforces the same grants again. Revoke the grant itself, in Step 3, to remove someone's access.
Step 3: Grant access to domains
The Domains column lists Full model first, then the domain rows in
groups. Full model and public both grant broadly, in different ways: read
Full model and public before granting either.
The groups are:
| Group | What it holds |
|---|---|
| Domains declared by the model | The domains the model currently declares, with the ungoverned public schema first among them. Shows This layer declares no domains. when the model declares none |
| Domains no longer declared | A domain that a grant still names and the model has since dropped |
| Named by a grant, not confirmed | A domain that a grant names while the model declares nothing at all |
The last two groups keep existing grants visible, so you can revoke access that names a domain the model no longer has.
The two groups mean different things. Domains no longer declared means the model declares other domains and this one is genuinely gone. Named by a grant, not confirmed means the layer returned no domains at all, which is also what Coginiti sees when the semantic layer server is unreachable. Check that the server is running before you treat those rows as stale.
To grant access:
- Select a domain, or Full model, in the Domains column.
- In Available, find the user or group. The filter box narrows a long list.
- Select it and move it to Granted.
- Repeat for each domain that user or group should reach.
- Click Save.
To revoke access, select the domain, move the user or group out of Granted, and click Save.
Granting a group grants access to every member. A user who is granted access personally and through a group can query the domains from both grants.
Full model and public
Full model and public have similar names and grant different access:
| Row | What it grants |
|---|---|
| Full model | The whole layer: the public schema and every domain the model declares, including domains declared later |
| public | The ungoverned public schema alone, and none of the domains projected over it |
The JDBC and ODBC guides call the public schema the full model, because it is
what a connection reads when it names no domain. On this screen, Full model
grants more than that: the public schema and every domain.
Full model access is exclusive. Granting it replaces whatever domains that user or group had, because it already covers them. They then appear in every domain's Granted list, marked via full model, and you cannot remove them from an individual domain. To give someone specific domains again, revoke their Full model access first.
public is an ordinary domain row. A user or group can have it alongside any number of named domains, and you grant and revoke each row separately.
public grants every domain's rowsA domain is a projection of the model, so a user who can query public reads
every domain's rows through it, with no domain filter applied, including the rows
of domains you did not grant them. A grant decides which schemas a user may
connect to and name in a query, not which rows they see.
Grant public to the people who are meant to see the ungoverned model, and
named domains to everyone else.
Setting permissions in bulk
Use the permissions API to set the access mode and the grants for several layers, or to make access part of a provisioning script. The API performs the same operations as this screen. See Permissions in the API Reference.
Step 4: Check what the user sees
Sign in with a non-administrator test account and open a connection to the semantic layer. Your own account is no use for this check: an administrator sees every layer and domain in both modes.
A user's grants decide three things:
- The Semantic Layer dropdown offers only the layers they can read, meaning a layer where they have Full model access or at least one domain. Other layers are absent from the list.
- The Domain dropdown offers the domains they are granted, with
publicfirst when they can read the ungoverned model, through eitherpublicitself or Full model. - A connection to a layer they may not read is refused when it is opened, so the user sees an error instead of an empty schema list.
A connection that names no layer resolves to the project's default layer when the user can read it, and otherwise to the first layer they can read.
See Connect to the semantic layer over JDBC for how a connection names a layer and a domain.
Troubleshooting
A layer is missing from the Permissions screen
The project is not published to the Project Hub, its manifest declares no semantic layer, or you cannot view the project. Only published projects can be governed.
A user sees no layers at all in the connection editor
They have no grants on any layer of that project. Check that the layer's access mode is the one you intended: a layer set to Granted explicitly with no grants on it is invisible to every non-administrator, which looks the same as a broken connection.
A user was granted a domain but still sees nothing
Check that the model still declares that domain. A grant naming a dropped domain still shows the layer in the Semantic Layer dropdown, because grants alone decide which layers appear, but the domain itself is gone, so there is nothing to query. The screen lists such a grant under Domains no longer declared.
An administrator sees everything regardless of grants
Administrators bypass domain access in both modes, by design. To see what a particular user sees, test with a non-administrator account.
Related tasks
- Set up semantic tenants restricts rows by customer, and composes with the domain restrictions here
- Domains in the Semantic Model Reference covers declaring the domains this screen grants
- Permissions in the API Reference covers setting the mode and the grants over HTTP
- Sharing a project with a semantic layer