HCL Domino Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
userlicenses.nsf considers logins within 30 days to be "active" users. That's a good default value but let the threshold be configurable. Would be nice if Domino would also consider agent activity as a login. That would prevent service accounts from being disabled. Alternatively, send LocalDomainAdmins an AdminP notification to approve disabling. They would know not to approve disabling an agent signer so it is no problem.
It depends what you define as inactive and how you would want to identify them. What about users that are on extended leave of absence? Just locking out a user (=deny access) will also lock any agents that are scheduled to run with this userID.
Let's go a step further. After x + y days, send LocalDomainAdmins a notice to approve an AdminP request to delete the account (and delete the Vault ID and delete the mail file and all its replicas). Letting this be pushed to admins and approving with a single button click will reduce security risks, reduce license cost, reduce server indexer load, and reduce backup times. Automatic to detect these accounts and then one click to approve the clean-up.