Feedback Ideas

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

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.

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

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.

Provide the ability to define characters that should not be include in the random password generator

The action currently only takes in a static link. Being able to change the button based on factors within the app would be great. For example, I currently need to append a link with a specified user's UPN to continue our onboarding flow into an external service seamlessly, so the user does not need to input the same data twice.

I would love a way to do a global search across all relations, filters, mappings, jobs, templates, actions, etc. So when either developing a new process that may be similar to a current one you can "check all your boxes" (so to speak) or troubleshooting different automated tasks you can easily pull up anything related to a title (if you're already naming in a way so they all relate). Or even if it could search inside filters to pull the names of different data points that are being used to create that filter. If it helps to relate, the Global Find in Palo Alto firewalls dashboards is top notch!

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.

To protect NIM configuration natively, we should provide the ability to schedule automatically backups. This is beneficial when there are multiple NIM Administrators making configuration changes and often forget to back up their configuration.

A proposed enhancement to the product is the introduction of workflows, allowing requests to be reviewed and approved by designated reviewers before proceeding. This would be particularly beneficial in scenarios such as application access requests or provisioning processes, ensuring oversight and compliance. How Workflows Would Improve the Product Approval Mechanism – When a user submits a request (e.g., access to an application or a provisioning action), it enters a workflow where assigned reviewers must approve or reject it before execution. Role-Based Reviewers – Approval requests could be routed to specific individuals based on their roles (e.g., managers, security officers, or compliance teams). Multi-Step Approvals – Workflows could support multi-tiered approvals where different stakeholders must review a request at various stages. Audit and Compliance – Each approval or rejection would be logged, providing a clear audit trail for governance and regulatory requirements. Example Use Case A user requests access to an HR application. Instead of immediate access, the request follows this workflow: Step 1: The user's manager reviews and approves the request.Step 2: If approved, the HR department reviews and grants final approval.Step 3: Upon approval, the provisioning process assigns the necessary permissions automatically. By incorporating workflows, the product enhances security, ensures compliance, and streamlines access management while preventing unauthorized changes.

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

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

Organizations need the option brand NIM to help users know they are in the right place. Apps currently give you a level of that today but it needs to be expanded. The following elements should be considered. Change logo in the top right of AppsChange logo on login pageAbility to turn on/off "I forgot my password" link on login pageOption to change "I forgot my password" link on login page.Ability to add custom text to the login page (markdown support)Option to change label and placeholder text for field on login pageOption to change background for login page