Skip to main content

​
Settings → General

Open Settings → General for the workspace-level controls that don’t belong to any one channel: the organization name, the IANA timezone and display locale, your plan tier, the branded short-link host, the monthly budget cap, and the danger zone where an organization is deleted. First-touch setup usually means this page plus three siblings — use this guide to know which control lives where.

​
Where the General page sits

The Settings → sidebar groups org-level pages. General is deliberately thin: controls that affect every surface get a card here; controls with their own canonical console get a cross-link card that routes you there instead of a second, drifted editor. The same “managed elsewhere” pattern covers senders and email domains (Audience → Senders) and data retention (Settings → Compliance). If you expect a control and find a pointer card instead, follow the pointer — the card exists so muscle memory from older consoles still lands on the canonical editor. At the top of the page, an account status card shows any active restriction on the organization — the reason, the remediation steps, and the appeal channel — so a restricted workspace surfaces why before you touch anything else.

​
Organization identity

The first card carries:
  • Name — the workspace label (2–100 characters), shown across the dashboard shell.
  • Slug — read-only; the API/identifier form of the name.
  • Tenant ID — read-only, with a copy button; the value you paste into API provisioning and support conversations.
Renaming the workspace is also an activation signal in product analytics: the event records that the name changed, never the literal name, to keep analytics free of PII. Treat the rename as live everywhere the moment the save lands.

​
Regional settings: timezone, locale, date format

The timezone combobox lists the full IANA set (roughly 400 entries) as a searchable picker. This one value drives anything that renders or evaluates “a local time” for your workspace:
  • Quiet-hours evaluation — the per-channel gate from Quiet hours converts send attempts into recipient-local or org-local time before deciding whether the window allows the send. The org timezone is the fallback for sends where the recipient timezone can’t be resolved.
  • Scheduled batches and statements — recurring schedules and statement-period boundaries resolve on the org timezone.
  • CSV import timestamps — imports that don’t carry an explicit offset parse against the org timezone.
Pick the timezone your operations team actually works in, not the one your contact list leans toward; per-recipient timezone resolution takes over when contact data carries it. The locale and date format selects on the same card govern dashboard rendering (number/date presentation), not send-time behavior.
A timezone change applies to future evaluations only. A quiet-hour window or scheduled batch already computed under the old zone does not re-run. Plan the change before a campaign launches, not mid-flight.

​
Plan and account info

The organization record returned by GET /settings/general carries your current plan tier as a read-only value. The page surfaces it alongside the identity data so you can read “what tier is this workspace on” without leaving settings. Upgrading or changing tiers runs through the billing console — contact sales or use the billing surface from the sidebar; do not try to mutate the plan field through the API (reads only). Monthly spend control lives on this page too: the monthly budget card sets the ceiling (in cents) that percent-of-budget spend alerts divide against. Without a value here, those alerts have no denominator and never fire — set one even if it’s approximate. Out of the box, tracked short links in outbound SMS are minted on the platform host (https://api.orbit.devotel.io/l/<code>). The branded short-link domain card lets you point them at a host you own — https://go.acme.li/l/<code> — so recipients see your brand in the SMS body. To go live:
  1. Point the host’s DNS at Orbit’s redirector (the short links guide covers the redirector target).
  2. Enter the bare host here — https://go.acme.li, no path, no trailing slash.
  3. Save. Invalid values (a path, a non-HTTPS scheme) are rejected client-side the same way the server validation rejects them, so a bad host never reaches the link-minter.
Reset to default clears the override (with a confirmation step) and returns future minted links to the platform host. Links already minted keep working on whichever host they were minted on; the reset changes only future minting.

​
Danger zone: deleting the organization

Owner and admin roles see the danger zone at the bottom of the page. It holds two irreversible flows:
  • Transfer ownership — there is no self-serve transfer; the dialog gives you the Devotel support address to contact. (Prevents an accidental ownership hand-off through the same surface that deletes.)
  • Delete organization — a two-step, owner-gated handshake. Consuming it removes members, numbers, contacts, messages, and call history, and signs you out.
Deletion runs as:
  1. POST /organizations/{id}/reauth-challenge mints a short-lived (5-minute, single-use) token proving you were just active on the account.
  2. DELETE /organizations/{id} consumes that token in an X-Reauth-Challenge header with a confirmation body.
The confirm dialog requires typing the organization name verbatim and then returns 202 for an asynchronous cascade. Before you run it, release or port out anything you’d want back — phone numbers and sender registrations attached to the workspace, and any outstanding quota you still owe against.
Deletion is irreversible. There is no undo endpoint and no soft-delete window you can appeal through support. If the goal is to stop spend or pause traffic, use the billing/spend controls instead.

​
Headless setup via the API

Everything editable on this page is one JSON merge into PUT /api/v1/settings/general; read back with GET.
The server does a shallow top-level merge on the settings blob, so sending only short_link_domain leaves sibling keys (email settings, quiet hours, escalation) untouched. Omit fields you don’t want to change.
For the deletion handshake, mint the challenge then consume it:

​
Gotchas

  • Rename is an activation signal — the rename flows through analytics as a boolean “name changed” marker; the literal new name never leaves the page.
  • Timezone applies forward — already-computed quiet-hour windows and schedules don’t re-evaluate; change it before a campaign, not mid-send.
  • Plan is read-only — the API returns it for display; tier changes run through billing, not this endpoint.
  • Delete is final — members, numbers, contacts, messages, and call history all go, and there is no recovery path.
  • Monthly budget gates spend alerts — without the cap set, percent-of-budget alerts have no denominator and silently never fire.

​
See also