Help index · Platform

Platform notes (landlord)

What the landlord controls versus what a tenant admin does in Octone. Tenants do not use the Telnyx portal for day-to-day setup.

Tenant admins should stay inside Octone: buy numbers, IVR, users, Yealink, SMS. They should not need a carrier login.

Landlord checklist

  1. Create the company and copy the owner temp password — Landlord → Tenants.
  2. Leave feature switches on unless you want to hide a module.
  3. Tell the owner to sign in at /login/{slug}, change the temp password, then Company setup and buy a number.

What the platform must already have

These are not tenant screens. If voice, SMS, or desk-phone outbound fails for every tenant, fix them on the platform (env / carrier app), not in a company admin page:

  • Voice webhook for inbound Call Control
  • Messaging profile + webhook for SMS (attached automatically on number buy when configured)
  • Outbound voice profile so transfers, Yealink outbound, and softphone PSTN can dial
  • API credentials used by number buy, SIP provision, and SMS send
  • Optional TELNYX_PUBLIC_KEY — when set, inbound voice and messaging webhooks verify signatures (skipped if absent)
  • Optional RESEND_API_KEY + EMAIL_FROM — invite and password-reset email
  • Optional OPENAI_API_KEY or XAI_API_KEY — richer call summaries; otherwise a template from keywords/cards

Tenants never enter those values in Octone. Public health: /status (no secrets).

Feature switches vs “it’s broken”

If one company is missing a tile, check Feature switches for that tenant. If every company fails to buy numbers or provision phones, that is platform configuration — not a missing Admin menu.

← Help index

Platform notes (landlord) · Help · Octone