Multi-Organization Setup Guide

What You’ll Learn

This guide covers managing multiple organizations in Junis:

Why Multiple Organizations: Use cases and benefits
Creating Additional Organizations: Step-by-step setup
Organization Switching: Seamless context switching
Cross-Organization Features: What’s shared and what’s isolated
Common Scenarios: Agency, enterprise, dev/prod separation
Best Practices: Naming, structure, and organization strategies

Who This Is For: Users who need to manage multiple projects, clients, or environments within Junis.

Why Multiple Organizations?

Common Use Cases

Agency/Consultancy

Scenario: Manage separate workspaces for each clientBenefits:

Complete data isolation per client
Separate billing and feature limits
Client-specific branding and settings
Easy client handoff (transfer ownership)

Example:

acme-corp (client A)
globex-industries (client B)
initech-consulting (your internal workspace)

Enterprise Departments

Scenario: Separate organizations for different departmentsBenefits:

Department-level autonomy
Isolated agent configurations
Department-specific analytics
Compliance and governance per department

Example:

acme-marketing
acme-sales
acme-engineering
acme-data-science

Dev/Staging/Production

Scenario: Separate environments for development lifecycleBenefits:

Test changes safely in dev
Isolated data per environment
Different feature flags per environment
Production safety

Example:

mycompany-dev
mycompany-staging
mycompany-production

Personal + Professional

Scenario: Separate personal projects from workBenefits:

Work-life separation
Different billing accounts
Personal experimentation space
Professional client work

Example:

john-doe-personal
john-doe-freelance
acme-corp (employer)

Single vs Multiple Organizations

Aspect	Single Organization	Multiple Organizations
Data Isolation	All data in one workspace	Complete isolation per organization
Billing	One bill for everything	Separate billing per organization
Team Management	One team roster	Separate teams per organization
Agent Sharing	Agents shared across projects	Agents isolated per organization
Use Case	Small teams, single project	Agencies, enterprises, multi-project

When to Use Multiple Organizations:

Managing multiple clients
Separating dev/staging/prod environments
Different departments with separate budgets
Projects with different compliance requirements
Testing new features in isolation

When NOT to Use Multiple Organizations:

Single project with multiple sub-projects (use agent tagging instead)
Small team working on one product
Just to separate different agent types (use agent naming/folders instead)

Creating Additional Organizations

Prerequisites

Existing Junis account (verified email)
At least one organization already created (from onboarding)
Organization approval pending or approved

Step-by-Step Creation

Access Organization Switcher

Click the organization name in the top-left corner of the dashboard.Or navigate to Settings > Organizations in the sidebar.

Click 'Create New Organization'

In the organization switcher dropdown, click ”+ Create New Organization” at the bottom.

Fill in Organization Details

Required Fields:

Organization Name: Display name (e.g., “Acme Corp - Marketing”)
Slug: URL-friendly identifier (e.g., “acme-marketing”)
- Auto-generated from name
- Can be customized
- Must be unique across all Junis organizations

Optional Fields:

Description: Organization purpose or description
Logo: Upload organization logo (PNG, JPG, max 2MB)
Welcome Suggestions: Custom chat suggestions for this organization

Configure Initial Settings

Organization Type: (Auto-selected: STANDARD)Initial Features:

Max Agents: 10 (default, can be increased)
Max Members: 50 (default)
Max Sessions/Day: 1,000 (default)
RAG Enabled: Yes (default)

Feature limits can be adjusted later by administrators.

Submit for Approval

Click “Create Organization”.What Happens Next:

Organization created with PENDING status
You become the OWNER automatically
Default orchestrator agent created (orchestrator-{slug})
Approval notification sent to Junis administrators

Approval Timeline: 1-2 business days

Wait for Approval

While PENDING:

Organization appears in your organization list
Yellow “Pending Approval” badge displayed
You can view organization settings but cannot use agents

After APPROVAL:

Status changes to ACTIVE
Green “Active” badge displayed
All features unlocked
You can invite team members and create agents

Organization Creation via API

Endpoint: POST /api/organizations Request Body:

