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

# Teams & Organizations

> Understanding multi-tenancy, team collaboration, and organization management in StatusStack

## Overview

StatusStack uses a hierarchical multi-tenant architecture to support teams of all sizes, from small startups to large MSPs managing hundreds of clients.

```
Organization (Your Company)
  ├── Team 1 (Engineering)
  │     ├── Stacks
  │     ├── Monitors
  │     ├── Notification Rules
  │     └── Users (Members, Admins)
  ├── Team 2 (Operations)
  └── Team 3 (Client: Acme Corp) → MSP Use Case
```

***

## Organizations

### What is an Organization?

An **Organization** is the top-level entity in StatusStack that represents your company or business. Everything in StatusStack belongs to an Organization.

<CardGroup cols={2}>
  <Card title="Single Tenant" icon="building">
    All your data is isolated from other Organizations
  </Card>

  <Card title="Subscription Billing" icon="credit-card">
    Subscription and billing are managed at the Organization level
  </Card>

  <Card title="Teams Management" icon="users">
    Create multiple Teams within your Organization
  </Card>

  <Card title="Shared Resources" icon="share-nodes">
    Share Sources and templates across Teams
  </Card>
</CardGroup>

### Organization Settings

Manage your Organization from the dashboard:

<Steps>
  <Step title="Navigate to Settings">
    Click **Settings** → **Organization** in the sidebar
  </Step>

  <Step title="Update Details">
    Configure Organization information:

    * Organization Name
    * Company Website
    * Contact Email
    * Time Zone
    * Logo (for branding)
  </Step>

  <Step title="Manage Subscription">
    View and manage your subscription:

    * Current plan (Free, Pro, Enterprise)
    * Usage statistics
    * Billing history
    * Payment methods
  </Step>
</Steps>

***

## Teams

### What are Teams?

**Teams** provide logical separation within your Organization. Teams are perfect for:

* **Departments** - Engineering, Operations, Support
* **Environments** - Production, Staging, Development
* **Clients** - MSP client management (Acme Corp, XYZ Inc.)
* **Projects** - Product A, Product B

### Team Hierarchy

```
Your Organization
  ├── Engineering Team
  │     ├── Production Stack
  │     ├── Staging Stack
  │     ├── 15 Website Monitors
  │     └── Users: Alice (Admin), Bob (Member)
  │
  ├── Operations Team
  │     ├── Infrastructure Stack
  │     ├── 5 Website Monitors
  │     └── Users: Charlie (Admin), Dave (Member)
  │
  └── MSP Client: Acme Corp
        ├── Acme Production Stack
        ├── Acme Staging Stack
        └── Users: Acme User (Viewer)
```

### Creating Teams

<Steps>
  <Step title="Navigate to Teams">
    Go to **Settings** → **Teams** in the sidebar
  </Step>

  <Step title="Create New Team">
    Click **"Create Team"** button
  </Step>

  <Step title="Configure Team">
    Fill in team details:

    ```yaml theme={null}
    Team Name: Engineering
    Description: Engineering team's monitoring
    Color: Blue (for visual identification)
    ```
  </Step>

  <Step title="Invite Members">
    Add team members with roles:

    * **Admin** - Full team management
    * **Member** - Create/edit resources
    * **Viewer** - Read-only access
  </Step>
</Steps>

***

## User Roles & Permissions

StatusStack has two levels of roles:

### Organization-Level Roles

| Role       | Permissions                                       | Use Case              |
| ---------- | ------------------------------------------------- | --------------------- |
| **Owner**  | Full access to everything including billing       | Company owner/founder |
| **Admin**  | Manage teams, users, and all resources            | IT director, CTO      |
| **Member** | Create and manage resources within assigned teams | Engineers, operators  |

### Team-Level Roles

| Role            | Permissions                                 | Use Case                    |
| --------------- | ------------------------------------------- | --------------------------- |
| **Team Admin**  | Full access within the team                 | Team lead, project manager  |
| **Team Member** | Create/edit Stacks, Monitors, Notifications | Engineers, developers       |
| **Team Viewer** | Read-only access to team resources          | Stakeholders, clients (MSP) |

### Permission Matrix

