Playbook Roles

Select the role that best describes the user's role in Playbook, not necessarily their role within the organization.
1. Only one role marked with an asterisk (*) can be selected.
2. Roles that aren't marked with an asterisk, e.g., Admin, Reports Admin, etc. can be selected in addition to their primary role.

Use the following to decide which role is the best fit for each user.

Playbook Role	Responsibilities
*(Level 1) Read-Only	View-only access. Can't save anything.
*(Level 2) Casual User	User will manage his tasks in Playbook but not create or update plans. Attendance is typically optional for huddles and rolling wave planning meetings.
*(Level 3) Core Team Member	User will manage his tasks in Playbook and create and update portions of the project plan. Attendance is typically required for huddles and rolling wave planning meetings.
*(Level 4) Summary Owner	Mini-Project Leader of one or more summary tasks/workstreams. May facilitate team huddles and decentralized planning meetings.
*(Level 5) Project Leader	Manages the project plan's structure and the integration between different workstreams. Monitors threats to the critical path, impacts to buffers, and captures impact reasons. Manages reports & buffer charts and provides updates to stakeholders.
Manager/Director	Leads the organizational change by demonstrating in-depth knowledge of Playbook Methods. Assesses team health, removes organizational impediments, and coaches the team.
Admin	User has access to the Admin page to perform administrative functions (Groups, Projects, Departments, Resources/Users).
Reports Admin	User can change and save Shared reports created by other people in the Dashboard.

Playbook roles determine a user's training curriculum