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

# Organizations

> Understanding VantEdge's multi-tenant architecture and organization isolation

## What is an Organization?

An **organization** in VantEdge is a completely isolated tenant environment. Each organization gets its own database schema, unique domain, and dedicated resources, ensuring complete data separation between different teams or companies.

## Multi-Tenant Architecture

VantEdge operates as a **multi-tenant platform** where each organization is a separate tenant:

```
Organization: "Acme Corp"
├── Domain: acme.vantedge.run
├── Database Schema: org_acme_db
├── Isolated Resources: Complete separation
└── Team Access: Only Acme Corp members

Organization: "Beta Inc"  
├── Domain: beta.vantedge.run
├── Database Schema: org_beta_db
├── Isolated Resources: Complete separation
└── Team Access: Only Beta Inc members
```

## Key Features

**🔒 Complete Data Isolation**

* Each organization has its own database schema
* No cross-tenant data access possible
* Encrypted data at rest and in transit

**🌐 Unique Domains**

* Every organization gets a custom subdomain
* Clean, branded experience for your team
* Easy bookmark and sharing within organization

**👥 Team Management**

* Organization-level user management
* Role-based access controls
* Invitation and member onboarding system

**📊 Resource Separation**

* Cloud integrations belong to organizations
* Workspaces are organization-scoped
* Complete billing and usage isolation

## Organization Types

### Personal Organizations

* **Automatically created** when you sign up
* **Single-user** environment for individual work
* **Domain**: Usually `firstname-lastname.vantedge.run`
* **Use cases**: Personal projects, learning, experimentation

### Team Organizations

* **Manually created** for teams and companies
* **Multi-user** collaborative environment
* **Custom domain**: `company-name.vantedge.run`
* **Use cases**: Team projects, production workloads, enterprise usage

## Organization Hierarchy

```
Organization: "Enterprise Corp"
├── Members: Users with different roles
├── Workspaces: Project containers
│   ├── "AI Training - Production"
│   ├── "Web App - Staging"
│   └── "Data Pipeline - Development"
├── Integrations: Cloud provider connections
│   ├── AWS Production Account
│   ├── AWS Development Account
│   └── GCP Analytics Account
└── Resources: Distributed across workspaces
    ├── Kubernetes clusters
    ├── Model deployments
    ├── AI gateways
    └── Secrets and configurations
```

## Organization Roles

**Owner**

* Full control over organization
* Billing and subscription management
* Can delete organization
* Manage all members and workspaces

**Admin**

* Manage workspaces and members
* Configure integrations and settings
* Cannot delete organization or manage billing
* Full access to all organization resources

**Member**

* Access to assigned workspaces
* Can create resources within permitted workspaces
* Limited admin functions
* Cannot manage organization-level settings

## Getting Started

**For Individuals:**

1. Sign up → Personal organization created automatically
2. Start with your default personal workspace
3. Add cloud integrations and begin building

**For Teams:**

1. Create or join a team organization
2. Set up shared cloud integrations
3. Create project-specific workspaces
4. Invite team members with appropriate roles

***

Organizations provide the foundation for VantEdge's secure, multi-tenant architecture, ensuring your team's data and resources remain completely isolated.