Nimriz

Organizations and workspaces

Understand org roles, workspace roles, billing scope, and how switching works under multi-workspace governance.

Organizations and workspaces

Use this guide when you want to understand how Nimriz organizes teams, billing, and day-to-day workspace operations.

Before you start

  • you should already have access to at least one Nimriz workspace
  • some org-wide roles are available only on supported plans or as features roll out gradually
  • workspace-owned actions such as links, domains, API keys, and webhooks still depend on the active workspace

What to expect

Nimriz can place one organization above one or more workspaces.

  • the organization is the top-level governance and billing layer
  • a workspace is where operational work happens: links, domains, teammates, API keys, and settings
  • your dashboard still needs an active workspace, even when your access comes from the organization layer

In the dashboard, expect settings to be split into three scopes:

  • Organization: org identity, members, invites, workspaces, and org billing
  • Workspace: workspace details, domains, and workspace team management
  • Personal: profile, appearance, and personal security settings

Org roles and workspace roles

Nimriz keeps org roles separate from workspace roles.

Common org roles:

  • org_member: basic organization membership without cross-workspace admin powers
  • org_admin: can administer child workspaces that belong to the org
  • org_owner: full org control, including delegated governance and billing ownership
  • org_billing_admin: billing-focused access without general workspace mutation powers

Workspace roles still control day-to-day collaboration inside a workspace:

  • owner
  • admin
  • member
  • viewer

What stays workspace-scoped

Even when an org exists above your workspaces, these flows still behave as workspace actions:

  • link creation and editing
  • domain management
  • workspace API keys
  • callback secrets
  • workspace webhooks
  • most dashboard actions tied to the current workspace

That is why switching to the correct active workspace still matters.

Org invites versus workspace invites

Nimriz treats these as different flows:

  • an org invite adds you to the organization layer
  • a workspace invite adds you to a specific workspace

If the workspace belongs to an organization, accepting the workspace invite can also create or reuse your org membership automatically.

Workspace switching under an organization

If you belong to more than one organization or workspace, use the account menu in the dashboard shell.

  • switch the organization first when you need to move to a different org context
  • switch the workspace when you need a different child workspace inside the current org

If your org role allows cross-workspace administration, Nimriz may let you enter a child workspace without a normal workspace membership row. The workspace is still explicit and still becomes your active workspace for dashboard actions.

Billing and governance expectations

The organization layer is where Nimriz can centralize:

  • billing
  • workspace-count governance
  • higher-level admin flows

Operational work remains scoped to the workspace so existing link, domain, webhook, analytics, and API-key behavior stays stable.

If you have a billing-focused org role, the billing page in dashboard settings is org-scoped. That page does not automatically grant general workspace mutation powers.

Common mistakes

  • assuming an org role automatically changes the active workspace
  • treating org invites and workspace invites as the same thing
  • expecting billing access to unlock general workspace mutation powers

Troubleshooting

I can access the org, but the dashboard shows the wrong data

  • check the active workspace first
  • switch into the workspace that owns the links or domains you expect
  • retry the action after switching

I accepted an invite, but I still do not see the expected workspace

  • confirm whether the invite was org-only, workspace-only, or both
  • if you already belonged to the org, you may still need to switch into the target workspace manually
  • if the workspace should be available but is missing, ask an admin to confirm the workspace membership actually exists

I can manage billing but not links or domains

  • that is usually expected for org_billing_admin
  • billing access does not automatically grant general workspace mutation powers

When to contact support

Contact support if:

  • your org role and workspace role combination behaves differently from what your admin expected
  • a workspace invite should have created org access, but it did not
  • you can see the org but can never reach the child workspace you were told to manage

Include:

  • the organization name
  • the workspace name
  • the approximate time of the problem
  • the visible error or screenshot

Related guides