Interno: Roles & Permissions Reference

Interno: Roles & Permissions Reference

Overview

Access to each part of Interno is controlled by permission scopes. Interno's own scopes all begin with defence:. This article lists the scopes that Interno checks and what each one unlocks.

This page covers Interno only. For every product's scopes in one place, see the Zeron Platform: Complete Permissions & RBAC Reference.


Prerequisites

  • The zitadel:iam permission, which is what gates the Admin > Management area where users, groups and policies are maintained
  • The list of scopes you intend to grant (below)

How Permissions Work

  • A scope is a single permission string, for example defence:dashboard:view.
  • Policies bundle scopes; groups bundle policies. Adding a user to a group is the recommended way to grant access, because everyone in the group stays consistent.
  • If a user does not hold the scope a page requires, Interno shows an Unauthorized screen instead of the page.
  • A user who holds no permissions at all sees the Unauthorized screen on every Interno page.
  • Where a row below lists two scopes joined by "or", holding either one is enough.
  • Some buttons are shown or hidden by one scope while the action behind them is checked against another. Those cases are called out under each table.
  • Users, groups and departments are maintained under Admin > Management. That whole area is visible only to users holding zitadel:iam.

Scope Reference

Dashboards

To do thisScope
Open dashboards, and the Asset Inventory pagedefence:dashboard:view
Create a dashboard, use AI dashboard/widget suggestions, import a dashboarddefence:dashboard:create
Edit a dashboard (rearrange widgets, save layout changes)defence:dashboard:update
Delete a dashboarddefence:dashboard:delete

Export Dashboard needs only defence:dashboard:view. Set As Default saves a change to the dashboard, so it requires defence:dashboard:update.

Widgets

To do thisScope
See saved widgets and the widget librarydefence:widget:view
Create or duplicate a widgetdefence:widget:create
Update a widgetdefence:widget:update or defence:widget:create
Link or unlink a drill-down widgetdefence:widget:update
Delete a widgetdefence:widget:delete
Load the data behind a widget, or preview a querydefence:widget:view or defence:dashboard:view

The Asset Coverage Matrix and User Access Coverage tabs in Asset Inventory are served as widgets, so viewing them also requires defence:widget:view. The scopes defence:widget:data:view and defence:widget:visualize exist in the permission list but no Interno screen or action currently depends on them.

Queries and Alerts

To do thisScope
View queries and alertsdefence:query:view
Create a query or alertdefence:query:create
Edit a query or alertdefence:query:update
Delete a query or alertdefence:query:delete
Run a query or alertdefence:query:execute

Manual Ingestion

To do thisScope
Open the Manual Ingestion page and its historydefence:manual-ingest:view
Start an uploaddefence:manual-ingest:create
Review and approve uploaded datadefence:manual-ingest:review

Those three scopes decide what the page shows. The work itself — loading the list of uploads, previewing rows, submitting an upload, approving and rejecting — is all checked against defence:query:execute. Grant it to everyone who uses Manual Ingestion, including people who only view.

Integrations

To do thisScope
See the Integrations page and the connector cataloguedefence:integration:view
See the credentials saved for a tool, and their scan historydefence:integration:credentials:view
Add an integration, edit an existing one, start a scan, activate or deactivatedefence:integration:credentials:create
Delete an integrationdefence:integration:credentials:delete

Editing an integration is deliberately gated on the same scope as creating one — there is no separate "edit" scope.

Risk Register

To do thisScope
View risksdefence:risk:view
See the Create Risk buttondefence:risk:create
Open a risk and work through its four stepsdefence:risk:manage
Save a new riskdefence:risk:create or defence:risk:manage
Save a step, or attach evidencedefence:risk:update or defence:risk:manage
Delete a riskdefence:risk:delete or defence:risk:manage
View documents attached to a riskdefence:risk:documents:view

In practice a person who raises and works risks needs defence:risk:view, defence:risk:create, defence:risk:manage and defence:risk:documents:view together. Holding defence:risk:manage alone does not show the Create Risk button, and holding defence:risk:update alone does not open a risk. There is no delete action for risks on any Interno screen, whatever scopes are held.

Evidence Queries (shared with Conformity)

To do thisScope
See the Evidence tab in the Query Librarygrc:evidence:view
Create or delete an evidence querygrc:evidence:create

Suggested Combinations

Read-only analyst defence:dashboard:view, defence:widget:view, defence:query:view, defence:integration:view, defence:integration:credentials:view, defence:risk:view, defence:risk:documents:view

Full Interno user All defence:* scopes above. Add grc:evidence:view and grc:evidence:create if the person works with evidence queries.

Administrator The full Interno user set plus zitadel:iam, so they can manage users, groups and departments.


Troubleshooting

A user sees the "Unauthorized" screen on a page → Their group is missing that page's scope. Find the row above and add the scope to the group's policy.

A user can open dashboards but cannot rearrange widgets → Editing a dashboard layout requires defence:dashboard:update. Adding widgets to it also needs defence:widget:view.

A user cannot see the Create button on the Dashboard page → That button appears only if the user holds at least one of defence:dashboard:create, defence:widget:create or defence:query:create.

A user cannot add or edit an integration → Add defence:integration:credentials:create in addition to defence:integration:view.

A user can open the Manual Ingestion page but the table is empty or the upload fails → Grant defence:query:execute alongside the defence:manual-ingest: scopes.

A user can see the Risk Register but clicking a risk shows Unauthorized → Opening a risk needs defence:risk:manage.

A user can open a tool's panel under Integrations but sees an Unauthorized image where the credentials should be → Add defence:integration:credentials:view.

An administrator cannot reach Admin > Management → That area requires zitadel:iam.


Need more help? Contact support@zeron.one