Every iDNA Applications appliance runs with one license file. panagenda issues it, and the iDNA administrator uploads it on the appliance. The license sets:
This page is for IT and security reviewers who evaluate iDNA Applications before or during a trial. What iDNA reads from your Notes/Domino environment and which access it needs is the same for every license type; see What iDNA Applications Reads from Your Notes Environment.
A trial license lets you evaluate iDNA Applications on your own Notes/Domino environment. It usually runs for 14 days and may be extended in special circumstances.
Everything a reviewer needs to approve and run a trial is on iDNA Applications Trial License.
An engagement license runs for three months and includes all features, without a sample and without masked names. It is meant for organizations that do not want to commit to a long-term subscription right away, but need a collection period long enough for meaningful results.
When the three months are over, iDNA stops collecting data. The data stays visible for up to six months after collection has ended. You can then continue with a full subscription, or with a usage-only subscription: the design and source code collected during the engagement stay available but are no longer updated.
A subscription license runs until its expiry date. A full subscription includes the usage, design and source code analysis; a usage-only subscription includes the usage analysis.
When any license expires, iDNA stops collecting and processing data. The data collected so far stay on the appliance. How long they remain accessible after expiry is set in the license.
Pseudonymization is the default. iDNA pseudonymizes user names in the per-user usage analyses: who used which application and when, per-user summaries, the license analysis and the editor statistics of the content analysis.
License without pseudonymization: the usage analyses show real names, and small departments and locations are named. panagenda issues such a license only after your organization has confirmed in writing that it has taken the necessary internal steps, including with the works council, and is responsible for the processing. The setting changes with a new license, in either direction. A trial license always pseudonymizes.
The note on user name pseudonymization is written for works councils, data-protection officers and compliance functions. It explains which user names iDNA pseudonymizes, which data it shows with real names on purpose, and what a license without pseudonymization requires. It describes iDNA Applications 3.5.0. Share it with the people who approve the evaluation.
English | German |
Who sees which data, and how pseudonymized data move through iDNA: iDNA Applications Data Flow in Detail.
With the MCP server, AI clients such as Claude, GitHub Copilot or OpenAI Codex can answer questions about your Notes/Domino estate from your iDNA data. The MCP server is off by default and free of charge. It needs a double opt-in: your organization requests an MCP license from panagenda, and the iDNA administrator then enables the MCP service on the appliance.
The MCP server reads the same prepared data as the dashboards: the pseudonymization setting applies to it, and on a trial it sees the same sample and masked names. MCP is available on every license type, including a trial. Data that the AI retrieves become part of the AI conversation and are processed by the AI platform your organization uses.
Setup, modes and tokens: Setting up the MCP Server.
To request a trial, an engagement or a subscription, or to change a license option, contact panagenda through the iDNA Applications contact form. On a trial or engagement license, the menu item [Upgrade your Experience] in iDNA opens the same form.
The iDNA administrator uploads the license file in [Settings] → [System configuration ...] → [License]: accept the General Terms and Conditions, choose the license file and click [Upload]. A new license replaces the previous one; the data collected so far stay on the appliance.