{
  "name": "Acme Corp - Marketing",
  "slug": "acme-marketing",
  "description": "Marketing department workspace",
  "logo_url": "https://example.com/logo.png",
  "welcome_suggestions": [
    "Analyze this campaign performance",
    "Generate social media content ideas",
    "Create a content calendar"
  ]
}

Response:

{
  "id": "org-uuid-1234",
  "name": "Acme Corp - Marketing",
  "slug": "acme-marketing",
  "status": "PENDING",
  "org_type": "STANDARD",
  "created_at": "2024-01-10T10:00:00Z",
  "created_by": "user-uuid-5678",
  "features": {
    "max_agents": 10,
    "max_members": 50,
    "max_sessions_per_day": 1000,
    "rag_enabled": true
  }
}

Switching Between Organizations

Using the Organization Switcher

Desktop/Web
Mobile/Tablet
API

Location: Top-left corner of the dashboard (next to Junis logo)Steps:

Click the current organization name (e.g., “Acme Marketing”)
Dropdown shows all your organizations
Click the organization you want to switch to
Page reloads with new organization context

Keyboard Shortcut: Cmd+K (Mac) / Ctrl+K (Windows) → Type organization name → Enter

What Changes When You Switch

UI Changes
API Context
Data Isolation

Visible Changes:

Organization name in header updates
Logo changes (if custom logo set)
Welcome suggestions update
Sidebar navigation shows organization-specific items

Dashboard:

Agents list filtered to current organization
Sessions filtered to current organization
Analytics show current organization data only
Team members list shows current organization roster

Organization Context Persistence

Session Persistence: Your last selected organization is remembered across browser sessions.

How It Works:

Organization choice stored in JWT token
JWT token saved in browser localStorage
On next visit, last organization is auto-selected
You can switch anytime using the organization switcher

Managing Multiple Organizations

Organization List View

Location: Click organization name → “Manage Organizations” What You See:

Your Organizations
Pending Invitations
Create New

List of Organizations You Own or Are a Member Of:

Organization	Status	Role	Members	Agents	Last Active
Acme Marketing	🟢 Active	OWNER	12	25	2 hours ago
Acme Sales	🟢 Active	ADMIN	8	15	1 day ago
Personal Workspace	🟡 Pending	OWNER	1	3	5 days ago
ClientCo Consulting	🔴 Suspended	MEMBER	5	10	3 weeks ago

Actions:

🔄 Switch: Switch to this organization
⚙️ Settings: Edit organization settings (OWNER/ADMIN only)
👥 Members: View/manage team members
🚪 Leave: Leave organization (if not last OWNER)

Multi-Organization Dashboard

Feature: Unified view across all your organizations (coming soon) What It Will Show:

Total agents across all organizations
Combined session count
Activity timeline across organizations
Quick organization switcher
Notifications from all organizations

Cross-Organization Features

What’s Shared Across Organizations

User Account

Shared:

User ID
Email address
Display name
Avatar
Password/authentication

Not Shared:

Role (OWNER in org A ≠ OWNER in org B)
Permissions (org-specific)

Global Platform Access

Shared:

Platform features (MCP, RAG, Payment)
Global LLM models
Junis platform updates
Documentation and support

Not Shared:

Organization-specific feature limits
Organization-specific settings

What’s Isolated Per Organization

Complete Isolation: The following are NEVER shared between organizations:

Data Isolation
Team Isolation
Billing Isolation

Completely Isolated:

Agents (cannot see other org’s agents)
Sessions (cannot access other org’s conversations)
RAG Datastores (separate knowledge bases)
Agent Templates (organization-specific)
File Uploads (separate storage per org)
Usage Analytics (separate metrics)

Global Resources

What Are Global Resources? Some platform features are shared across all organizations:

LLM Models

Shared Models:

Anthropic Claude (all versions)
OpenAI GPT (all versions)
Google Gemini
DeepSeek, Qwen, etc.

How It Works:

Models available to all organizations
Usage tracked per organization
API keys managed per organization

MCP Platforms

Shared Platforms:

GitHub, Firecrawl, 커스텀 MCP 등
Platform definitions shared
Credentials per-user or per-organization

How It Works:

Platform capabilities available to all
Authentication per user or org
Usage isolated per organization

Tool Registry

Shared Tools:

