Skip to main content
A Project is a workspace inside iTeam, dedicated to a client, an area, a product or an initiative. Everything that happens there — conversations, objectives, knowledge, files and tasks — lives inside the project and doesn’t mix with the rest of the company. It’s the practical way to organize iTeam by context: each project is its own “world”, with the right agents and the right information.
An open project with its tabs

📸 Screenshot to insert [/en/projects/overview]: an open project showing the tabs at the top (Chat, Cortex, App, Workspace, Storage, Tasks, Processes, Codes) and the agents/teams panel on the right.

​
What a project is for

Organize by context

Bring together in one place everything that belongs to a client, area or initiative — without cluttering the whole company.

Isolate what's sensitive

A project’s objectives, knowledge and files stay exclusive to it. Whoever isn’t in the project doesn’t see them.

Give agents focus

The project’s agents work only with the project’s context — sharper answers, no noise.

Access inheritance

Whoever gets access to the project inherits the resources tied to it — a practical way to grant everything at once.

​
The project tabs

When you open a project, you’ll find a tab bar at the top. Each one is a complete workspace, restricted to that project:
Chat with the project’s agents and teams. The chat already runs in the project’s context: the agents see that project’s objectives, knowledge and files (and nothing from outside it).
The management brain of the project: Objectives, Actions, Results, Learnings, Meetings, Knowledge and Library — all isolated from the company Cortex. It’s the main page of a project; see Project Cortex.
The project’s interface (micro-app), when it has one. It gathers the widgets and screens the agents built for that project’s day-to-day.
The project’s shared workspace — the place where deliverables and collaborative materials stay within reach of the team and the agents.
The project’s data and collections. It’s where the information the project’s agents read and write is stored, isolated from other projects.
The project’s task board: what’s to do, in progress and done — including what the agents run asynchronously.
The automated multi-step routines that run inside the project.
The project’s code and scripts, when you need custom logic running in isolation.
Not every project uses every tab. Start with Chat and Cortex — the rest shows up as the project’s needs grow.

​
The agents and teams panel

On the right side of the project there’s a panel with the agents and teams that are part of it. It’s that project’s “team”.
1

Add agents or teams to the project

Choose from the agents/teams you have access to. From then on, they become part of the project and see its context.
2

Click an agent or team to chat

Clicking an agent (or team) in the panel opens the chat with it already selected, inside the project’s context. It’s the shortcut to put it to work right away.
3

Remove whoever's no longer needed

When you remove an agent from the project, it stops seeing that project’s context. Nothing at the company level is affected.
The same agent can take part in several projects. Inside each project it only sees that project’s context — it never crosses information between projects.

​
Next steps

Project Cortex

Objectives, knowledge and management exclusive to the project.

Project Agents

Who can access what inside a project.