Skip to content
RouteSeam

Organizations

RouteSeam is organized around organizations, not individual user accounts. An organization is the workspace that owns everything you build: domains, routes, API keys, and the subscription. Understanding this model matters most when you work with clients or teams.

Every user gets an organization

Section titled “Every user gets an organization”

When you sign up, RouteSeam automatically creates an organization for you — named after you, like “Ose’s Workspace”. There is no separate “create a workspace” step: your first domain can be added seconds after signup.

The hierarchy is:

User
 └─ Organization
     ├─ Domains (and their routes)
     ├─ Members
     ├─ API keys
     └─ Subscription (plan and billing)

Billing belongs to the organization

Section titled “Billing belongs to the organization”

Everything billable belongs to the organization, not to a user. The plan (Free, Starter, Pro, Business), the Stripe subscription, and the quotas — domain count, monthly redirect volume, analytics retention — all attach to the organization. This means:

  • When you upgrade, every member of the organization benefits from the higher limits.
  • Usage from every domain in the organization counts against the organization’s quota.
  • If the organization runs into billing trouble, the consequences apply to the organization as a whole — though existing redirects keep serving regardless. See plans and billing for the details.

Multiple organizations

Section titled “Multiple organizations”

A user can belong to many organizations. This is the agency pattern: you have your own workspace, plus a membership in each client’s organization, and you switch between them with the org switcher in the navigation.

Everything in the dashboard — the domains list, analytics, settings — is scoped to the organization you currently have selected. There is no cross-organization view: each organization’s domains, quota usage, and billing are fully separate.

Roles

Section titled “Roles”

Membership in an organization has a role:

  • Owner — full control, including billing and organization settings. Every organization has an owner; the user who created it starts as owner.
  • Admin — can manage domains, routes, and members.
  • Member — can view and work with the organization’s domains.

Role checks apply to every dashboard and API action within the current organization.

What this means in practice

Section titled “What this means in practice”
  • Solo founder: you have exactly one organization and never think about it. Fine.
  • Agency: create or join one organization per client. Each client’s domains, plan, and billing stay cleanly separated, and you flip between them with the org switcher.
  • Team: invite colleagues into your organization with the role they need rather than sharing a login.
Section titled “Related pages”