Feedback Ideas

I would like for the Azure/Entra connector to be able to set "Sponsors". We have an app allowing our departments to request accounts for external (non-HR-managed) accounts. I would like the user that submitted the external-account-request to be recorded as" sponsor" in the newly-created-identity's account properties so we know who to contact when that account is due for expiration or renewal.

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.

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

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

We have been live on password reset since mid-December 2025 and the biggest problem for our students using this tool is the generic "Internal Server Error" that shows when students have entered a invalid password. Mainly it seems that they are attempting to reuse an old password, so this does not show in the criteria, does not through an error that they understand. These instances represent the majority of the calls to our help desk for password resets. Making these errors more meaningful would go a long way toward serving our students.

Period slider in configuration -> Visuals -> Flow, add a way to pivot to a group of data (e.g. creates in a day, deletes in a day), to see an itemized list of the records affected and what changes.

Alberta has moved to a new year-round UTC-06:00 Mountain Time (Alberta) time zone. Windows supports the new time zone, and our NIM server is configured to use (UTC-06:00) Mountain Time (Alberta). However, NIM Scheduler does not appear to recognize or correctly respect this time zone. Scheduled tasks are being calculated at incorrect times. For example, a NIM task configured to run every day at 00:15 can show its next run as 18:15 on the previous day. We see the same pattern with other scheduled tasks. NIM Support has confirmed that NIM currently does not appear to respect the new Mountain Time (Alberta) time zone and that there is no preference available in NIM to correct it. It would be very helpful if NIM could fully support the Windows (UTC-06:00) Mountain Time (Alberta) time zone so that Scheduler tasks run at their configured local times without requiring manual time offsets. This affects organizations in Alberta using the new year-round UTC-06:00 time zone and could cause scheduled synchronization, import, export, retention, and other automated jobs to run at unintended times.

Provide the ability to create a duplicate of an item (input text, static, text, grid, etc.) that is already on a form. This would speed up form development when a form needs to have multiple items with similar styling (labels, colors, spacing, etc.)

Provide the ability to manage group membership using the Skyward Qmlativ connector.

Jobs send great emails when the job completes successfully. It would be great if some notification was able to be sent when a job failed as I generally have to check through my emails to count the jobs that ran to find one of them failed to process.

When renaming or deleting filters and mappings there is no warning if they are in use by downstream objects. Having an indicator that the object is in use and/or a warning with what objects depend on an item before deleting or renaming would be great. I have deleted a production filter several times after cleaning up a test filter I had created and had no indication I was creating a problem until the schedule job failed to run.

It would be helpful to enhance the Exchange Online connector functions to include all of the CASMailbox parameters as well as adding Get-MobileDevice and Remove-MobileDevice. Our use case would be in an emergency termination where we want to disable all protocol access without disabling the mailbox and remove any connected mobile devices to the mailbox.

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