← Help home

What Tapestry does for partners

Last reviewed: 2026-04-27 · Owner: Product & Engineering

Goal

Understand what you configure inside Tapestry admin versus what stays in your identity stack, so you can integrate without mixing responsibilities (PROP-005 / EXP-002).

Prerequisites

  • A tenant context (synthetic example: tenant_alpha) and an assigned admin role per SPEC-001.
  • Access to your IdP operator for realm and client work—Tapestry does not replace those runbooks.

Steps

  1. Read the partner registry topic to see how partner_key and routing relate to launch.
  2. Review federation at the Tapestry boundary—callbacks and trust are negotiated with your IdP team.
  3. Use Finance Sync and export topics only with finance-approved roles (ADR-037).

Verify

  • You can name the three planes: tenant scope, partner routing, and federation handoff.
  • You know who to contact for IdP-side changes vs Tapestry admin changes.

If it fails

If terminology still feels opaque, open the troubleshooting topic and capture symptoms (without pasting secrets or live tenant identifiers).

Further reading