Skip to main content
A Workspace (organization) is the top-level container for all NearNode resources — nodes, batches, templates, analytics, and team members. Every resource belongs to exactly one workspace.

​
Multi-Workspace Architecture

Users can belong to multiple workspaces. Each workspace has its own:
  • Node inventory and routing rules
  • Batches and templates
  • Analytics data and retention
  • API keys and webhook configurations
  • Billing and plan tier
  • Custom domains
  • Team members and role assignments
┌─ User: james@vidiai.ch ─────────────────────┐
│                                              │
│  ┌─ Workspace: VidiAI ──────────────────┐    │
│  │  Role: Owner                         │    │
│  │  Nodes: 342  │  Batches: 12          │    │
│  │  Plan: Enterprise                    │    │
│  └──────────────────────────────────────┘    │
│                                              │
│  ┌─ Workspace: Client Project ──────────┐    │
│  │  Role: Admin                         │    │
│  │  Nodes: 89   │  Batches: 3           │    │
│  │  Plan: Pro                           │    │
│  └──────────────────────────────────────┘    │
│                                              │
└──────────────────────────────────────────────┘
Ops Tip: Switch between workspaces using the workspace selector in the top-left of the Dashboard sidebar.

​
Creating a Workspace

New workspaces start on the Developer (free) plan. The creating user is automatically assigned the Owner role. 
curl -X POST https://nearnode.io/api/v1/organizations \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Acme Corp",
    "slug": "acme-corp"
  }'

​
Workspace Settings

SettingDescriptionWho Can Change
NameDisplay name shown in the sidebarOwner
SlugURL-safe identifier (immutable after creation)—
LogoWorkspace avatarOwner
PlanBilling tier (Developer / Pro / Enterprise)Owner
Default timezoneUsed for time-based routing rulesOwner, Admin

​
Data Isolation

Workspace data is fully isolated at the database level via Row Level Security (RLS). There is no cross-workspace data access — even at the API level, a key scoped to Workspace A cannot read Workspace B’s nodes.
Deleting a workspace permanently destroys all associated nodes, batches, templates, analytics data, and API keys. This action cannot be undone.

​
Inviting Team Members

1

Open Members

Navigate to Settings → Members in the workspace.
2

Send Invite

Enter the email address and select a role. The invitee receives an email with a join link.
3

Accept

The invitee clicks the link, creates an account (if needed), and is added to the workspace with the assigned role.
Pending invitations expire after 7 days. The invite can be resent from the Members page.

​
Transferring Ownership

Only the current Owner can transfer ownership to another workspace member:
  1. Navigate to Settings → Members
  2. Click the target member’s role badge
  3. Select Transfer Ownership
  4. Confirm with your password
The previous owner is demoted to Admin. A workspace always has exactly one Owner.

​
Plan Limits

FeatureDeveloperProEnterprise
Nodes251,000Unlimited
Batches3UnlimitedUnlimited
Templates110Unlimited
Team members210Unlimited
Custom domains—1Unlimited
Analytics retention30 days1 yearUnlimited
API rate limit100 req/min500 req/minCustom
Need to evaluate Enterprise features? Contact sales@nearnode.io for a 14-day trial on any workspace.