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

# Organizations

> Learn about organizations in Pylee and how they help you manage your MCP infrastructure

# Organizations

Organizations are the top-level containers in Pylee that help you organize and manage your MCP (Model Context Protocol) infrastructure. They provide a centralized way to group related registries, servers, and team members under a single administrative unit.

## What is an Organization?

An organization in Pylee represents a workspace where you can:

* **Manage multiple registries** - Group related MCP server registries together
* **Control access** - Define who can view, edit, or administer your MCP resources
* **Organize teams** - Collaborate with team members on MCP server development and deployment
* **Centralize configuration** - Share variables and secrets across registries and servers

## Organization Structure

Each organization contains:

### Registries

Collections of MCP servers that work together to provide specific functionality. Organizations can have multiple registries for different use cases or environments.

### Variables and Secrets

Shared configuration that can be used across all registries and servers within the organization. This promotes consistency and reduces duplication.

### Team Members

Users who have been granted access to the organization with different permission levels:

* **Admins** - Full control over the organization, including managing members and settings
* **Members** - Can view and interact with resources based on their permissions

## Creating an Organization

Organizations are typically created when you first sign up for Pylee or when you need to separate different projects or teams. Each organization has:

* **Name** - A human-readable name for your organization
* **Slug** - A URL-friendly identifier used in the dashboard
* **Description** - Optional description explaining the organization's purpose
* **Overview** - Detailed documentation about the organization (supports Markdown)

## Organization Settings

### Access Control

Organizations provide granular access control, allowing you to:

* Invite team members via email
* Assign different permission levels
* Manage who can create or modify registries and servers

### Configuration Management

* Define organization-level variables that can be inherited by registries and servers
* Store sensitive information as secrets with proper access controls
* Maintain consistency across your MCP infrastructure

## Best Practices

### Organization Structure

* Use clear, descriptive names for your organizations
* Create separate organizations for different environments (development, staging, production)
* Consider team boundaries when structuring organizations

### Access Management

* Regularly review organization members and their permissions
* Use the principle of least privilege when assigning roles
* Document team member roles and responsibilities

### Documentation

* Keep your organization overview up-to-date with current objectives and architecture
* Document any organization-specific conventions or standards
* Include contact information for organization administrators

## Getting Started

When you first access your organization, you'll see an onboarding timeline that guides you through:

1. **Setting up your organization** - Adding description and overview documentation
2. **Creating your first registry** - Organizing your MCP servers
3. **Inviting team members** - Collaborating with others
4. **Configuring variables and secrets** - Setting up shared configuration

This onboarding process ensures you have everything needed to effectively use Pylee for your MCP server management needs.