Wizard-based onboarding

Every connector goes through the same 5-step wizard. ~5 minutes per target, no professional services required.

Step 1 — Type

Pick from the catalog:

• A specific vendor (Salesforce, Entra, ServiceNow, …) if you know exactly what you're connecting to
• SCIM 2.0 if your vendor speaks SCIM but isn't in the catalog yet
• LDAP for any directory
• REST (generic) for internal/custom APIs

The wizard immediately scopes the next steps to the chosen type — you won't see fields that don't apply.

Step 2 — Connection

Paste the endpoint URL and credentials. The exact fields depend on type:

• SCIM 2.0: base URL + bearer token (or OAuth2 client creds)
• LDAP: host, port, base DN, bind DN, bind password
• REST: base URL + auth method dropdown → fields per method

Test connection runs a live probe. For SCIM that's GET /ServiceProviderConfig with a fallback to GET /Users?count=1. For LDAP it's an anonymous bind followed by a 1-result paged search. Failures show the actual HTTP response or LDAP result code — no generic "couldn't connect" handwaving.

Step 3 — Discovery

The wizard reads a sample of users + groups + roles. For SCIM that's the schema endpoints. For LDAP it's the schema attributes of the configured object classes. For generic REST it samples one record and infers field types.

You see a table of discovered fields with sample values. Spot-check that the right things showed up.

Step 4 — Field mapping

Heuristic auto-mapping pre-fills the IGA-side schema:

Heuristic	Example
Exact-name match	email → email, displayName → display_name
Common synonym	mail → email, cn → display_name, sAMAccountName → username
Type-shape match	first ISO date field → hire_date
Vendor template	Entra userPrincipalName → email, AD userAccountControl → is_disabled

For SCIM 2.0, the enterprise:User extension (RFC 7643 §4.3) is mapped automatically: manager, department, employeeNumber, etc.

You can override any mapping — type a different IGA field, transform with a Python expression, or mark a field as ignored. Sector packs (installed at tenant bootstrap) pre-configure the mappings most relevant to your industry.

Step 5 — First sync

Click Run first sync. The wizard streams progress in real time — identities read, accounts discovered, entitlements mapped, grants recorded.

When sync completes, the dashboard ticks the funnel from bootstrapped → connected.

What happens next

The connector is now active. Subsequent runs are incremental — only changes since the last sync are processed.

If you want governance to kick in immediately, head to Role mining to see what patterns RapidValue found in your data.

Re-running discovery

Field shape changed at the source? Click Re-discover on the connector's settings page. The wizard re-samples and shows a diff: new fields highlighted, removed fields flagged for review, type changes called out. Accept the changes or override per field.

Multi-environment

Most customers have prod + staging variants of the same target. Add the second one as a separate connector instance. Mappings can be copied from the first instance during the wizard — no need to redo the work.