Brand search tools
Google search
File upload tools
Payment tools (AP2/x402)

How It Works:

Tool definitions global
Tool usage tracked per organization
Tool results isolated per organization

Documentation

Shared Resources:

Platform documentation
API reference
User guides
Support knowledge base

Always Available:

Same docs for all users
Accessible from any organization

Common Multi-Organization Scenarios

Scenario 1: Agency Managing Multiple Clients

Setup: Organization Structure:

Organization	Role	Members	Purpose
`myagency-internal`	OWNER	10 (your team)	Internal agency work, templates, testing
`clienta-workspace`	OWNER	3 (you + 2 client staff)	Client A production agents
`clientb-workspace`	OWNER	5 (you + 4 client staff)	Client B production agents
`clientc-workspace`	OWNER	2 (you + 1 client staff)	Client C production agents

Best Practices:

Use agency internal workspace for agent templates and testing
Clone templates to client organizations
Keep client data completely isolated
Transfer ownership when client relationship ends
Use consistent naming: {clientname}-workspace

Scenario 2: Enterprise with Multiple Departments

Setup: Organization Structure:

Organization	Role	Members	Purpose
`acme-marketing`	ADMIN	20	Marketing campaigns, content generation
`acme-sales`	ADMIN	15	Sales automation, lead qualification
`acme-engineering`	ADMIN	50	Code generation, documentation
`acme-data-science`	ADMIN	10	Data analysis, model training

Benefits:

Department autonomy (each dept manages own agents)
Separate billing (cost allocation per department)
Compliance (different data policies per dept)
Analytics (department-specific usage metrics)

Coordination:

Platform admin has OWNER role in all departments
Shared best practices document
Cross-department agent templates (manual copy)
Monthly usage review meetings

Scenario 3: Dev/Staging/Production Environments

Setup: Organization Structure:

Organization	Role	Members	Purpose	Features
`myapp-dev`	OWNER	5 (dev team)	Development, testing, experimentation	All features enabled, relaxed limits
`myapp-staging`	ADMIN	3 (QA team)	Pre-production testing, UAT	Production-like limits
`myapp-production`	OWNER	2 (senior devs)	Live production environment	Strict limits, monitoring

Workflow:

Develop new agents in myapp-dev
Test thoroughly in dev environment
Clone successful agents to myapp-staging
Perform UAT and QA validation
Manually recreate in myapp-production (safest)
Monitor production carefully

Best Practices:

Never test in production
Use different API keys per environment
Separate RAG datastores (dev uses test data)
Different feature flags per environment
Strict access control on production

Scenario 4: Personal + Professional Workspaces

Setup: Organization Structure:

Organization	Role	Billing	Purpose
`john-doe-personal`	OWNER	Personal credit card	Hobby projects, learning
`john-doe-freelance`	OWNER	Business credit card	Client deliverables
`acme-corp`	MEMBER	Company billing	Full-time job work
`consulting-inc`	ADMIN	Client billing	Part-time consulting

Benefits:

Clear work-life separation
Different billing accounts (personal vs business)
Professional work stays with employer
Freelance work is portable

Best Practices:

Use work email for employer organizations
Use personal email for personal workspace
Never mix personal and professional data
Archive freelance organizations after project ends

Organization Naming Best Practices

Naming Conventions

Agency/Consultancy
Enterprise Departments
Environment Separation
Personal/Professional

Pattern: {agency-name}-{client-name}Examples:

innovate-agency-clienta
innovate-agency-clientb
innovate-agency-internal

Benefits:

Consistent naming across clients
Easy to identify your organizations
Alphabetical sorting keeps them grouped

Slug Best Practices

✅ Good Slugs:

acme-corp-marketing (clear, descriptive)
clienta-workspace (simple, purposeful)
myapp-production (environment clear)
john-doe-personal (ownership clear)

❌ Bad Slugs:

org1, org2, org3 (meaningless)
test, temp, sandbox (too generic, conflicts likely)
acme_corp (use hyphens, not underscores)
AcmeCorp (lowercase only)
my-super-long-organization-name-with-many-words (too long)

Billing and Features Across Organizations

Per-Organization Billing (When Enabled)

Current Status: Junis is currently free during beta. Billing features will be enabled in future releases.

