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

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

Surprisingly, the "insert link" button is not available on the email template editor. It is available in the JODIT editor, but it is not available when creating an email template. Please add it.

Make it possible to user conditions in the email template We can do this in HelloID which is very useful. My example is the last name was changed for a user but not the first name. But the customer wants the names to be reflected in the email. The problem is since "givenName" wasn't updated it's not available as an argument even it's specified in the mapping So the result for "John Smith" would be "Smith" In HelloID we can do something like {​​​​​​​​​{​​​​​​​​​account.password||"No password"}​​​​​​​​​}​​​​​​​​​, wondering if have some similar logic here available. I think to expand on this we should have the following: If Null Example: If {var.event.argument.mail} is null then {var.event.input.mail} If statement Example: If {var.event.input.employeeType} == "student" && {var.event.argument.mail} != null then allow block of text with variables

Requiring a phone number for students to change passwords is a huge issue, especially for lower grade students who either do not have a phone or the current mandate is for students not to have a cell phone during school hours. There really needs to be an alternative that would allow users to change their password without a phone. Even having one time tokens that could be generated in NIM would be something.

Integrated with KnowBe4

It would be helpful to have the ability to do both full and incremental pulls on systems. If you're pulling a large amount of data via API. It's impractical to have a job run to pull a lot of data that isn't changing. There are also cost implications for many vendors either on # of query or data being pulled. The ability to schedule something like a full pull is made once a week to make sure the data set is complete, but the ability to schedule more frequent incremental updates would be a great option.

Provide a bulk input data via NIM App. For example, you have a CSV file you want to process to add group memberships or process some sort of action. All this done through the NIM App. Acceptable solutions could be file upload or pasting the text into a multi-line element

When designing apps, we need the option to be able to undo changes (e.g. CTRL-Z)

When using the App action Target System Function Execution, pressing Save will exit the mapping table. Desired result: Make it behave like Custom Columns in filters do now. Provide both 'Save' and a 'Save and Exit' buttons.

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.