| Action                  | Owner | Org Admin | Org Member | Team Admin | Team Member | Team Viewer |
| ----------------------- | ----- | --------- | ---------- | ---------- | ----------- | ----------- |
| Manage billing          | ✅     | ❌         | ❌          | ❌          | ❌           | ❌           |
| Create teams            | ✅     | ✅         | ❌          | ❌          | ❌           | ❌           |
| Delete teams            | ✅     | ✅         | ❌          | ❌          | ❌           | ❌           |
| Invite org users        | ✅     | ✅         | ❌          | ❌          | ❌           | ❌           |
| Invite team users       | ✅     | ✅         | ❌          | ✅          | ❌           | ❌           |
| Create Stacks           | ✅     | ✅         | ✅\*        | ✅          | ✅           | ❌           |
| Delete Stacks           | ✅     | ✅         | ✅\*        | ✅          | ✅           | ❌           |
| View Stacks             | ✅     | ✅         | ✅\*        | ✅          | ✅           | ✅           |
| Create Monitors         | ✅     | ✅         | ✅\*        | ✅          | ✅           | ❌           |
| Configure Notifications | ✅     | ✅         | ✅\*        | ✅          | ✅           | ❌           |
| View Analytics          | ✅     | ✅         | ✅\*        | ✅          | ✅           | ✅           |

\*Only within teams they're a member of

***

## Team Management

### Inviting Team Members

<Tabs>
  <Tab title="Via Dashboard">
    1. Navigate to **Settings** → **Teams**
    2. Select the team
    3. Click **"Invite Member"**
    4. Enter email address
    5. Select role (Admin, Member, Viewer)
    6. Send invitation
  </Tab>

  <Tab title="Bulk Invite">
    1. Go to team settings
    2. Click **"Bulk Invite"**
    3. Paste emails (one per line)
    4. Select default role
    5. Send invitations
  </Tab>
</Tabs>

### Managing Team Members

**Change Role:**

1. Go to team settings
2. Find user in members list
3. Click role dropdown
4. Select new role

**Remove Member:**

1. Go to team settings
2. Find user in members list
3. Click "Remove" button
4. Confirm removal

**Transfer Ownership:**

1. Organization Owner only
2. Go to organization settings
3. Click "Transfer Ownership"
4. Select new owner
5. Confirm transfer

***

## Multi-Team Workflows

### Scenario 1: Department-Based Teams

Organize by company departments:

```
Acme Corp Organization
  ├── Engineering Team
  │     ├── Production API Stack
  │     ├── Staging API Stack
  │     └── Development Stack
  │
  ├── DevOps Team
  │     ├── Infrastructure Stack
  │     ├── Database Stack
  │     └── CDN Stack
  │
  └── Support Team
        ├── Customer Services Stack
        └── Help Desk Stack
```

**Benefits:**

* Clear ownership and responsibility
* Department-specific monitoring
* Targeted notifications per team

### Scenario 2: Environment-Based Teams

Organize by deployment environment:

```
SaaS Startup Organization
  ├── Production Team
  │     ├── Prod API Stack
  │     ├── Prod Database Stack
  │     └── Users: On-call engineers
  │
  ├── Staging Team
  │     ├── Staging Stack
  │     └── Users: All engineers
  │
  └── Development Team
        └── Dev Stack
```

**Benefits:**

* Environment isolation
* Role-based access per environment
* Separate notification rules

### Scenario 3: MSP Client Teams

Managed Service Providers managing multiple clients:

```
MSP Company Organization
  ├── Internal Operations Team
  │     └── MSP Infrastructure Stack
  │
  ├── Client: Acme Corp Team
  │     ├── Acme Production Stack
  │     ├── Acme Staging Stack
  │     └── Users: Acme stakeholders (Viewers)
  │
  ├── Client: Beta Inc Team
  │     ├── Beta Production Stack
  │     └── Users: Beta stakeholders (Viewers)
  │
  └── Client: Gamma LLC Team
        └── Gamma Stack
```

**Benefits:**

* Complete client isolation
* Client-specific branding
* Client portal access
* Per-client billing

See [MSP Setup Guide](/guides/msp-setup) for detailed MSP workflows.

***

## Access Control Best Practices

