navan-install-auth
/navan-install-auth
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".
- Author
- jeremylongshore ↗
- Repository
- tons-of-skills-marketplace ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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".
Triggers from the description
Arguments
/navan-install-auth <tenant> <integration-surface> <environment>
Original author 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".
How it works
- Overview
- Prerequisites
- Current Contract
- Authentication
- Instructions
- Tool Discipline
- Approval Boundaries
- Error Handling
- Output
- Examples
SKILL.md preview
--- 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" --- # 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](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.
Files in this package (2)
- SKILL.md 4 KB
- references/official-docs.md 1 KB
Versions
The database has no other skills named navan-install-auth.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 7852cece8766 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100navan-sdk-patterns
Design an application-owned Navan adapter pinned to the tenant's actual integration contract. Use when wrapping Booking API, Expense API, SFTP, or direct integration behavior. Trigger with "build a Navan client", "wrap Navan API", or "type Navan responses". - 100navan-common-errors
Triage Navan integration failures without exposing travel or payment data or applying blind retries. Use when a contracted API, SFTP, SCIM, or direct integration fails. Trigger with "Navan error", "Navan sync failed", or "debug Navan integration". - 100saas-sso-scim-enterprise-auth
Use when implementing tenant-scoped SAML or OIDC SSO, SCIM provisioning, custom domains, IP allowlists, or enterprise auth migration. - 100ssojet
Use when adding, fixing, or improving how an app signs users in with SSO or OIDC, protects a backend with machine-to-machine tokens, or manages teams, tenants, roles, invitations, and directory sync (SCIM) — or when using or configuring any SSOJet feature or API. Covers Next.js,… - 100cursor-sso-integration
Configure SSO and enterprise authentication in Cursor. Triggers on "cursor sso", "cursor saml", "cursor oauth", "enterprise cursor auth", "cursor okta". Use when working with cursor sso integration functionality. Trigger with phrases like "cursor sso integration", "cursor integration", "cursor". - 100shopify-setup
Set up Shopify CLI auth and Admin API access for a store. Install CLI, authenticate, create custom app, store access token, verify. Use whenever the user wants to connect to a Shopify store, set up Shopify API access, install Shopify CLI, or troubleshoot Shopify auth / Admin API token issues.