Feedback Ideas

NIM currently supports only two access levels: FULL or APPS-only. It would be helpful to have an "admin light" security level for junior admins to manage existing source syncs and run existing schedules/jobs when needed, but not be able to make changes to role model, mappings, filters, or what-have-you.

Allow a temporary increase to thresholds in jobs. I have seen several customer NIM environments recently where they had adjusted the job thresholds to allow for the spike in enrollment changes at the beginning of the school year. It was set to really high number and they had forgotten to set it back to a modest number. In one instance, the customer had ALL of their employee's Google groups removed.

There would be some potential benefit in having an Admin Dashboard when you login to the NIM Studio. Essentially providing an overall health status for the service. Here are some key items you would see System/Filters/Jobs/Scheduler StatusesLicense StatusBackup StatusConnector/Service UpdatesConfiguration RecommendationsRecent Error logs Attached is a concept of the information that could be presented

It would be nice to be able to structure & reorder roles either through folders, or child roles akin to filters.

Provide the option to attach files to mail templates. Perhaps we can provide the ability to specify an attachment(s) by specifying a path, filter or audit query.

It's no fun getting evaluation reports every hour that show zero changes to be made. An option to only send evaluation reports when there are changes to be made in the target systems would be nice.

This has been asked/requested by a few, so building a feedback item here for further input and research. Why it matters: Some laws and standards (like HIPAA for healthcare or PCI-DSS for payment systems) say you must encrypt personal or sensitive data to keep it safe from hackers or leaks.Encrypting inside NIM: You should be able to choose specific fields in your system tables (like passwords or SSN) and encrypt them using a key that only NIM admin controls. This keeps the data safe even if someone gets access to the database.Encrypting exported data: If you export data from NIM (for reports, backups, or sharing with partners), allow the file to be encrypted using an admin-provided key. That way, the data stays protected even outside the system. Recommendations per industry standards Use secure connections: Always send data over HTTPS with the latest version of TLS (like TLS 1.2 or 1.3). This keeps the data encrypted while it’s traveling.Strong encryption: Use trusted methods like AES-256 (for encrypting data) and RSA (for sharing keys securely). These are widely accepted and hard to break.Protect your keys: Store encryption keys in secure places like a key vault or hardware security module. Rotate them regularly and limit who can access them.Verify the data: Add digital signatures or checksums so the receiving system can confirm the data wasn’t changed or tampered with.Follow the rules: Make sure you’re meeting standards like GDPR (for privacy), NIST (for government systems), or ISO 27001 (for general security). These help you stay compliant and avoid fines

If Roles could be tagged with a Type, then when scheduled, rather than just selecting groupMembership -> target it could be groupMembership ->target to only run the specific tagged roles for that target. This could allow separation of Role concerns (e.g. Students roles not running Employee roles).

Currently, you have to export all columns that are turned on in a filter. This prevents you from using ordering on data that you don't want in the export. There should be an option to select which columns that are present in the filter that we want to export in the scheduler's export and multi-export options.

In Privileged Identity Management, elevated rights are typically granted on a temporary basis (e.g., 8 hours). NIM should have native functionality to support this directly. While some target systems offer time-bound permissions, a centralized approach within NIM would provide greater control and consistency. This perhaps is related to https://feedback.nimsuite.com/b/5v84550g/feature-ideas/workflows

Currently NIM does not use the data types and keys from the connector. To simplify the process in adding an new system this should be automatically loaded and used. Additionally it would be beneficial if relations would be defined and used in the connector too.

There are instances in apps where we need to call scripts/commands outside the capability of NIM. E.g. running DACLS.exe when generating a new OU in AD to configure permissions, or custom PowerShell scripts that perform actions outside the scope of NIM.

Should have the ability to write to a Google sheet like it does with creating a csv export

Presently, the Membership tab of a role displays the Group ID, Group Display Name, and Member ID. Without a Member Display Name, this view is useless except for validating that the role has more than zero members. It would be infinitely more useful if we could see the name of the members in this view as well.

A key concept within the Role Model is implementing Segregation of Duties (SoD) or preventing Toxic Role Combinations to enhance security and compliance. This feature would ensure that conflicting roles are not assigned to the same individual, reducing the risk of fraud or misuse of privileges. Possible Implementation Approaches: Defining Conflicting Roles – Explicitly specify roles that cannot be held by the same user. Example: If your Role Model includes three roles—Employee, HR, and Payroll—you could define a rule stating that members of the HR role cannot also be assigned the Payroll role. This prevents HR employees from processing payroll, reducing the risk of internal fraud.Defining Conflicting Target Resource – Explicitly specify target resources that cannot be held by the same user. Example: In financial workflows, a system could enforce a rule that the person approving payments cannot also be responsible for issuing checks, ensuring a proper checks-and-balances system. By enforcing these restrictions, the Role Model ensures accountability and minimizes security risks associated with excessive or conflicting permissions.