Who can do what
The three kinds of users in Cortex, what each one can do, how builder freedom is set and how to get access or a Studio seat.
Cortex has three kinds of users. Most people are the first kind, some also build, and a few administer. Each kind sees a bit more of the product than the one before, and nobody sees more than their role and their access allow. This page lists what each kind can do, who decides it, and how you get from one kind to the next.
Who can do this
This page is for everyone. It explains the roles; it does not change anything. The people who change roles are your IT administrators, in Cortex Control and in your organisation's Microsoft Entra.
Asks, opens what is shared, handles tasks, pins, subscribes, requests access.
Everything above, plus Studio: builds dashboards, apps, workflows and models.
Runs Cortex Control: people, approvals, policy, data sources, AI engine, licence.
The three roles
| Role | Who | What they can do |
|---|---|---|
| Everyone | Anyone who can sign in to Cortex Hub | Ask questions, open the dashboards, apps and workflows shared with them, handle tasks, pin values, subscribe to digests and alerts, request access to something they cannot open |
| Builder | People with a Studio seat | Everything above, plus Studio: build dashboards, apps and workflows, work on semantic models, documents and data sources |
| Admin | People with the Admin role in Cortex Control | Manage people and roles, decide requests, set policy and budgets, connect data sources, choose the AI engine, read the audit log, watch health |
You only see what your role allows. A person without a Studio seat has no Studio group in the menu. A person who is not an admin does not see Cortex Control.
What each role can do
| You want to | Everyone | Builder | Admin |
|---|---|---|---|
| Ask a question in Ask | Yes | Yes | Yes |
| Open what is shared with you | Yes | Yes | Yes |
| Handle tasks in the Inbox | Yes | Yes | Yes |
| Pin a value, subscribe to a digest or alert | Yes | Yes | Yes |
| Request access to something | Yes | Yes | Yes |
| Start a dashboard, app or workflow | No | Yes, as far as the builder permissions allow | Yes |
| Define and certify figures in a model | No | Only as an owner of that model | Yes |
| Publish a model, dashboard or workflow | No | As an owner, as far as the policy allows | Yes |
| Decide requests in Cortex Control (Approvals) | No | No | Yes |
| Set policy, budgets and builder permissions | No | No | Yes |
| Connect a data source, grant datasets | No | Requests access | Yes |
| Choose the AI engine | No | No | Yes |
| Read the audit log | No | No | Yes |
Everyone
If you can sign in, you can use the Hub. What you can open depends on what has been shared with you. A dashboard, app or workflow is shared with specific people, with a group or with the whole organisation, and its owner decides. Ask only answers with data you are allowed to see. See Access and security for how that works.
If you cannot open something, you can request access from the page itself. The owner or IT decides, and you see the answer in your Inbox on the Sent tab. See Access and sign-in.
Builders
A builder is someone with a Studio seat. Studio is the Hub's section for building. Builders describe what they want in a chat, and Cortex builds a dashboard, an app or a workflow with them. They also maintain the semantic models behind the numbers, and the owner of a model can certify its figures. See Start something and follow your requests.
What a builder may do without asking is set by your organisation, per kind of action: Create a workspace, Create an app, Create a workflow, Create a dashboard and Load ad-hoc data. For each one IT chooses:
| Mode | What happens |
|---|---|
| Allowed | The builder does it without asking. |
| Needs approval | The request goes to the admins, who decide in Approvals. |
| Admins only | Only an admin can do it. |
IT can also make exceptions for one person, a group or a workspace. See Builder permissions and policy. When a request lands in Approvals, an admin decides: see Approvals.
The number of Studio seats is part of your organisation's licence with VDS. IT sees how many are in use on the Licensing page: see Licence and seats.
Admins
Admins run Cortex Control. They decide who has access to what, decide requests, set policy, budgets and limits, connect data sources, choose and watch the AI engine, and read the audit log. The Admin role is granted in your organisation's Microsoft Entra, not inside Cortex itself. Studio seats are given in Control, under Studio users. See People and Studio users.
Being an admin does not give a free pass on data. The row rules and figure restrictions of a model apply to admins too. An admin does see tables that are hidden from others and fields that are masked for others (the Security tab of a model says who sees what). See Access and security.
How do I get access or a seat?
Ask your IT team. They can:
- give you access to Cortex,
- give you a Studio seat, as far as your licence allows,
- make you an admin of Cortex Control,
- or share a specific dashboard or app with you.
You can also ask the owner of a dashboard or app directly, or use Request access on the page.
Example: three people at Brightwater Foods
- Lotte, a production planner. Lotte signs in, asks "What was the scrap rate last week?" and opens the OEE dashboard that is shared with her. She has no Studio group in the menu and no Cortex Control. When she wants a new overview, she asks a builder or her IT team.
- Daan, a builder. Daan has a Studio seat. He describes "a dashboard for sales" in one sentence and reviews what Cortex builds. Creating a dashboard is set to Allowed, so the draft appears at once. Creating an app is set to Needs approval, so his app request waits for an admin.
- Sam de Vries, an admin. Sam sees Cortex Control. Sam approves Daan's app request, connects the ERP under Data and sets the monthly AI budget.
Signing in and your first minutes
How to sign in with your work account, what you see first, how to change language and appearance, and what to do when something is missing.
Find your way
Which part of this documentation to read first, depending on what you do with Cortex, and where to look up a specific task.