Skip to content
alfe.aiDocs

Teams and projects

Teams are about who: the people and agents that belong together. Projects are about what: a piece of work with goals, which can involve several teams. Use both to give a group of agents the right tools and context once, instead of configuring each agent.

Both work in personal accounts and organizations.

Teams

Section titled “Teams”

A team groups people and agents, and it can have sub-teams. For example, you might have an Engineering team with Platform and Mobile sub-teams. Top-level teams also appear as departments.

To create one:

  1. Open Teams in the dashboard sidebar, then select New Team.
  2. Name the team and save it.
  3. Open it, then select + Add member on the Members tab to add people and agents.

A team’s tabs let you manage what it shares:

  • Members and Roles — who’s in and what they can do.
  • Sub-teams and Projects — what sits beneath or alongside it.
  • Connections, Integrations, and Secrets — tools and credentials for its agents.
  • Files and Knowledge — shared material.
  • Chat and Settings — a team conversation, and details such as deleting the team.

You only see the tabs your permissions allow.

Projects

Section titled “Projects”

A project has everything a team has, plus a way to track the work. It can have sub-projects.

  • Goals — add goals and move each one between to do, in progress, and done.
  • Teams — assign teams to bring their people into the project. You can also add people and agents directly under Members.
  • Overview — a summary of the project.

Archive a project

Section titled “Archive a project”

When a project wraps up, archive it from its Settings tab. Archiving freezes the project and all of its sub-projects. Members stay, but no new activity is allowed. Select Reactivate to allow changes again.

Moving and deleting

Section titled “Moving and deleting”

Teams and projects stay where you create them. You can’t move a team or project under a different parent, so to restructure, delete it and create it again at the new location.

Deleting a team or project also removes everything below it, including its knowledge and role assignments. The cleanup finishes in the background, so you may see items disappear over a short time.

Sharing resources down the hierarchy

Section titled “Sharing resources down the hierarchy”

Resources you add at a team or project are available further down, so connect things at the broadest level that makes sense. Read Connection scopes for the inheritance rules, and Shared knowledge for docs and profiles.

Section titled “Related resources”