<AccordionGroup>
  <Accordion title="Principle of Least Privilege">
    **Start restrictive, expand as needed**

    * New users → Viewer role initially
    * Promoted to Member after training
    * Only trusted users get Admin role
    * Limit Organization Owners to 1-2 people
  </Accordion>

  <Accordion title="Team Separation">
    **Keep teams focused**

    * Production teams separate from development
    * Client teams isolated from each other (MSP)
    * Clear ownership of Stacks and Monitors
  </Accordion>

  <Accordion title="Regular Access Review">
    **Quarterly access audit**

    * Review active users
    * Remove users who left company
    * Verify roles are appropriate
    * Update team memberships
  </Accordion>

  <Accordion title="Secure Invitations">
    **Invitation hygiene**

    * Use company email addresses only
    * Set expiration on invitations
    * Verify identity before granting access
    * Use 2FA for sensitive teams
  </Accordion>
</AccordionGroup>

***

## Organization Limits by Plan

| Resource            | Free | Pro       | Enterprise |
| ------------------- | ---- | --------- | ---------- |
| **Organizations**   | 1    | 1         | Unlimited  |
| **Teams per Org**   | 1    | 5         | Unlimited  |
| **Users per Org**   | 3    | 25        | Unlimited  |
| **Users per Team**  | 3    | Unlimited | Unlimited  |
| **Stacks per Team** | 1    | 10        | Unlimited  |

***

## MSP-Specific Features

### Client Portal Access

Grant clients view-only access to their monitoring:

1. Create a team for the client

2. Invite client users with **Viewer** role

3. Client users can:
   * View their Stack status
   * See incident history
   * Subscribe to email updates
   * Access public status pages

4. Client users **cannot**:
   * Modify Stacks or Monitors
   * Access other clients' data
   * View billing information
   * Change notification settings

### Client Branding

Customize per-client branding:

* **Custom Logos** - Upload client logo for their team
* **Custom Colors** - Match client brand colors
* **Custom Domains** - status.clientdomain.com
* **White-Label** - Hide StatusStack branding (Enterprise)

See [MSP Branding Guide](/guides/msp-branding) for details.

***

## Common Scenarios

### Adding a New Employee

<Steps>
  <Step title="Create User Account">
    Organization Admin invites user to Organization
  </Step>

  <Step title="Assign to Teams">
    Add user to appropriate teams (Engineering, Operations, etc.)
  </Step>

  <Step title="Set Team Roles">
    Assign role in each team (typically start with Viewer or Member)
  </Step>

  <Step title="User Accepts Invite">
    User clicks invitation link and creates account
  </Step>
</Steps>

### Offboarding an Employee

<Steps>
  <Step title="Remove from Teams">
    Remove user from all teams in organization
  </Step>

  <Step title="Revoke Access">
    User automatically loses access to all resources
  </Step>

  <Step title="Audit Changes">
    Review any resources the user created or modified
  </Step>

  <Step title="Transfer Ownership">
    If user owned Stacks/Monitors, transfer to another user
  </Step>
</Steps>

### Adding a New Client (MSP)

<Steps>
  <Step title="Create Client Team">
    Create a new team for the client: "Client: Acme Corp"
  </Step>

  <Step title="Set Up Stacks">
    Create client-specific Stacks within the team
  </Step>

  <Step title="Invite Client Users">
    Invite client stakeholders with Viewer role
  </Step>

  <Step title="Configure Branding">
    Customize logo, colors, and domain for client
  </Step>

  <Step title="Share Status Page">
    Provide client with their branded status page URL
  </Step>
</Steps>

***

## Troubleshooting

### User Can't Access a Stack

**Check:**

1. User is member of the correct team
2. Stack belongs to that team
3. User has at least Viewer role
4. User accepted team invitation

### User Can't Create Resources

**Possible Causes:**

1. User has Viewer role (read-only)
2. Organization quota reached (upgrade plan)
3. User not member of any team

### Invitation Not Received

**Solutions:**

1. Check spam/junk folder
2. Verify email address is correct
3. Resend invitation
4. Try different email provider

***

## Next Steps

<CardGroup cols={2}>
  <Card title="MSP Setup Guide" icon="building" href="/guides/msp-setup">
    Configure multi-client monitoring
  </Card>

  <Card title="Team Management" icon="users" href="/account/team-management">
    Detailed team management documentation
  </Card>

  <Card title="User Roles" icon="shield" href="/account/security">
    Security and access control
  </Card>

  <Card title="Subscription Plans" icon="credit-card" href="/account/subscription-plans">
    Compare plans and features
  </Card>
</CardGroup>