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

# Team Management

> Organize your team, manage permissions, and control access to your functions and projects.

## Organizations & Projects

**Organizations** are your team workspace - think of them like your company account that handles billing and team members.

**Projects** group related functions together - like "Website API" or "Payment System".

```text Structure Example theme={"system"}
Acme Corp (Organization)
├── Website API (Project)
│   ├── User Login Function
│   ├── Payment Function
│   └── Email Function
└── Mobile App (Project)
    ├── Push Notifications
    └── File Upload
```

## Team Roles & Permissions

### Roles

<CardGroup cols={3}>
  <Card title="Owner" icon="crown">
    Company founder, CTO, or whoever manages billing and organization
  </Card>

  <Card title="Admin" icon="users-gear">
    Team leads, senior developers who manage projects and team members
  </Card>

  <Card title="Member" icon="code">
    Developers who build and deploy functions in assigned projects
  </Card>
</CardGroup>

### Permissions

Each team member gets a role that controls what they can access and modify:

| Permission                   | Owner | Admin | Member |
| ---------------------------- | ----- | ----- | ------ |
| **Organization Management**  |       |       |        |
| Delete organization          | ✅     | ❌     | ❌      |
| Manage billing               | ✅     | ❌     | ❌      |
| Change organization settings | ✅     | ❌     | ❌      |
| **Team Management**          |       |       |        |
| Invite team members          | ✅     | ✅     | ❌      |
| Remove team members          | ✅     | ✅     | ❌      |
| Change member roles          | ✅     | ✅     | ❌      |
| **Project Management**       |       |       |        |
| Create projects              | ✅     | ✅     | ❌      |
| Delete projects              | ✅     | ✅     | ❌      |
| Modify project settings      | ✅     | ✅     | ❌      |
| **Function Management**      |       |       |        |
| Create functions             | ✅     | ✅     | ✅      |
| Edit function code           | ✅     | ✅     | ✅      |
| Delete functions             | ✅     | ✅     | ✅      |
| Deploy functions             | ✅     | ✅     | ✅      |
| **Monitoring & Logs**        |       |       |        |
| View function logs           | ✅     | ✅     | ✅      |
| View usage metrics           | ✅     | ✅     | ✅      |
| View billing details         | ✅     | ❌     | ❌      |

<Warning>
  **Important**: Only owners can delete the organization or manage billing. Choose your owner carefully.
</Warning>

## Setting Up Your Team

<CardGroup cols={2}>
  <Card title="Create Organization" icon="building">
    Set up your team workspace with a clear name and description
  </Card>

  <Card title="Invite Team Members" icon="user-plus">
    Add your team and assign appropriate roles based on their responsibilities
  </Card>

  <Card title="Create Projects" icon="folder-plus">
    Organize your functions into logical groups for better management
  </Card>

  <Card title="Control Access" icon="shield-check">
    Manage which team members can access specific projects
  </Card>
</CardGroup>

## Team Invitations

Invite team members by email and assign them Admin or Member roles. New members can sign up using Google, GitHub, or email authentication - they must use the same email address that received the invitation.

### Team Management Best Practices

<CardGroup cols={2}>
  <Card title="Start with Minimal Access" icon="key">
    Give team members only the permissions they need initially - you can always add more later
  </Card>

  <Card title="Regular Access Reviews" icon="calendar-check">
    Review team permissions monthly and remove access for members who no longer need it
  </Card>

  <Card title="Clear Role Communication" icon="message-circle">
    Explain project access and role responsibilities when inviting new team members
  </Card>

  <Card title="Organize by Function" icon="layers">
    Group related functions into projects that match your team's workflow
  </Card>
</CardGroup>

## Project Organization

Use clear, descriptive project names that explain what the functions do:

**✅ Good Names**

* `user-authentication` - Clear and specific
* `payment-processing` - Describes the purpose
* `email-notifications` - Easy to understand

**❌ Avoid These**

* `project1` - Not descriptive
* `misc-functions` - Too vague
* `everything` - Not organized

## Single Sign-On (SSO)

<CardGroup cols={3}>
  <Card title="Google SSO" icon="google">
    Sign up with Google accounts
  </Card>

  <Card title="GitHub SSO" icon="github">
    Use GitHub authentication
  </Card>

  <Card title="Magic Links" icon="link">
    Email-based authentication with secure login links
  </Card>
</CardGroup>

<Info>
  **Important**: New members must use the same email address that received the invitation to automatically join with the correct role and project access.
</Info>

## Billing & Cost Management

<CardGroup cols={3}>
  <Card title="Organization Billing" icon="credit-card">
    All costs roll up to the organization owner for centralized management
  </Card>

  <Card title="Project Breakdown" icon="chart-pie">
    See which projects consume the most resources and optimize accordingly
  </Card>

  <Card title="Usage Transparency" icon="eye">
    Admins see organization usage, members see their own function metrics
  </Card>
</CardGroup>