Browse documentation

Organization Setup

Configure and manage your enterprise organization in nRouter. Set up workspace resources, team member access, role permissions, budgets, and billing limits.

Your nRouter organization is the top-level tenancy boundary that owns all workspace resources: teams, virtual API keys, credit balances, guardrails, budget limits, and audit logs. Everything provisioned within nRouter belongs to your organization, with strict tenant isolation enforced at the API gateway layer.

Org-scoped dashboard at /[organization] — sidebar, top metrics, and the org name shown in the header

Organization Provisioning

  1. Registration: Create your workspace at /signup.
  2. Prepaid Funding: Fund Pay as you go credits via Stripe Checkout (0% platform fee).
  3. Verification: Verify email in Getting Started (/[organization]/getting-started) to mint your starter Default key (sk-nrouter-*).
  4. Invitations: Invite team members under People → Members (/[organization]/people/members).

Organization Settings

Access organization settings via the pinned-bottom account menu in the sidebar (SidebarAccountMenu), which opens AccountSettingsModal presenting Org Settings directly above Profile Settings (there is no topbar profile menu).

Settings · General tab — org name, slug, logo upload, and timezone at /[organization]/settings

General Information

SettingDescription
Organization NameDisplay name in headers, invoices, and emails
Organization SlugUnique URL identifier across dashboard routes (/[organization]/*)
Organization LogoBrand image in dashboard header

Data Policies

PolicyDescription
Data RetentionLog and metrics storage retention window
Data ProcessingOpt-in telemetry controls
RegionGeographic data processing preference

Resource Architecture

  • Shared Pool: Organization credits fund requests across all teams and virtual keys at list price with 0% fees.
  • Hierarchical Governance: Virtual keys and budgets cascade across organization, team, and key levels.
  • Multi-Tenant Isolation: The gateway resolves tenancy from authenticated keys and never echoes tenant IDs over the wire; log x-nr-request-id to correlate requests with dashboard logs (/[organization]/logs).
  • Single Tenancy: Accounts bind strictly to one organization without in-session workspace switching.
  • Danger Zone (/[organization]/settings/danger-zone): Deleting an organization permanently purges all assets and requires typing the organization slug (Owner only).

Frequently asked questions

Who can change organization settings?

Owners and Org Admins edit general settings and data policies, while slug changes, billing, and workspace deletion are restricted to Owners.

Where do I find my organization ID, and where does it show up?

Your organization ID appears on Settings; correlate API calls by logging x-nr-request-id and inspecting Observability or Analytics.

If I rename my organization or change the slug, do I need to update my code?

No, renaming only updates dashboard URLs and display labels without affecting API keys or integration endpoints.

What happens when I delete my organization?

Deletion permanently purges all keys, teams, credits, and logs after confirmation in the Settings danger zone.

Next Steps

Was this page helpful?