Customer management preview
Section ID: Guide/jde3abb4i4#overview
Status: Upcoming — not yet available.
The customer-management API and platform console are not available. Start with the workspace and project guidance and confirm your operator’s supported arrangement. This preview distinguishes hosting companies as customers from delegated work in a workspace they own.
Your billing system remains responsible for collecting payments from your customers.
Hosted and client-owned relationships
Section ID: Guide/jde3abb4i4#customer-relationships
Status: Upcoming — not yet available.
The proposed hosted relationship gives each company a customer identity within a project, without creating a separate workspace or subscription. A client-owned workspace remains independent and requires separately authorized delegated access. Paying for it would not itself grant access to its content.
Customer and environment isolation
Section ID: Guide/jde3abb4i4#customer-isolation
Status: Upcoming — not yet available.
The planned scope binds each authenticated company to its own customer identity and separates test/live data. An omitted customer, where permitted, would select unassigned records rather than every customer. Combined views need separate authorization; validate isolation before enabling a deployment.
Delegated access
Section ID: Guide/jde3abb4i4#delegated-workspace-grants
Status: Upcoming — not yet available.
The proposed workspace administrator chooses permitted projects, environments, customers, actions and expiry. A grant cannot enlarge the integration’s own key permissions. Revocation must stop new grant-dependent work while separately tracking actions already sent to external services; an invitation is not permanent authority.
Operations summaries
Section ID: Guide/jde3abb4i4#managed-console-boundary
Status: Upcoming — not yet available.
The planned platform console exposes permitted usage and health summaries, not private employee conversations or transcripts through drill-down, exports or embedded sessions. Access to a client’s own console still requires that client’s membership and permissions.
Usage and payment attribution
Section ID: Guide/jde3abb4i4#usage-and-payment-attribution
Status: Upcoming — not yet available.
The proposed workflow attributes usage under the agreement effective when it occurred, including late-arriving usage. Customer identities and test/live modes have no separate entity fee in this design; metered usage and accepted terms remain distinct.
Your billing system collects customer payments. See commercial agreements and invoicing for your agreement with Travila.
Relationship recovery and offboarding
Section ID: Guide/jde3abb4i4#relationship-recovery
Status: Upcoming — not yet available.
The planned recovery path reconciles the original creation request before creating another customer. Offboarding one company would block its new work and account for cleanup, retained records and uncertain external effects while other customers continue. Delayed updates must not reactivate it; deletion does not close a shared payment account.
Retain the usage and payment references required for outstanding charges; see billing and spend.
Document ID: Guide/jde3abb4i4