> For the complete documentation index, see [llms.txt](https://i7os.gitbook.io/i7os-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://i7os.gitbook.io/i7os-docs/workspaces-and-teams.md).

# Workspaces and teams

### Workspaces and projects

Use a workspace for one organization or agency. Inside it, use projects to separate:

* individual brands
* clients
* campaigns
* internal initiatives
* time-limited collaborations

A project can become a dedicated brand workspace with its own brand knowledge, files, people, and planning.

### Invite collaborators

Workspace administrators can invite people by email. Project invitations make it possible to involve someone only where their contribution is needed.

Before inviting a collaborator, decide whether they need:

* access to the entire workspace
* access to selected projects
* permission to manage projects
* permission to edit brand or design information

### Keep client work separated

Agencies can create one project per client or brand. This keeps tasks, brand foundations, visual references, and collaborators organized without mixing contexts.

### Team collaboration

Depending on the area of i7OS, teams can:

* assign and update tasks
* add comments and checklists
* mention collaborators in documents and brainstorms
* share files and project knowledge
* collaborate on whiteboards in real time
* follow activity inside the workspace

### Practical setup

For a small team, start with:

1. one workspace
2. one project for each active brand
3. a small set of workspace administrators
4. project access for everyone else
5. one agreed place for files and one shared planning structure<br>

Continue with Brand workspace to build the shared source of truth.