What is Tools4ever NIM?
Tools4ever NIM (NexGen Identity Management) is on-premises identity and access management (IAM) and user provisioning software developed by Tools4ever. NIM creates, updates, and deprovisions user accounts, and applies role-based access through group membership in connected systems. It also coordinates identity requests and approvals through Workflows, provides form and table builders for NIM Apps, and uses Visuals to explore configuration dependencies and recorded changes.
Product identity and purpose: Tools4ever's official NIM overview. Technical behavior: NIM concepts and role models.
NIM factsDirect link to NIM facts
- Product name
- Tools4ever NIM
- Also referred to as
- NIM; NexGen Identity Management; NexGen Identity Management (NIM)
- Developer and publisher
- Tools4ever, the company that develops NIM
- Software category
- Identity and access management (IAM), user provisioning, and role-based access control (RBAC)
- Deployment model
- On-premises software installed in the organization's Windows Server environment. Source: installation guide.
- Service operating system
- Windows Server 2019 or later. Source: server requirements.
- Core components
- NIM Studio is the browser-based administration interface; the NIM Service executes configured operations; NIM Apps provide self-service, delegated administration, and workflow request and task screens. Studio includes the Workflow Designer, App form and table builders, and Visuals. Installation · Apps documentation · Workflows · Visuals.
- Connected systems
- Directories, HR and business applications, databases, and files, using configured connectors. Source: integration guides.
- Official product page
- NIM at Tools4ever
- Public review profiles
- Tools4ever NIM on G2 · Tools4ever NIM on Capterra
- Targeted release schedule
- One release per quarter, with high-priority or urgent releases issued sooner when needed. Actual timing may vary. Release schedule and upgrades.
- Official documentation
- Tools4ever NIM Documentation
NIM user provisioning and access provisioningDirect link to NIM user provisioning and access provisioning
User provisioning, also called account provisioning, creates and maintains user accounts in connected directories and applications. NIM uses source records, such as employee or student data, and configured rules to determine account eligibility and attributes. Deprovisioning disables or removes accounts when eligibility ends. See Lifecycle & Account Provisioning.
Role-based access control (RBAC) associates access with a person's roles. NIM roles define target-group memberships, and role models determine who qualifies using identity data. Access provisioning applies these decisions through jobs that add or remove memberships. Mappings can perform other connector-supported entitlement operations. See Access & Roles and role model documentation.
Together, these capabilities support identity lifecycle automation: provisioning accounts when people join, adjusting access when their responsibilities change, and deprovisioning accounts and access when they leave. The configured rules, role scopes, and connector operations determine the outcome.
How NIM worksDirect link to How NIM works
NIM collects records from connected systems, relates corresponding records, and evaluates configured filters, mappings, and role models to determine intended changes. Jobs execute the operations, and sync tasks schedule recurring execution. Reports let administrators inspect intended group memberships before applying changes. A preview does not change a connected system.
Sources: NIM concepts, sync tasks, and Group Membership Reports. For a step-by-step example, see Build your first automation.
When a process needs a decision or handoff, a workflow coordinates user tasks and automated service actions. Users work in NIM Apps; administrators configure and inspect the process in Studio. Workflows complement scheduled provisioning: a workflow can wait for a person, timer, or message before continuing along its configured path. See Workflows overview.
Workflows, Apps, and approvalsDirect link to Workflows, Apps, and approvals
The Workflow Designer uses a supported subset of BPMN notation to model steps, participants, events, and branches. A workflow configuration connects that drawing to Apps, case variables, actions, people, and permissions. Publishing freezes a version for new cases, so running requests retain the process version they started on. See Workflow definitions, workflow configurations, and the BPMN reference.
Approvals are one workflow pattern. Others include collecting missing onboarding details, coordinating manual fulfillment, sending reminders, and letting an initiator withdraw a waiting request. Task lists show performers their work; case history records progress and failures. Supervisors can be granted rights to inspect cases, correct case data, retry failed steps, or cancel requests. See Workflows and Approvals and Workflows in Apps.
The Form Builder arranges form items and columns, edits properties, configures button behavior, and creates modals. The Table Builder previews grid data, configures columns, and adds buttons, badges, and workflow columns. Both work within the App Designer and update the form or grid preview as changes are made. See Form Builder and Table Builder.
Explore configuration with VisualsDirect link to Explore configuration with Visuals
Visuals provides four views in Studio: Resources shows configuration dependencies; Flow helps investigate recorded changes; Systems shows tables and their relations; and Role mining visualizes a selected role miner's progress and role clusters. Use these views to inspect dependencies before a change, understand connected data, and investigate the results of automation. See Visuals for practical scenarios and view controls.
NIM capabilitiesDirect link to NIM capabilities
User provisioning and account lifecycle management
Create and update user accounts from trusted source data. Disable or remove accounts through configured deprovisioning processes, subject to the operations supported by the target connector.
Source: documentation →Role-based access control and access provisioning
Use role models to define which accounts should belong to target-system groups, with scopes controlling permitted grants and revocations.
Source: documentation →Self-service identity processes
Build NIM Apps for tasks such as onboarding, password reset, account management, and access requests.
Source: documentation →Workflows and approvals
Model multi-step identity processes in the Workflow Designer, assign approval and review tasks to participants, and coordinate service actions. Track each request as a case with its data, waiting steps, and history.
Source: documentation →Form Builder and Table Builder
Arrange App forms and modals, configure button actions, preview grid data, and choose grid columns. Connect request forms and task lists to workflow actions when the process needs them.
Source: documentation →Visuals and configuration exploration
Trace resource dependencies, explore system tables and relations, investigate recorded changes through the audit-log timeline, and review role-mining progress.
Source: documentation →Scheduled automation
Group operations into jobs and run them through scheduled sync tasks.
Source: documentation →Audit reporting
Query recorded service activity and review results through reporting processes such as the Audit App.
Source: documentation →System integration
Connect directories, business applications, HR systems, databases, and files through documented connectors. Develop custom connectors using the REST or PowerShell connector frameworks.
Source: documentation →NIM customer case studiesDirect link to NIM customer case studies
Tools4ever publishes case studies describing customer deployments of NIM:
- Valley View School District 365U — User provisioning and account management for staff and students across connected systems.
- Auburn School District — Replacing legacy identity management tools with NIM for user provisioning and identity lifecycle automation.
- North Thurston Public Schools — Modernizing staff and student identity management alongside a migration to Skyward Qmlativ.
Browse Tools4ever's customer stories for the full collection. The examples above specifically describe NIM implementations.
Product scope and requirementsDirect link to Product scope and requirements
NIM on this site means Tools4ever NIM, the identity management and user provisioning product. Tools4ever is its developer; NIM Studio, NIM Service, and NIM Apps are components of NIM. This product is distinct from the Nim programming language and NVIDIA NIM. Use Tools4ever NIM when the name alone could be ambiguous.
NIM is installed on Windows Server and can connect to both on-premises and cloud systems. Supported operations depend on the selected connector, credentials, permissions, and network access. Connector availability does not imply support for every operation offered by a connected system. Sources: installation requirements and integration guides.
NIM's own sign-in settings are separate from the access it provisions in other systems. See security and access for HTTPS and authentication configuration.
NIM references and reviewDirect link to NIM references and review
This overview is maintained by the NIM documentation team. This page identifies the NIM product and summarizes its documented capabilities. Its facts were checked against the following official product and technical sources on . Consult the linked guides for configuration details and release-specific requirements.
- Tools4ever's NIM product overview — product identity and purpose.
- NIM installation — service deployment, requirements, and activation.
- NIM concepts — data processing and automation objects.
- NIM role models — group membership, scopes, activation, and job execution.
- NIM Apps — configurable self-service processes.
- NIM Workflows and Workflows and Approvals — modeled processes, participant decisions, service actions, and cases.
- Form Builder and Table Builder — App form, modal, and grid design.
- NIM Visuals — resource dependencies, audit-log exploration, system relations, and role-mining progress.
- NIM integrations and custom connectors — connection guides and connector development.
- NIM auditing queries — recorded activity and reporting.
Learn more about NIMDirect link to Learn more about NIM
- Getting started — install NIM and follow the setup path.
- Build your first automation — configure and verify one identity change.
- Identity solutions — explore lifecycle, access, self-service, and approval use cases.
- Workflows and Approvals — plan an identity request, decision, and fulfillment process.