Feedback Ideas
Submit IdeaYour Voice Matters: Share Your Thoughts and Help Us Enhance Your Experience!
Add ability to set "sponsors" to Azure/Entra connector
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.
Gary M2
Enable Google api write
Should have the ability to write to a Google sheet like it does with creating a csv export
Joel M3
Exclude characters option for random password generator
Provide the ability to define characters that should not be include in the random password generator
Mike Sheldon0
Itemized list of changes from Flow screen
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.
Nick W1
Support the new UTC-06:00 Mountain Time (Alberta) time zone in NIM Scheduler
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.
Anton S2
Ability to duplicate form items
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.)
Steve M1
Schedule Failure Notices
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.
Jeffrey R2
Warnings when objects have dependencies
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.
Jeffrey R1
Junior/Light Admin Access
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.
fe10
Temporary Job Threshold Increase
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.
Josh M3
Admin Dashboard
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
Mike Sheldon0
Attached Files to Mail Templates
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.
Mike Sheldon0
Role organization
It would be nice to be able to structure & reorder roles either through folders, or child roles akin to filters.
Truman C0
Only send evaluation report if there are changes to be made
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.
Steve M1
Data Encryption
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
Mike Sheldon1