Team Members in Requify
Project Roles
Requify has different categories for team members on a per-project basis:
Administrator
- They can do anything inside the project
Stakeholder
- An individual who has some controlling interest in the project
- Has elevated permissions on the project
Tech Lead
- Considered a technical authority
- Has elevated permissions on the project
Developer
- Is developing the product
Tester
- Is dedicated to testing the product
Outsider
- An individual who is interested in the project, but is not allowed to modify anything
No Access
- An individual who is not allowed to view the project at all
Role Permissions
Each role in Requify comes with specific permissions:
Administrator
- Create, edit, and delete all project content
- Manage team members and their roles
- Configure project settings and integrations
- Access billing and subscription information
- Archive or delete the project
Stakeholder
- Create and edit requirements
- Approve or reject requirement changes
- View all project content
- Comment on any item
- Access reports and analytics
- Cannot delete the project or manage billing
Tech Lead
- Create and edit technical requirements
- Approve or reject technical implementations
- Manage test cases and test results
- Configure integrations with development tools
- Cannot manage billing or delete the project
Developer
- View all requirements
- Create and edit technical requirements
- Link code implementations to requirements
- Mark requirements as implemented
- Cannot approve high-level requirements
Tester
- View all requirements
- Create and edit test cases
- Record test results
- Link tests to requirements
- Cannot modify requirements
Outsider
- View requirements (read-only)
- View test results (read-only)
- Cannot create or modify any content
- Cannot access sensitive project settings
No Access
- Cannot view or access the project in any way
- Will not see the project in their project list
Best Practices for Team Management
Assign Appropriate Roles: Give team members the minimum permissions they need to do their job effectively.
Regular Audits: Periodically review your team list to ensure all members still require access.
Onboarding Process: Create a standardized process for adding new team members and introducing them to your project structure.
Documentation: Maintain clear documentation about who is responsible for different aspects of the project.
Role Transitions: When team members change responsibilities, update their roles promptly to maintain proper access control.