Getting started
What ProjectBrain is, how these docs are organized, and where to start for your role.
ProjectBrain is where a team plans projects, tracks tasks, and reports progress. Projects hold tasks, a board, a timeline, standups, files and a wiki. Owners decide what each role can do, and everything belongs to one organization.
It is built for agencies, studios and internal teams who run several client or product projects at once. Clients can be invited to read and comment on the work that concerns them.
Start here
Section titled “Start here”- Create your first project and add a few tasks.
- Invite your team and give each person a role.
- Keep the glossary open. Some words, such as “milestone”, mean two things.
Where to go by role
Section titled “Where to go by role”| You are | Start with |
|---|---|
| A project manager or team lead | For project managers |
| Setting up how a team works | Scrum in ProjectBrain, or the Implementation overview |
| An owner or admin | Security and admin, then Invite your team |
| A team member | Create your first project and Standups |
How these docs are organized
Section titled “How these docs are organized”- Getting started: first steps and the glossary.
- Features: one page per part of the app, such as standups.
- AI and Agent orchestration: connecting AI tools, and letting agents work on approved tasks.
- Integrations: GitHub and other connected services.
- Security and admin and Trust center: roles, permissions and how your data is protected.
- Settings: what each settings screen does.
- Implementation: work styles and role guides for rolling ProjectBrain out.
- Best practices and Changelog.
Some features are in beta. Their pages carry a beta badge. If you do not see a feature, ask your admin to turn it on for your organization.