> ## Documentation Index
> Fetch the complete documentation index at: https://pulze.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Organization Management

> Admin guide for managing and configuring organizations in Pulze

<Note>
  **Admin Access Required**: This guide covers organization-level settings and management features that require admin permissions. Users with viewer or editor roles have limited access to these features.
</Note>

## Overview

As an administrator, you have full control over your organization's structure, settings, and access management. Organizations in Pulze are the top-level entity that contains all spaces, members, data, and resources. This guide covers everything you need to know about managing your organization effectively.

### Key Admin Responsibilities

* **Organization Settings**: Configure organization-wide defaults and branding
* **Member Management**: Control who has access and their permission levels
* **Resource Control**: Manage models, routers, assistants, and tools across the organization
* **API Key Management**: Generate and manage programmatic access
* **Billing & Plans**: Oversee subscription and usage across the organization

## Admin Dashboard Access

### Accessing Organization Settings

To access your organization's admin settings:

1. Click on your **profile icon** in the top right corner
2. Select your organization from the dropdown menu
3. Click **Manage Organization** to access the admin dashboard

<Frame>
  <img src="https://mintlify.s3.us-west-1.amazonaws.com/pulzeai/images/org-dropdown.png" alt="Organization dropdown menu" />
</Frame>

<Tip>
  The **Manage Organization** option is only visible to users with admin permissions.
</Tip>

### Switching Between Organizations

If you're an admin in multiple organizations:

1. Click your **profile icon** in the top right
2. Select the organization you want to switch to from the list
3. The interface will reload with the selected organization's context

<Note>
  Each organization has its own independent settings, members, spaces, and billing. When you switch organizations, you'll see only the resources belonging to that organization.
</Note>

## Creating a New Organization

As an admin, you can create new organizations to separate different teams, projects, or clients:

1. Click your **profile icon** in the top right
2. Select **+ New Organization**
3. Configure the organization:
   * **Organization Name** (required): Choose a clear, descriptive name
   * **Logo URL** (optional): Brand your organization with a custom logo
   * **Organization ID**: Automatically generated unique identifier for API integration

<Frame>
  <img src="https://mintlify.s3.us-west-1.amazonaws.com/pulzeai/images/create-org.png" alt="Create new organization" />
</Frame>

<Warning>
  Creating a new organization creates a separate billing entity. Each organization has its own subscription plan and usage tracking.
</Warning>

## Organization Administration

### General Settings

Access comprehensive organization settings through **Manage Organization**:

#### Organization Profile

* **Organization Name**: Update your organization's display name
  * This name appears throughout the platform for all members
  * Choose a name that clearly identifies your team or project
* **Logo URL**: Set or change your organization's logo
  * Supported formats: PNG, JPG, SVG (120x120 to 1800x1800 pixels)
  * Logo appears in navigation and organization switcher
* **Organization ID**: Your unique identifier
  * Read-only value used for API integrations
  * Required when using the Pulze API programmatically

#### Default Router Configuration

Configure the default routing strategy for all spaces:

* Set organization-wide router preference
* Choose between Pulze managed routers or custom routers
* Individual spaces can override this setting if needed

<Info>
  The default router setting applies to all new spaces automatically. Existing spaces retain their configured routers unless you change them individually.
</Info>

#### Conversation Naming Model

Select the AI model for auto-generating conversation titles:

* Affects all conversations across all spaces in the organization
* Helps maintain consistent, meaningful conversation naming
* Can be overridden at the space level if needed

### Member Administration

<Card title="Member Management" icon="users" href="/pulze/permissions/members">
  Control organization-wide access, roles, and permissions for all members.
</Card>

Admin capabilities for member management:

* **View All Members**: See complete list with roles and permissions
* **Invite Members**: Send email invitations with predefined roles
* **Manage Permissions**: Adjust member roles (Admin, Editor, Viewer)
* **Space Access**: Control which spaces members can access
* **Remove Members**: Revoke organization access when needed

Permission levels you can assign:

* **Admin**: Full control over organization and all resources
* **Editor**: Can create and modify resources, limited admin access
* **Viewer**: Read-only access to resources they're granted access to

<Tip>
  Use the principle of least privilege: grant members only the permissions they need for their role.
</Tip>

### API Key Management

<Card title="API Keys" icon="key" href="/pulze/permissions/api-keys">
  Generate and manage programmatic access to your organization's resources.
