Roles and Permissions

Savah supports a set of predefined roles, each with fixed permissions to control what actions users can perform within PI Planning boards. These roles are locked, meaning their permissions cannot be customized and are consistent across the platform. A user's access and capabilities depend on the role assigned to them within a team that is linked to a workspace.

Available Roles

Admin

Grants full administrative access to workspaces where the user is a member of a team with this role. Key permissions include:

  • Access to workspace-level settings and configurations.

  • Ability to manage all teams and users within the workspace.

  • Full control over all Program Increment (PI) planning sessions inside the workspace.


PI Admin

This role is focused on managing a specific PI Planning session. A PI Admin can:

  • Create and manage backlog items, including Capabilities, Epics, and Stories.

  • Assign backlog items to teams.

  • Manage dependencies, objectives, milestones, and risks.

  • Conduct and manage the confidence voting process.

  • Adjust planning outcomes based on feedback.


Team Member

Team Members actively participate in the PI Planning process. They can:

  • Create and update user stories for their team.

  • Estimate story points and link stories to Epics.

  • Manage dependencies related to their work.

  • Participate in planning activities and vote during confidence sessions.


Observer

Observers have read-only access to all PI Planning boards. They are ideal for leadership and stakeholders who need visibility without editing rights. Observers can:

  • View all backlog items and team progress.

  • See dependencies, milestones, and objectives.

  • Review planning analytics and confidence vote results.


Role Resolution in Multiple Teams

If a user belongs to multiple teams with different roles, and those teams are linked to the same workspace, Savah will apply the highest level of role among them. For example:

If a user is a Team Member in Team A and a PI Admin in Team B, and both teams are linked to the same workspace, the user will be treated as a PI Admin in that workspace.

Last updated