NIM concepts

NIM fundamentals

Learn the objects that turn trusted identity data into repeatable, auditable identity changes.

At a glance

NIM follows a clear automation path: connect a system, collect and relate its data, select the records that need action, define the intended target change, and run that work in a job. Start with one source, one target, and one limited outcome. Verify the result before you schedule it or apply the same pattern to more systems.

The core automation path

Concept	What it does	Use it when you need to
System	Connects an external source, target, or NIM-managed data source.	Read identity data or apply a change in another system.
Collection and Vault	Collect current system data and make it available to NIM processing.	Confirm the automation is working from current, usable data.
Inter-system relation	Matches related records across systems.	Connect an HR person to a directory account or other corresponding record.
Filter	Selects and shapes the records a workflow should evaluate.	Express who needs an account, access change, or notification.
Mapping	Applies a create, update, read, or remove operation to a target system.	Provision or update target-system records from filter output.
Role	Maintains group membership or other target entitlements from identity rules.	Manage ongoing access rather than a one-time direct operation.
Job	Groups mappings and role operations into reusable work.	Run related identity changes together and review one result.
Sync task	Runs jobs manually or on a schedule.	Repeat a validated job at the right frequency.

How the concepts work together

Consider a typical account-provisioning outcome: create an application account for each active employee who does not already have one.

1. Configure the HR source and application target as systems, then collect their data.
2. Create an inter-system relation if NIM must identify existing accounts for the HR employees.
3. Build a filter that returns active employees without a matching application account.
4. Create a mapping that creates the application account and maps the required attributes.
5. Add the mapping to a job, run it manually, and verify the selected account in the target system.
6. Add the validated job to a sync task only when the result and schedule are appropriate for the business process.

This is a workflow: a documented sequence of NIM objects and checks that delivers a defined identity outcome. A workflow can be as small as one account update or grow to include multiple systems, mappings, roles, jobs, and approval steps.

Choose the right object

• Use a system to connect data; use a connector when selecting the component and connection method for that system.
• Use a relation to identify corresponding records; use a filter to decide which records should be evaluated.
• Use a mapping for direct target-record operations; use a role for maintained group membership or entitlement rules.
• Use a job to group work; use a sync task to decide when that work runs.

Verify before automation

Before enabling a schedule, confirm each layer in order: collected data is current, relations match the right records, filter output contains the intended population, the mapping or role produces the expected target change, and the job completes with the expected result. This sequence makes it easier to isolate errors without changing unrelated parts of the workflow.

Continue learning

• How NIM works — see the end-to-end automation flow.
• Build your first workflow — create and verify one limited automation.
• Troubleshoot NIM — diagnose collection, filter, relation, validation, and service issues.