Organizations

Every resource in Norcube (a namespace in LangSync, a data source in Backup, a watcher in DomainRadar) belongs to an organization. Permissions, billing, and limits are all scoped to the organization, not the user.

Your default organization

When you sign up, Norcube creates an organization for you automatically. It's named after you and you're the only member. For solo users, this is all you need – everything happens inside this org.

Why you might want more than one

• Separate clients. Agencies running Norcube for multiple clients create one org per client. Billing, data, and access are isolated.
• Separate environments. Some teams run a "Norcube – staging" org alongside their "Norcube – production" org for safer experimentation.
• Separate cost centres. Different teams inside one company can have separate orgs so usage and bills don't co-mingle.

URL pattern

Every authenticated URL in the dashboard is prefixed with your organization's slug:

app.norcube.com/<organization-slug>/langsync/namespaces
app.norcube.com/<organization-slug>/backup/datasources

The slug is a URL-safe identifier (lowercase, hyphens). It's set at org creation and stable after.

Switch organization

1. Open the organization switcher in the top-left of the dashboard sidebar.
2. Pick another org from the list.

The URL updates to use the new slug and the page reloads with that org's data. Your auth token is re-minted for the new org behind the scenes.

Create another organization

1. Click + New organization at the bottom of the switcher.
2. Pick a name and a slug.
3. Submit. You're a member of the new org immediately, and the dashboard switches into it.

The new org has its own free-tier allowance, its own billing setup, and no resources until you create them.

Roles and members

Today, every member of an organization has the same access (effectively admin). Fine-grained roles (admin / member / read-only) are on the roadmap.

Inviting other members is in the dashboard's Settings → Members.

Delete an organization

Only sole-member organizations can be deleted via self-service. The flow:

1. Open Settings → Danger zone in the org.
2. Click Delete organization and confirm by typing the slug.

What happens:

• Open billing usage is finalised (a final invoice may be issued).
• Each product's data is cascade-deleted – LangSync namespaces, Backup data sources and jobs, DomainRadar checks and watchers.
• The Stripe customer record is anonymised but retained for 10 years (Czech tax law).
• The org's slug is freed up after a brief delay.

Multi-member org deletion is a manual support request today. Contact us via the dashboard.

Behaviour and edge cases

• One organization is always your default. When you log in without specifying an org, you land in the most recently used one.
• Cross-org data isolation is enforced at the API layer. A token scoped to org A can't read org B's data, even if you're a member of both.
• Slugs are not reused immediately. A deleted org's slug is parked for a short window before becoming available again.

Related

• Tokens – org-scoped token minting.
• Account deletion.