</Card>

As an admin, you can:

* **Create API Keys**: Generate keys with specific permission scopes
* **Scope Management**: Define exactly what each key can access
* **Monitor Usage**: Track API key activity and usage
* **Rotate Keys**: Update keys periodically for security
* **Revoke Access**: Immediately disable compromised keys

API key scopes include:

* Chat completions access
* Data management
* Conversation history
* Space management
* Model and router configuration

### Resource Control

Admins have organization-wide control over:

#### Models

* Enable/disable models across the organization
* Models disabled at org level are unavailable to all spaces
* Manage model visibility and access

#### Routers

* Configure custom routing strategies
* Set default routers for the organization
* Manage Pulze router versions

#### Assistants

* Control which assistants are available organization-wide
* Enable/disable assistants for all spaces
* Manage assistant visibility

#### Tools

* Enable/disable tools across the organization
* Control tool access and permissions
* Configure tool integrations

## Organization Hierarchy

Understanding how organizations structure your work:

```
Organization
├── Spaces
│   ├── Conversations
│   ├── Assistants
│   └── Models & Routers
├── Data
│   ├── Documents
│   ├── Datasets
│   └── Custom Data
├── Permissions
│   ├── Members
│   ├── API Keys
│   └── Access Control
└── Tasks
    └── Scheduled Tasks
```

## Admin Best Practices

<Tip>
  **Separation of Concerns**: Use separate organizations for different business units, clients, or projects to maintain clear boundaries and independent billing.
</Tip>

### Security Best Practices

1. **Regular Access Audits**: Review member permissions quarterly
2. **API Key Rotation**: Rotate API keys every 90 days or when team members leave
3. **Principle of Least Privilege**: Grant minimal necessary permissions
4. **Monitor Activity**: Regularly check logs for unusual access patterns

### Organization Management

1. **Clear Naming Conventions**: Use descriptive names for easy identification
2. **Consistent Branding**: Add logos to help members identify organizations quickly
3. **Documentation**: Maintain internal docs about your organization structure
4. **Backup Keys**: Store API keys securely in a password manager

### Resource Management

1. **Model Management**: Regularly review and disable unused models
2. **Router Optimization**: Monitor router performance and adjust settings
3. **Assistant Governance**: Maintain guidelines for assistant creation and usage
4. **Cost Control**: Monitor usage and set up alerts for unexpected spikes

### Member Onboarding

1. **Standard Procedures**: Create consistent onboarding processes
2. **Training Resources**: Provide documentation for new members
3. **Role Templates**: Define standard role configurations
4. **Gradual Access**: Start with minimal permissions, expand as needed

## Billing and Plans Administration

Each organization operates as a separate billing entity:

### Billing Management

* **Independent Subscriptions**: Each org has its own plan and billing cycle
* **Usage Tracking**: Monitor consumption across all spaces in the organization
* **Cost Allocation**: Track usage by space, member, or assistant
* **Plan Management**: Upgrade/downgrade plans as organizational needs change

<Card title="Billing Support" icon="credit-card">
  Contact [sales@pulze.ai](mailto:sales@pulze.ai) for billing questions, plan changes, or enterprise pricing.
</Card>

### Usage Monitoring

As an admin, monitor:

* Total API calls and token usage
* Per-space resource consumption
* Model usage patterns
* Cost trends over time

<Warning>
  Organization admins receive notifications when approaching usage limits or billing thresholds.
</Warning>

## Administrative Support

<CardGroup cols={2}>
  <Card title="Technical Support" icon="headset">
    Contact support for technical issues or platform questions.
  </Card>

  <Card title="Enterprise Solutions" icon="building">
    Reach out to [sales@pulze.ai](mailto:sales@pulze.ai) for enterprise features and custom solutions.
  </Card>
</CardGroup>

## Related Resources

<CardGroup cols={2}>
  <Card title="Spaces Overview" icon="rocket" href="/pulze/spaces/overview">
    Learn about creating and managing spaces within your organization
  </Card>

  <Card title="Permissions" icon="shield" href="/pulze/permissions/overview">
    Understand role-based access control
  </Card>

  <Card title="Members" icon="users" href="/pulze/permissions/members">
    Manage team members and their access
  </Card>

  <Card title="API Keys" icon="key" href="/pulze/permissions/api-keys">
    Generate and manage API keys
  </Card>
</CardGroup>
