Roles & Permissions

Vabro roles are used to control what users can edit within an Organization,Workspace, Project,Workflow or Team.
 

• Organizational Admin- An Organizational Admin has the highest level of control across the entire organization. They can manage all workspaces, users, settings, billing, and security policies. They can add or remove Organizational Admins and oversee the platform's overall governance.
• Additional Organization Admin- An Additional Organization Admin serves as a backup to the Organizational Admin. They possess the same administrative powers and responsibilities across the organization, except they cannot remove the primary Organizational Admin.
• Organisation Member- An Organization Member is a user who has access to one or more workspaces within the organization. They can participate in projects, tasks, and workflows as per their permissions but do not have administrative privileges over the organization.
• Workspace Admin - A Workspace Admin is responsible for managing a specific workspace. They have full control over workspace settings, can create and manage boards, add or remove members, and oversee the overall workflow within the workspace.
• Additional Workspace Admin - An Additional Workspace Admin acts as a backup to the Workspace Admin. They have the same permissions and responsibilities as the Workspace Admin, except they cannot remove the primary Workspace Admin from the workspace
• Workspace Member- A Workspace Member is a user who has access to the boards and tasks within a specific workspace. They can collaborate on projects and contribute to workflows based on the permissions assigned to them but do not have administrative control.
• 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.
• Kanban Manager- Ensures the workflow is optimized, the board is properly maintained, and blockers are addressed promptly.
• Additional Kanban Manager- An Additional Kanban Manager is a user who acts as a backup for the Kanban Manager to support and maintain the Kanban workflow. An Additional Kanban Manager holds the same responsibilities and authority as the Kanban Manager, including optimizing workflow, maintaining the board, and resolving blockers—except they cannot remove the primary Kanban Manager from a Board.
• Team Members: The individuals doing the work. They are responsible for pulling tasks from the board and moving them through each stage as progress is made.