Navan Contract Upgrade Control

Overview

Upgrade a Navan API, file, identity, or direct-integration contract without silent data loss. 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

Treat the tenant documentation, delivered schema, and enabled feature set as versioned evidence even when no public semantic version exists. Separate additive drift from breaking field, identity, lifecycle, or delivery changes.

Authentication

Reconfirm scopes, host, credential format, rotation requirements, and environment separation; do not carry forward obsolete credentials merely because old calls still succeed.