Roles & Permissions

Vabro roles are used to control what users can edit within a Workspace, Project, or Team. There are eight different roles in Vabro to choose from:

• Guest - A Guest is a person who isn't explicitly a member of your organization, but who has read-only permissions to all public Projects in the Workspace.
• Admin - An Admin is the user responsible for managing a Workspace in Vabro. The Admin can manage all settings related to the workspace, projects, and teams from the Admin Console. 
• Additional Admin - An Additional Admin is a user who acts as a backup for the Admin to manage the Workspace. An Additional Admin possesses the same authority as the Admin except for the fact that they cannot remove the Admin from the Workspace.
• Product Owner - The Product Owner is the person responsible for maximizing business value for the project. The Product Owner is responsible for articulating customer requirements and maintaining business justification for the project. The Product Owner represents the Voice of the Customer. The Product Owner is responsible for ensuring clear communication of product or service functionality requirements to the Scrum Team, defining Acceptance Criteria, and ensuring those criteria are met. In other words, the Product Owner is responsible for ensuring that the Scrum Team delivers value.
• Additional Product Owner - An Additional Product Owner is a user who acts as a backup for the Product Owner to manage the Project and its requirements. An Additional Product Owner possesses the same authority as the Product Owner except for the fact that they cannot remove the Product Owner from an Epic.
• Scrum Master – The Scrum Master is a facilitator who ensures that the Scrum Team is provided with an environment conducive to completing the product’s development successfully. The Scrum Master guides, facilitates, and teaches Scrum practices to everyone involved in the project; clears impediments for the team; and ensures that Scrum processes are being followed. Note that the Scrum Master role is very different from the role played by the Project Manager in a traditional waterfall model of project management, in which the Project Manager works as a manager or leader for the project. The Scrum Master only works as a facilitator and he or she is at the same hierarchical level as anyone else in the Scrum Team—any person from the Scrum Team who learns how to facilitate Scrum projects can become the Scrum Master for a project or for a Sprint.
• Additional Scrum Master - An Additional Scrum Master is a user who acts as a backup for the Scrum Master to facilitate the Scrum Team. An Additional Scrum Master possesses the same authority as the Scrum Master except for the fact that they cannot remove the Scrum Master from a Team.
• Scrum Team - The Scrum Team is one of the Scrum Core Team roles. The Scrum Team works on creating the deliverables of the project and contributes to realizing business value for all stakeholders and the project. The optimum size for a Scrum Team is six to ten members—large enough to ensure adequate skill sets, but small enough to collaborate easily. A key benefit of a six-to-ten-member team is that communication and management are typically simple and require minimal effort.