---
name: navan-install-auth
description: >-
  Establish a Navan integration access contract without guessing endpoints, grants, or scopes. Use when onboarding a Booking API, Expense API, SFTP, SCIM, SSO, or direct integration. Trigger with "set up Navan access", "authenticate Navan", or "review Navan credentials".
allowed-tools: Read,Glob,Grep,Write,Edit
argument-hint: "<tenant> <integration-surface> <environment>"
version: 1.9.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags: [ saas, navan, access ]
model: inherit
effort: high
compatibility: "Designed for Claude Code; live or external Navan actions require network access and explicit approval"
title: navan-install-auth
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/navan-install-auth
last_updated: 2026-10-07T06:06:28.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/official-docs.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/navan-install-auth/references/official-docs.md).
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/navan-install-auth`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/navan-install-auth`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/navan-install-auth) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/navan-install-auth`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/navan-install-auth --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/navan-install-auth --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Navan Integration Access Intake

## Overview

Establish a Navan integration access contract without guessing endpoints, grants, or scopes. 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 confirms Booking API, Expense API, SFTP, direct integrations, SCIM, SAML, and OpenID Connect surfaces. Exact hosts, credentials, scopes, schemas, and enablement are tenant- and contract-specific; copy them from the current in-account source.

## Authentication

Record the credential type, issuer, audience or destination, scopes or permissions, expiry, rotation owner, and storage location from the tenant contract. Never infer OAuth client credentials or reuse interactive session cookies.

## Instructions

1. Choose one integration surface and its business owner.
2. Capture the current tenant documentation URL, revision date, and access prerequisites.
3. Request least-privilege non-production credentials through the approved secret channel.
4. Create a redacted connection profile with no credential values.
5. Plan one read-only or metadata-only validation allowed by the contract.
6. Record rotation, revocation, escalation, and production-promotion gates.

## 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

Require the Navan admin and data owner before credential issuance, scope expansion, production access, SSO/SCIM changes, or any traveler-data read.

## Error Handling

- A public product page is not an endpoint contract.
- A login redirect is not proof that an API route exists.
- Missing scope or tenant enablement must fail closed and go to the Navan administrator.

## Output

Return an access matrix, evidence links, credential owner, allowed environments, read-only validation, rotation plan, and unresolved tenant questions. Identify assumptions, owners, expirations, and evidence gaps explicitly.

## Examples

- Prepare Expense API access without placing a secret in the repository.
- Document an Okta SCIM handoff while leaving provisioning disabled.

## Validation

Verify the evidence date, tenant, credential provenance, least privilege, secret storage, revocation owner, and absence of live values in artifacts. Record expected and observed results, including fail-closed behavior.

## Resources

- [Current first-party evidence map](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/navan-install-auth/references/official-docs.md) — recheck dated sources and the selected tenant's in-account contract before relying on mutable endpoints, fields, entitlements, limits, or delivery behavior.
- Record tenant observations as environment-specific evidence, never universal Navan guarantees.
