Agent skill · software engineering · jeremylongshore
navan-entity-management
Govern workforce, organization, and access lifecycle changes across Navan and enterprise identity sources. Use when operating HRIS, SCIM, SSO, or manual provisioning. Trigger with "manage Navan users", "Navan SCIM", or "offboard Navan traveler".
Why this skill is useful
Provides specific API commands and SCIM provisioning patterns for managing user entities in Navan that the AI wouldn't reliably generate on its own.
What it needs
Requires navan account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Navan Workforce and Organization Lifecycle Overview Govern workforce, organization, and access lifecycle changes across Navan and enterprise identity sources. This workflow produces an auditable decision or artifact before any live action. Prerequisites Access to the selected tenant's current Navan Help Center and contracted integration documentation. A named business owner and data owner for the travel or expense workflow. A non-production evidence set with secrets and traveler data removed. Current Contract Navan publicly lists HRIS integrations, HR-SFTP, Okta SCIM, SSO, OpenID Connect, SAML, and user-management integrations. Exact attributes, roles, group rules, activation states, and deprovision behavior are tenant-specific. Authentication Provisioning identities are privileged and must be separate from ordinary data-read integrations. Bind one identity source as authority and document manual exceptions. Instructions 1. Inventory authoritative people, employment, organization, and access attributes. 2. Map identifiers and lifecycle states without using email alone as an immutable key. 3. Define joiner, mover, leave, rehire, guest, contractor, and exception behavior. 4. Stage changes and review role, policy, manager, entity, and traveler-impact deltas. 5. Apply only through the enabled integration and record acknowledgements. 6. Reconcile source authority, Navan state, downstream systems, and manual grants. Tool Discipline Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion. Approval Boundaries Privileged role grants, bulk changes, authority-source changes, reactivation, manual exceptions, and destructive deprovisioning require explicit approval. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/navan-entity-management