Team & Settings

Organization Settings

Your organization is the home for everything you build in Routebase — projects, specs, test suites, mock servers, and the people who work on them. This guide covers the organization-wide settings under Settings → General: your organization's identity, usage type, versioning defaults, and the danger zone.

Managing these settings requires the org:manage-settings permission, which Admins and Owners have. For people, roles, and access control, see Members & Invitations, Roles & Permissions, and Team Access.

Organization details

  • Organization Name — shown across the app and on your documentation portals.
  • Description (optional) — a brief description of your organization.

Edit either field and click Save Changes; a save indicator confirms when the change persists, and Reset discards unsaved edits.

The General organization settings page with name, description and logo

Usage type

Choose whether this organization is for Personal use (side projects, learning, and personal APIs) or Business use (team collaboration, professional API management). This affects which plans and features are available:

  • Switching to Business unlocks the Enterprise plan and enables team-oriented features.
  • Switching to Personal hides the Enterprise plan option — if you have an Enterprise subscription, you'll need to change your plan first.

See Billing & Plans.

Upload a logo to be displayed in the sidebar and on your documentation. Click the upload area or drag and drop a PNG, JPG, or GIF image (max. 2MB).

Default versioning strategy

Set a recommended versioning strategy for new API specifications. This is a suggestion, not enforced — each spec can override it.

Field Options
Strategy Type None (no default), URL Path, Header, Query Parameter, or Content Negotiation
Parameter Name The version carrier — e.g. v for URL path, Api-Version for header, version for query parameter
URL Pattern For URL-path versioning: the pattern, e.g. /v{major}
Default Version Behavior Latest version, Specific version, or Require explicit version
Strict Mode Reject requests with invalid versions

Click Save Default to apply, or Clear Default to remove the recommendation. See Versioning for how strategies play out in your specs.

Your organization's data region (US or EU) is chosen once at signup and can't be changed here. See Region Selection.

Danger zone

The two account-ending actions live at the bottom of the General page. Neither destroys anything on the spot: deleting an organization stays reversible for 30 days, and leaving one starts a 30-day clock on your own account.

  • Leave Organization — removes you as a member. You will lose access to all projects, API specifications, test suites, and mock servers of this organization. This option is shown to Admins and Members; as the Owner you won't see it — delete the organization instead if you're winding it down. Leaving has consequences for your personal account too — see After you leave below.
  • Delete Organization — schedules the organization for deletion. Everyone is signed out immediately and the workspace becomes unreachable, but nothing is erased yet: the Owner receives an email titled "…is scheduled for deletion" with a Restore workspace link that works without logging in, and only when the 30 days are up do the projects, API specifications, test suites, and mock servers get removed for good. Memberships are deliberately kept during those 30 days, so restoring brings every member back with their role. You must type the organization's name to confirm. Only the organization Owner can delete it (org:delete permission); for everyone else the button is disabled with a tooltip saying so. Your own user account survives either way, so you can sign in and start fresh later.
The danger zone with leave and delete organization actions

Before you can delete: cancel the subscription

An organization with a live, uncancelled subscription cannot be deleted. The confirmation dialog checks this when it opens and, if a subscription is running, shows a "Cancel your subscription first" notice with a Go to Billing shortcut instead of letting you proceed. Cancel the subscription first — you keep access until the end of the current billing period, and a subscription that is already cancelled but still running does not block the deletion. See Billing & Plans.

Before you confirm, the dialog also tells you how many members will lose access, and — if the organization has ever been invoiced — that invoices and billing records are kept for the statutory retention period while everything else is removed.

After you leave

Ending a membership always sends you a mail and starts a 30-day clock; the clock only bites if that was your last organization. The mechanic is identical whether you left voluntarily, an Admin removed you, or the organization was deleted around you:

  • You get an email confirming that the membership ended. It names the exact date on which your account and personal data would be deleted if you don't join an organization again, and carries a one-time Download my data link so you can take your data with you — see Profile & Preferences. If you are still a member of another workspace, that date never arrives.
  • Joining an organization before the date — or simply signing in again — stops the clock. Nothing is deleted while you hold a membership anywhere.
  • If your email address is on a verified domain of the organization you left, your sign-in is blocked as well: the address belongs to the company, so it can neither keep the account alive nor found a separate workspace under that domain. Collaborators on their own domains — agencies, freelancers, contractors — are never blocked; for them a single sign-in is enough to keep the account. See Custom Domains for what verifying a domain claims.

Tenant isolation

Every organization is fully isolated. Members, invitations, roles, teams, API keys, variables, and audit logs are scoped to a single organization — there's no way for one organization to see another's data, even if they share a name. When you belong to more than one organization, each keeps its own members and settings entirely separate.