User roles and permissions hierarchy

Forest uses a 3-tier role system: Platform, Company, and Project levels.

Project level roles

Project roles control what users can do within a specific project.

ActionAdminTeam AdminMemberViewer
Create issues✓*
Edit issues✓*
Delete issues✓*
Change settings
Invite members✓*
Manage teams✓*
View all data

*Team Admins can only manage their own team(s).

Admin

Full control over the project:

  • Create, edit, delete issues
  • Modify project settings
  • Invite and remove members
  • Create and manage teams
  • View capacity and budget reports
  • Delete the project

Team Admin

Can manage their assigned team(s):

  • Create, edit, delete issues in their team
  • Manage members in their team
  • Edit team capacity and time allocation
  • Invite members to their team
  • Cannot access other teams
  • Cannot modify project settings

Member

Can perform core work activities:

  • Create and edit issues
  • Update issue status
  • Comment and collaborate
  • View capacity and budget data
  • Assign issues to themselves
  • Cannot delete issues
  • Cannot modify settings
  • Cannot invite new members

Viewer

Can view content only:

  • View all issues and boards
  • View timelines and reports
  • View comments
  • Cannot create, edit, or delete anything
  • Cannot modify settings

Company and Platform roles

In addition to project roles, users may have:

  • Company Owner / Admin — Manage all projects in a company
  • Platform Owner / Admin — Manage the entire system

These roles grant broader permissions across projects and companies.

On this page

  1. Project level roles
  2. Admin
  3. Team Admin
  4. Member
  5. Viewer
  6. Company and Platform roles

Not finding the help you need?