How It Will Work:

Feature	Single Organization	Multiple Organizations
Subscription	One subscription for all usage	Separate subscription per organization
Billing	One invoice	Separate invoice per organization
Payment Method	One credit card	Different cards per organization
Usage Limits	Shared across all projects	Isolated per organization
Overages	One overage charge	Overage per organization

Feature Limits Per Organization

Each organization has independent feature limits: Default Limits (STANDARD Organization):

{
  "max_agents": 10,              // Can create up to 10 agents
  "max_members": 50,             // Can invite up to 50 team members
  "max_sessions_per_day": 1000,  // 1,000 sessions per day
  "rag_enabled": true,           // RAG knowledge base enabled
  "payment_enabled": true,       // AP2/x402 payments enabled
  "mcp_platforms": true,         // MCP integrations enabled
  "scheduled_tasks": true        // Scheduled agent execution enabled
}

Example: Multi-Organization Limits:

Organization	Max Agents	Max Members	Max Sessions/Day	RAG	MCP
`myagency-internal`	10	50	1,000	✅	✅
`clienta-workspace`	10	50	1,000	✅	✅
`clientb-workspace`	10	50	1,000	✅	✅
Total	30 agents	150 members	3,000 sessions/day	-	-

Limits Add Up: If you have 3 organizations, you get 3× the limits (10 agents × 3 = 30 total agents).

Troubleshooting Multi-Organization Issues

Cannot Find Organization in Switcher

Symptoms: Organization doesn’t appear in organization switcher dropdownPossible Causes:

Organization status is PENDING (not yet approved)
You were removed from the organization
Organization was deleted
Browser cache issue

Solutions:

Check organization status in Settings > Organizations
Verify you’re still a member (check email for removal notification)
Clear browser cache and reload
Try logging out and logging back in
Contact organization OWNER to confirm membership

Switched Organization But See Wrong Data

Symptoms: After switching, still see previous organization’s agents/sessionsPossible Causes:

Page didn’t fully reload after switch
Browser cache showing stale data
API token not updated

Solutions:

Force refresh page: Cmd+Shift+R (Mac) / Ctrl+Shift+R (Windows)
Clear browser cache
Log out and log back in
Check organization name in header (confirm switch succeeded)
If using API, ensure you’re using the new token from switch response

Cannot Create New Organization

Symptoms: “Create Organization” button disabled or shows errorPossible Causes:

Email not verified
Organization limit reached (platform-level restriction)
Slug already taken
Invalid characters in organization name/slug

Solutions:

Verify email if prompted
Try a different slug (must be globally unique)
Use only lowercase letters, numbers, and hyphens in slug
Contact support if you need more than 10 organizations

Lost Access to Organization

Symptoms: “Access Denied” or “Not Found” when trying to access organizationPossible Causes:

You were removed from the organization
Organization was suspended or deleted
Your role was changed and you lost permissions
Organization is PENDING approval

Solutions:

Check email for removal or role change notifications
Verify organization status in your organizations list
Contact organization OWNER or ADMIN
If organization is PENDING, wait for approval

Organization Stuck in PENDING

Symptoms: Organization created but status stays PENDING for > 2 business daysPossible Causes:

Admin approval backlog
Organization name/purpose requires review
Missing required information

Solutions:

Wait 1-2 business days after creation
Check email for approval requests or follow-up questions
Edit organization settings to provide more details
Contact Junis support at [email protected]

Cannot Transfer Organization Ownership

Symptoms: Trying to transfer OWNER role but operation failsCurrent Status: Organization ownership transfer not yet implementedWorkaround:

Make the intended new owner an ADMIN
Give them full permissions
As current OWNER, restrict your own permissions (stay as OWNER but with limited actions)
Contact Junis support for manual ownership transfer if needed

Coming Soon: Self-service ownership transfer feature

API Reference for Multi-Organization Management

List Your Organizations

Endpoint: GET /api/organizations Authentication: Bearer token required Response:

