Admin | 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.

To help you decide which role is the best fit for a user, use the following guideline.

Playbook Role	Responsibilities
*(Level 1) Read-Only	None. User can view projects but is not able to save.
*(Level 2) Casual User	User will manage his tasks in Playbook but not develop 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 develop plans. 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	Manage the plan structure and the integration between different workstreams. Monitor threats to critical path, impacts to buffers, & captures impact reasons. Manage reports & buffer charts and provides updates to stakeholders.
Manager/ Director	Lead the organizational change by demonstrating in-depth knowledge of Playbook Methods. Assess team health, remove organizational impediments, and coach 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 the course a user will be automatically enrolled in.