Page History
...
- the license type: trial, engagement or subscription
- how long iDNA collects data and how long the data stay stays accessible afterwards
- which HCL Domino servers can be analyzed (by certifier)
- which content packages are available
- two options that matter in a security or privacy review:
- whether user and small department names are pseudonymized
- whether and how AI clients may access iDNA's data through the MCP server
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. See iDNA Applications Data Collection and Access.
License Types
Trial
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.
- What it reads: the same as a subscription, from the same servers and content packages.
- What it analyzes per server: Notes client and web sessions, the Domino Directory, server configuration and the database catalog; with . With the optional content packages, also the Domino event log, mail routing, HCL DLAU and MarvelClient data.
- What it analyzes per application: the design of every focus database; Focus Database and, depending on license options, the source code from of a subset of databases. Document profiles Profile Documents and content age are analyzed for a sample of about 50 databases, which iDNA selects itself from the middle of the pack in usage and complexity.
- What you see: the sample in full. All other applications are counted in every total but shown with masked names.
- User names and small department names are always pseudonymized.
- Upgrade: the data collected during the trial stay stays available when the installation is upgraded to a subscription.
...
An engagement license runs for three months and includes all features, without a sample and without masked application 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 extend it to a full subscription, or with a extend it for 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 . A usage and complexity subscription includes the usage analysis and the design complexity, but not the detailed source code analysis.
...
When any license expires, iDNA stops collecting and processing data. The data collected so far stay stays on the appliance. How long they remain it remains accessible after expiry is set in the license.
...
- Each name is replaced by a pseudonym derived from it. A person keeps the same pseudonym, so trends over time still work. The organization part of the Notes name stays readable (example: edf224d918d55f0da97e/ACME).
- Departments and locations with fewer than 15 assigned user names are shown as a placeholder; their . Their usage still counts in every total. The license can set another threshold.
- Some data are is shown with real names on purpose, whatever the setting: access-control entries, agent signers and , group memberships, the people who last changed Profile Documents, who last accessed and last wrote to each application, and person documents from the Domino Directory, and MarvelClient data.
- The collected data are is stored with real names on the appliance in your network. Pseudonymization is applied when iDNA prepares the data for the analyses.
...
Who sees which data, and how pseudonymized data move moves through iDNA: iDNA Applications Data Flow in Detail.
...
- License without MCP (the default): the MCP server has no access to iDNA's data.
- Restricted mode: the AI works with an allowlist of iDNA's data; the . The detailed user-activity tables are excluded.
- Permissive mode: the AI can access all of iDNA's analysis data, including detailed user activity.
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 application names. MCP is available on every license type, including a trial. Data that the AI retrieves become becomes part of the AI conversation and are is processed by the AI platform your organization uses.
...
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 . The data collected so far stay stays on the appliance.
Related Topics
- iDNA Applications Trial LicenseWhat
- iDNA Applications Reads from Your Notes EnvironmentData Collection and Access
- iDNA Applications Data Flow in Detail
- Setting up the MCP Server