{
  "organizations": [
    {
      "id": "org-uuid-1234",
      "name": "Acme Marketing",
      "slug": "acme-marketing",
      "status": "ACTIVE",
      "org_type": "STANDARD",
      "role": "OWNER",
      "member_count": 12,
      "agent_count": 25,
      "created_at": "2024-01-01T00:00:00Z",
      "last_active_at": "2024-01-10T16:00:00Z"
    },
    {
      "id": "org-uuid-5678",
      "name": "Personal Workspace",
      "slug": "john-doe-personal",
      "status": "PENDING",
      "org_type": "STANDARD",
      "role": "OWNER",
      "member_count": 1,
      "agent_count": 3,
      "created_at": "2024-01-09T10:00:00Z"
    }
  ],
  "total": 2,
  "current_organization_id": "org-uuid-1234"
}

Switch Organization

Endpoint: POST /api/organizations/{organization_id}/switch Authentication: Bearer token required Response:

{
  "message": "Switched to organization: Acme Marketing",
  "organization_id": "org-uuid-1234",
  "organization_name": "Acme Marketing",
  "new_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
}

Important: Use the new_token for all subsequent requests. It contains the new organization context.

Create Organization (Programmatically)

See “Organization Creation via API” section above.

What’s Next?

Organization Best Practices

Security, scaling, and advanced organization management strategies

Team Management

Back to team member management guide

Organization Overview

Back to organization system overview

Admin Dashboard

Learn about the admin dashboard interface

Additional Resources

Organization API Reference: Full API documentation for all organization endpoints
Enterprise Plans: Contact sales for custom organization limits and features
Migration Guide: Moving agents between organizations (coming soon)
Organization Templates: Pre-configured organization setups for common use cases

Need Help with Multi-Organization Setup? Contact Junis support at [email protected] or your dedicated account manager.

User Guides

​What You’ll Learn

​Why Multiple Organizations?

​Common Use Cases

Agency/Consultancy

Enterprise Departments

Dev/Staging/Production

Personal + Professional

​Single vs Multiple Organizations

​Creating Additional Organizations

​Prerequisites

​Step-by-Step Creation

​Organization Creation via API

​Switching Between Organizations

​Using the Organization Switcher

​What Changes When You Switch

​Organization Context Persistence

​Managing Multiple Organizations

​Organization List View

​Multi-Organization Dashboard

​Cross-Organization Features

​What’s Shared Across Organizations

User Account

Global Platform Access

​What’s Isolated Per Organization

​Global Resources

LLM Models

MCP Platforms

Tool Registry

Documentation

​Common Multi-Organization Scenarios

​Scenario 1: Agency Managing Multiple Clients

​Scenario 2: Enterprise with Multiple Departments

​Scenario 3: Dev/Staging/Production Environments

​Scenario 4: Personal + Professional Workspaces

​Organization Naming Best Practices

​Naming Conventions

​Slug Best Practices

​Billing and Features Across Organizations

​Per-Organization Billing (When Enabled)

​Feature Limits Per Organization

​Troubleshooting Multi-Organization Issues

​API Reference for Multi-Organization Management

​List Your Organizations

​Switch Organization

​Create Organization (Programmatically)

​What’s Next?

Organization Best Practices

Team Management

Organization Overview

Admin Dashboard

​Additional Resources

What You’ll Learn

Why Multiple Organizations?

Common Use Cases

Single vs Multiple Organizations

Creating Additional Organizations

Prerequisites

Step-by-Step Creation

Organization Creation via API

Switching Between Organizations

Using the Organization Switcher

What Changes When You Switch

Organization Context Persistence

Managing Multiple Organizations

Organization List View

Multi-Organization Dashboard

Cross-Organization Features

What’s Shared Across Organizations

What’s Isolated Per Organization

Global Resources

Common Multi-Organization Scenarios

Scenario 1: Agency Managing Multiple Clients

Scenario 2: Enterprise with Multiple Departments

Scenario 3: Dev/Staging/Production Environments

Scenario 4: Personal + Professional Workspaces

Organization Naming Best Practices

Naming Conventions

Slug Best Practices

Billing and Features Across Organizations

Per-Organization Billing (When Enabled)

Feature Limits Per Organization

Troubleshooting Multi-Organization Issues

API Reference for Multi-Organization Management

List Your Organizations

Switch Organization

Create Organization (Programmatically)

What’s Next?

Additional Resources