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

# Teams

> Collaborate with your team and manage shared workspaces for AI agent projects

Teams enable seamless collaboration on AI agents while maintaining secure access control. By organizing your work into teams, you can share resources and workflows across your teams.

<CardGroup cols={2}>
  <Card title="Create Teams" icon="users-plus" href="#creating-teams">
    Set up workspaces for your organization
  </Card>

  <Card title="Manage Members" icon="user-gear" href="#team-roles--permissions">
    Control access with role-based permissions
  </Card>

  <Card title="Switch Workspaces" icon="toggle-left" href="#workspace-switching">
    Move between personal and team contexts
  </Card>

  <Card title="Share Resources" icon="share" href="#resource-scoping">
    Collaborate on projects, agents, automations, and more
  </Card>
</CardGroup>

## Creating Teams

Teams serve as collaborative workspaces where members can share projects, automations, agents, and other resources.

<Steps>
  <Step title="Access Workspace Switcher">
    Click the workspace switcher in the sidebar to open the workspace menu
  </Step>

  <Step title="Create New Team">
    Select "Create Team" from the dropdown menu
  </Step>

  <Step title="Configure Team">
    Provide a team name and optional description for your new team
  </Step>

  <Step title="Automatic Ownership">
    You'll automatically become the team owner with full administrative privileges
  </Step>
</Steps>

## Team Roles & Permissions

Teams use role-based access control (RBAC) to manage what members can do:

<AccordionGroup>
  <Accordion title="Owner" icon="crown">
    **Full Control**

    * Manage all team members and invitations
    * Delete the team
    * Access and modify all team resources
  </Accordion>

  <Accordion title="Admin" icon="shield-check">
    **Administrative Access**

    * Manage team members and send invitations
    * Create, edit, and delete team resources
    * Cannot delete the team
  </Accordion>

  <Accordion title="Member" icon="user">
    **Standard Access**

    * Create and manage their own resources within the team
    * View all team resources
    * Cannot manage other team members
    * Can leave the team voluntarily
  </Accordion>

  <Accordion title="Viewer" icon="eye">
    **Read-Only Access**

    * View team resources and activity
    * Cannot create, edit, or delete resources
    * Cannot manage team members
    * Perfect for stakeholders and observers
  </Accordion>
</AccordionGroup>

## Inviting Team Members

Team owners and admins can invite new members via email:

<Steps>
  <Step title="Navigate to Team Settings">
    Go to your team settings page from the workspace switcher
  </Step>

  <Step title="Send Invitation">
    Click "Invite Members", enter the email address, and select a role
  </Step>

  <Step title="Email Notification">
    The invitee will receive an email invitation with acceptance link
  </Step>

  <Step title="Accept or Decline">
    Invitees can accept or decline from their Palmier dashboard
  </Step>
</Steps>

<Info>
  **Invitation Details**

  * Invitations expire after 7 days
  * Only registered Palmier users can accept invitations
  * Pending invitations can be cancelled by admins/owners
</Info>

## Workspace Switching

The workspace switcher in the sidebar allows you to seamlessly move between your personal workspace and team workspaces.

### Personal vs Team Workspaces

<Tabs>
  <Tab title="Personal Workspace">
    **Your Individual Space**

    * Default workspace containing personal projects and resources
    * Only you have access to these resources
    * Ideal for individual work and experimentation
    * No collaboration features
  </Tab>

  <Tab title="Team Workspaces">
    **Shared Environments**

    * Collaborative spaces where team members work together
    * Resources are scoped to the team and visible to all members
    * Perfect for shared projects and workflows
    * Role-based access controls apply
  </Tab>
</Tabs>

### Resource Scoping

When you switch workspaces, all resources are automatically filtered based on your current context:

| Resource Type    | Personal Workspace                       | Team Workspace                       |
| ---------------- | ---------------------------------------- | ------------------------------------ |
| **Runs**         | Your individual agent runs               | Team member runs                     |
| **Projects**     | Personal projects only                   | Team projects visible to all members |
| **Automations**  | Your private automations                 | Shared team automations              |
| **Agents**       | Personal custom agents                   | Team-scoped agents available to all  |
| **Environments** | Individual dev environments              | Shared team environments             |
| **MCP**          | MCP connection with personal credentials | Shared across team agents            |
| **Secrets**      | Only accessible by you                   | Shared across team resources         |

<Warning>
  Resources created in a team workspace are visible to all team members according to their role permissions. Always verify your current workspace before creating sensitive resources.
</Warning>

<Warning>
  Team members without access to a repository cannot view runs (job details) for that repository, even if they are part of the team.
</Warning>

## Best Practices

### Team Organization

<CardGroup cols={2}>
  <Card title="Start Small" icon="seedling">
    Begin with a core team of trusted collaborators and gradually expand as workflows mature
  </Card>

  <Card title="Clear Roles" icon="hierarchy">
    Assign admin roles to team leads, member roles to contributors, and viewer roles to stakeholders
  </Card>

  <Card title="Naming Conventions" icon="tag">
    Use descriptive team names and establish consistent resource naming patterns
  </Card>

  <Card title="Regular Reviews" icon="calendar-check">
    Periodically review team membership and remove inactive members
  </Card>
</CardGroup>

***

Teams provide the foundation for collaborative AI-powered development. Start with a small team, establish clear workflows, and gradually expand your collaborative practices as your organization grows.