Feedback Ideas

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.

Password Reset module of NIM provides a multitude of possibilities but it's prime function is Account recovery via password reset. Previously SSRPM provide a landing page for multiple options (Enroll, Reset Password, Unlock, Manage Attributes, Lookup Username) NIM should provide an option to have a landing page that can provide options for different Password Reset profiles (e.g. Reset Password, Unlock Only). This provides a simple point of entry. Expansion on this is to allow only certain hostnames to be allowed. For example if my nim host name is "nim.domain.com", I maybe want to have password reset point to "reset.domain.com". This would mean then if I go to "reset.domain.com" I would land on the dashboard page to select my option.

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.

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.

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

We would like a feature-rich SQL editor to be added to NIM, particularly when working with the various Systems and Tables. It is difficult to only have the single line for each System Query's SQL Statement, necessitating the use of an external text editor to copy/paste which often loses formatting (besides the simple fact that copy and pasting back and forth is not the most efficient way to work) - it also leads to errors. It would be great to have a formal SQL editor which would not only allow multi-line view but also the ability to format, highlight, color, etc. - all of which would help us with troubleshooting problems and avoiding errors because of the difficulty we currently encounter. Having an integrated SQL editor would be extremely helpful for our workflow, and it would allow us to do so much more than we are able to at present.

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.

When an update for NIM is detected, the patch/release notes should be pulled down into NIM studio and displayed there before an update is applied. Current implementation: On Studio->Settings->Version page. "Current version: some version number" "Latest version: some version number" Customer is asking: Is it worth the potential downtime to upgrade? No justification is provided other than "it's a bigger number". Customer has to review patch/release notes on https://feedback.nimsuite.com/announcements or some other channel. Possible future implementation: On Studio->Settings->Version page. "Current version: some version number" "Latest version: some version number" Within a nearby text box or field: "Release notes for version some version number... (the full release notes follow here)" Another candidate location may be the NIM overview page, since it is often the default page when logging into the Studio application.

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.

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.

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.

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).

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.

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.