Skip to content

IRMA: functional and technical administration

This page is for your organization’s functional administrator (in IRMA the Beheerder (Administrator) role) and for the technical administrator or IT department that connects IRMA to other systems. It explains how access works, which integrations there are, how another system retrieves data from IRMA and what you can do when the agreement ends.

How to use the app is covered in IRMA: getting started. The day-to-day administration items (roles, departments, taxonomy, service tokens, audit trail and Trust Center) are covered in IRMA: administration. This page bundles what an administrator needs besides that.

The IRMA app is in Dutch. This page quotes its labels in Dutch, with an English gloss in parentheses. What you see depends on the modules turned on for your organization and on your role. You only see Beheer (Administration) with administrator rights.

WhatWho
Roles, departments, tasks, statuses, notifications, risk taxonomy, importing, Trust Center, tokensYour organization’s Beheerder, in the IRMA app
Inviting users and membership of the organizationYour organization’s Eigenaar (Owner) in the Account Dashboard, see Signing in & choosing a persona
Signing in with Microsoft (SSO)Your IT administrator, together with Prudai: Setting up SSO (Microsoft) + SharePoint
Turning menu sections and other functions on or off, IRMA Management for the assistantPrudai, on request via support@prudai.com
Hosting, backups, updates and the availability of the servicePrudai

You sign in to IRMA with your Prudai account, the same account as in the Prudai web app. That can be with email and password or with single sign-on through Microsoft.

  • Microsoft (Entra ID). With SSO, employees sign in with their own Microsoft account; the multi-factor authentication and access policy of your own Microsoft environment then applies, such as conditional access. The steps for your IT administrator are in Setting up SSO (Microsoft) + SharePoint.
  • Multi-factor authentication. Users can set up a second factor with an authenticator app or a passkey. For accounts without SSO, Prudai can make MFA mandatory for your whole organization; ask for it via support@prudai.com.
  • Other identity providers. Signing in through SAML with another identity provider and automatic creation of users (provisioning) are not part of the standard service. Users are invited and managed by your organization’s owner.
  • No access. If IRMA is not active or is blocked for your organization, the app shows a single screen with the reason. See Access.
  • Browsers. IRMA works in a common browser without plug-ins; see Access & requirements.

An employee needs a Prudai account and, in IRMA, a role.

  1. Your organization’s owner invites the employee in the Account Dashboard.
  2. An administrator gives the employee a role under Beheer → Rollenbeheer (Role management): open the role, go to the Gebruikers (Users) tab and under Gebruiker toewijzen (Assign user) enter the user ID (Keycloak sub). If you do not know the ID, ask support@prudai.com.
  3. Which rights a role has, you set per section with the Rechtenmatrix (Rights matrix): Lezen (Read), Aanmaken (Create), Bewerken (Edit) and Verwijderen (Delete). You can adjust the twelve standard roles and create roles of your own.

Everything about this, with the list of standard roles, is under Roles and rights. Someone with several roles has the rights combined. Someone who signs in without a role can read everything and change nothing. If you want employees to read only their own department, set up read access per department.

  1. Record the offboarding under Beheer → Uitdiensttreding (Offboarding). Click Toevoegen (Add) and choose the Medewerker (Employee), the Functie (Position) and the Laatste werkdag (Last working day). The checklist comes from your organization’s template; compile that template with Checklist-sjabloon beheren (Manage checklist template) and tick off the steps during the offboarding.
  2. Withdraw the employee’s access to linked systems. You revoke their personal tokens (see below) under Beheer → Persoonlijke tokens (Personal tokens); revoking takes effect immediately and cannot be undone.
  3. Remove them from their roles on the Gebruikers tab of the role, or have your organization’s owner delete their account in the Account Dashboard.
  4. Reassign what they owned in IRMA. Risks, controls and tasks have an owner.

Under Instellingen (Settings) → Integraties (Integrations) is the list of integrations. Everything is optional; IRMA works without. Each integration shows its status: Werkend (Working), Wacht op configuratie (Waiting for configuration) or Nog niet gekoppeld (Not linked yet). An integration with the status Nog niet gekoppeld does not exchange any data yet.

IntegrationWhat it does
Outlook / e-mail (notificaties)IRMA mails the action holder on a new action, a completed action, a reminder, an escalation and a new data breach, if the recipient’s email address is known. The sender is irma@prudai.com.
Webhook (generiek koppelvlak) (Webhook, generic interface)IRMA sends a JSON message per event (the same events as the mail) to a URL of yours. Every message is signed (HMAC-SHA256), so the receiver can check that it comes from IRMA. Only an https address is allowed.
Microsoft 365 (bewijsmonitor) (Evidence monitor)IRMA collects evidence daily from your own Microsoft 365, see below.

