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

# Teams & permissions

> How Ciclo organises work by team, the Admin / Editor / Member roles, and how strategy cascades from your Executive Team.

## Overview

Ciclo is organised around **teams** within your **organisation**. Each team has its own
strategy, roadmap, KPIs, and actions, and every person is given a **role** on each team
that controls what they can do.

## Teams

* Each team is a self-contained workspace with its own strategy, roadmap, performance, and
  actions.
* You switch between the teams you belong to using the **team selector** on the home page.
* Teams are created in **Settings → Teams**, where each has a **name**, **initials**, and
  **colour** used as a visual marker across Ciclo. Teams you no longer need can be
  **archived** and restored later.
* Many features let you **link** or **import** items between teams (a goal, KPI, or
  initiative), so the organisation stays aligned while each team keeps its own focus.

<Frame caption="Create and manage teams in Settings → Teams">
  <img src="https://mintcdn.com/ciclostrategy-5e0b62a7/xst0q8VQ171r6I_e/images/settings/teams-tab.png?fit=max&auto=format&n=xst0q8VQ171r6I_e&q=85&s=5113fc7747b2e65dface7be2bfd64403" alt="The Teams tab in Settings" width="1400" height="1061" data-path="images/settings/teams-tab.png" />
</Frame>

## The Executive Team

One team can be marked as your **Executive Team** — the origin point for **strategy
cascading**. Strategy elements defined here can flow down to other teams (who import and
link them), and the home page's **Are we on track?** section follows its headline goals.
Setting an Executive Team also improves the quality of Ciclo's AI analysis.

```mermaid theme={null}
flowchart TD
  O["Organisation"] --> E["Executive Team<br/>org-wide strategy"]
  E -->|strategy cascades down| A["Team A"]
  E -->|strategy cascades down| B["Team B"]
  E -->|strategy cascades down| C["Team C"]
```

## Roles

Each user is assigned a role **per team**, so someone can be an Admin on one team and a
Member on another:

<CardGroup cols={3}>
  <Card title="Admin" icon="user-gear">
    Full control of the team, including its settings and members.
  </Card>

  <Card title="Editor" icon="user-pen">
    Can create and edit the team's strategy, roadmap, KPIs, and actions.
  </Card>

  <Card title="Member" icon="user">
    Can participate in and view the team's work.
  </Card>
</CardGroup>

<Note>
  You only see the teams you're a member of. Being added to a team with an appropriate role
  is what gives someone access to that team's data. Some organisation-wide settings are
  limited to administrators.
</Note>

## Common tasks

<CardGroup cols={2}>
  <Card title="Invite a new member" icon="user-plus" href="/getting-started/inviting-your-team">
    Add someone and assign their team and role.
  </Card>

  <Card title="Manage teams & roles" icon="users-gear" href="/features/admin-settings">
    Create teams and change roles in Settings.
  </Card>
</CardGroup>

## Related

<CardGroup cols={2}>
  <Card title="Inviting your team" icon="user-plus" href="/getting-started/inviting-your-team" />

  <Card title="Organisation & admin settings" icon="gear" href="/features/admin-settings" />
</CardGroup>
