Page History
This page follows the data that iDNA Applications reads from your Notes environment. It covers where the data is stored, how it is processed, who sees it, and what leaves your network, including to AI clients. The reading itself is described on What iDNA Applications Reads from Your Notes EnvironmentData Collection and Access.
| Table of Contents | ||
|---|---|---|
|
...
- Read: iDNA reads from your Domino servers with the collection Notes ID
(see What iDNA Applications Reads from Your Notes EnvironmentData Collection and Access). - Stored on the appliance, a Linux host in your network.
- Processed every night on the appliance into the analyses.
- Shown to the people you give an iDNA login.
- Retrieved by AI clients, only if you enable the MCP server.
For reviews by a works council, a data-protection officer or a compliance function, panagenda provides two documents. The AI position paper covers the iDNA Applications Companion and the MCP server and is available from panagenda on request. The note on user name pseudonymization is available in English and German. This page summarises summarizes both. Where a detail matters, the documents apply.
...
- Pseudonymization is the default. iDNA replaces user names in the per-user usage analyses with a pseudonym derived from the name. These analyses are who used which application and when, the per-user summaries, the license analysis, and the editor statistics of the content analysis. A person keeps the same pseudonym over time, so trends still work. The organisation organization part of the Notes name stays readable.
- It is pseudonymization, not anonymization. iDNA has no function that turns a pseudonym back into a name, but anyone who holds the list of names and the method can rebuild the mapping.
- Small departments and locations: while pseudonymization is on, a department or location with fewer than 15 assigned users is shown under a placeholder. The license can set another threshold. The row and its figures stay, so totals still add up.
- Shown with real names on purpose: access-control entries, agent signers, group memberships, the people who last changed profile documentsProfile Documents, who last accessed and who last wrote to each application, person documents from the Domino Directory, and MarvelClient data. These describe permissions, responsibilities and recent use. They are not intended for assessing anyone's work.
- Switching it off takes a new license. panagenda issues it only after your organisation organization has confirmed in writing that it has taken the necessary internal steps, including with the works council. On a trial license, the usage analysis is always pseudonymized.
...
The MCP server lets an AI assistant that your organisation organization already uses retrieve analysis results from iDNA. The AI position paper describes it in full. In short:
- Off by default. Your organisation organization requests it from panagenda as a license option, and your administrator switches it on. Your organisation organization acknowledges the position paper when it opts in.
- Restricted mode is the default: a fixed set of tools, no ad-hoc queries, no per-user analysis tool and no access to the tables that record individual activity. The AI sees application metadata, aggregates and source code. Notes records some names as part of an application, for example access-control entries and agent signers. The server's database account can read them, but no current restricted-mode tool returns them.
- Permissive mode (ad-hoc queries and per-user analysis) must be chosen deliberately, as a separate license decision.
- Access: every user gets a personal access token, valid for 365 days by default. All tokens have the same data scope. The appliance records every tool call in an audit log.
- Where results go: tool results travel over HTTPS to the user's assistant platform and into the AI model's context. From there, storage, retention and use are governed by your organisationorganization's contract with the platform's vendor. In its default configuration the MCP server opens no connection to any external service.
- Purpose: the AI components are intended for application portfolio analysis. They are not intended for monitoring or evaluating individual employees.
Setup: Setting up the MCP Server and Setting up iDNA Applications Companion.
Related Topics
- What iDNA Applications Reads from Your Notes EnvironmentData Collection and Access: what is read, the access it needs, the connections to Domino.
- iDNA Applications License Types and Options: license types and options, including pseudonymization and MCP.
- iDNA Applications Trial License: what a trial reads, analyzes and shows.
- Setting up the MCP Server: enabling the MCP server and issuing tokens.
- Content Age and Data Retention Analysis in iDNA Applications: what content age measures.
- SSL Certificate: using your own certificate for port 443.
- User Roles (Authority): the Portal roles.
- LDAP Settings: logins through your LDAP directory.
- Appliance Maintenance and Updates: software updates.
- Download Log Files: support bundles.
- Configuration: Usage by Organizational Units: department and location data.