With the card Microsoft 365 koppelen (Link Microsoft 365) under Instellingen → Integraties you let IRMA collect evidence daily from your own Microsoft 365 environment.

  • IRMA only reads counts and scores: how many accounts there are (on or off, employees or guests, new), how many changes the directory audit log recorded in the past 30 days, and your Microsoft Secure Score with the MFA components in it. IRMA does not read or keep names, email addresses or the content of mail or documents. IRMA changes nothing in your Microsoft 365; no write permission was requested.
  • A global administrator of your Microsoft 365 (or an administrator of privileged roles) gives consent once through Koppel je Microsoft 365 (Link your Microsoft 365). Sign in with an account of your own of the organization you are linking, not a guest account.
  • The card shows the status: Actief (Active), Gekoppeld, nog niet gecontroleerd (Linked, not checked yet), Geen toestemming (No consent), Toestemming ingetrokken (Consent withdrawn) or Storing (Fault), with the Tenant-id, Gekoppeld op (Linked on) and the Laatste run (Last run).
  • With Ontkoppelen (Unlink) IRMA no longer collects new evidence. The evidence already collected stays. If you really want to take IRMA’s access away, withdraw the consent at Microsoft in the Microsoft Entra admin center.

A system or script of your own does not need a user; it works with a token.

  • Service token (Beheer → Service-tokens). A key for an integration or script of your organization. You give it a Naam (Name) and choose per section what the token may do: read, create and change, or delete. A token can never do more than your organization can in IRMA. You see the secret key once; IRMA only keeps a derived value. With Intrekken (Revoke) you stop a token immediately. The steps are under Service tokens.
  • Personal token (Instellingen → Persoonlijke tokens). An employee creates it themselves by linking the IRMA CLI with irma auth login. It belongs to that employee and to one organization and is valid for 90 days. It works with their rights; in the audit trail every change shows that it went through a token. An administrator sees and revokes all personal tokens of the organization under Beheer → Persoonlijke tokens.

Retrieving data for a BI tool or data warehouse

Section titled “Retrieving data for a BI tool or data warehouse”

A BI tool, an ETL process or a data warehouse retrieves data from IRMA through the API, in JSON.

  • Retrieval is a pull: your system requests the data, for example every night with a token. IRMA itself does not send data to a data warehouse.
  • Every answer contains, besides the data, the context, how many rows there are in total and what was deliberately left out, so that a part is not mistaken for the whole. Lists are paginated. See Concepts and Recipes.
  • With a personal token you see exactly what that employee may see in the app. With a service token, the rights you choose when creating it determine what the token may do.
  • For a one-off or manual export, use Exporteren (Export) in a table, see IRMA: reporting, import and export.

The connection and the description of the API are in IRMA for developers, with a quickstart and a CLI reference. For a connection to a specific tool, contact support@prudai.com.

IRMA records who did what. The Audittrail (Audit trail) under Beheer is immutable: lines cannot be changed or deleted, and every line is linked to the previous one. You filter on action, kind of object, actor and period, see whether a change was made by a user, the assistant or the system, and with Ketting verifiëren (Verify chain) check that the trail is intact. Sensitive views are in it too: downloads of reports, evidence files and incident attachments, and the Records management export. An Excel or CSV export of a table is not. See Audit trail.

Signing in itself (logins and failed attempts) is recorded in Prudai’s sign-in system and not in IRMA’s audit trail.

Taking your data with you and the end of the agreement

Section titled “Taking your data with you and the end of the agreement”

You keep control over your data. During the term you can retrieve data from IRMA yourself:

  • tables and registers as Excel or CSV, see Exporting;
  • reports as PDF, Word or Excel;
  • evidence files and incident attachments, one by one;
  • records from Informatiebeheer (Records management) as XML or JSON;
  • data through the API, with a token, see Retrieving data for a BI tool or data warehouse.

You request a full export of your organization’s data via support@prudai.com. The agreements on access after the end of the agreement, handover and deletion are in the Data Pro Statement that belongs to your agreement; you can find the official documents on Privacy & security. Irreversibly destroying the content of a record you do yourself, in a controlled way, in Informatiebeheer.