Manage Your Team
Specify supports teams of any size - from a solo evaluator to a full engineering organisation. Roles and permissions control who can do what at both the organisation and project level.
Organisation setup
Your organisation is the top-level container for all projects and team members. When you create an account, you either join an existing organisation or create a new one.
Organisation settings are managed from the organisation page, where you can update the name, manage members, and control access.
Organisation roles
Every team member has an organisation-level role:
Admin - full control. Can manage organisation settings, invite and remove members, create and delete projects, and assign roles. Admins can unlock finalised features.
Manager - can create projects, manage project settings, and invite members. Cannot change organisation-level settings or delete projects.
Member - can access projects they're assigned to, add and edit features, and participate in reviews. Cannot create projects or manage organisation settings.
Viewer - read-only access. Can browse projects and features but cannot make changes. Useful for stakeholders who need visibility without edit access.
Project-level roles
Within each project, members can have specific roles that override their default permissions:
Owner - full control of the project. Can manage settings, assign roles, and finalise features.
Lead - can manage features through all stages, approve features, and assign reviewers. Cannot change project settings.
Contributor - can add and edit features in Plan and Create stages. Can participate in reviews but cannot approve features.
Viewer - read-only access to this specific project.
Inviting team members
Invite members from the organisation settings page. Each invitation includes:
- The member's email address
- Their organisation role (Admin, Manager, Member, or Viewer)
- Which projects they should have access to
Assigning reviewers
During the Review stage, features can be assigned to specific reviewers. The assigned reviewer is responsible for assessing the feature's priority, categorisation, and making the approval decision.
To assign a reviewer, open a nominated feature in the Review stage and select the reviewer from the team member list. The reviewer receives notification that a feature requires their attention.
Reviewer assignment is particularly valuable when different team members have expertise in different system areas - hardware engineers review HW/SW interface features, domain experts review product-specific features.
Permissions overview
| Action | Admin | Manager | Lead | Contributor | Viewer |
|---|---|---|---|---|---|
| Create projects | Yes | Yes | No | No | No |
| Invite members | Yes | Yes | No | No | No |
| Add features | Yes | Yes | Yes | Yes | No |
| Nominate features | Yes | Yes | Yes | Yes | No |
| Approve features | Yes | Yes | Yes | No | No |
| Assign reviewers | Yes | Yes | Yes | No | No |
| Finalise features | Yes | Yes | Yes | No | No |
| Unlock finalised | Yes | No | No | No | No |
| Export | Yes | Yes | Yes | Yes | Yes |
Related
- Capture Features - the Plan stage workflow
- Review & Prioritise - where reviewer assignment happens
Need help? Contact us · Return to home