Give project, analysis, verification and delivery staff the records they need.
Project Manager owns project context and baseline decisions; Business Analyst owns requirement detail.
Team Member needs assigned item and time-entry access; QA Engineer needs verification findings and supporting evidence.
Delivery Lead and Admin need access to failed operation receipts so a rejected action can be investigated.
Record attachments can be internal or shared; check visibility with a real file before the operating cycle begins.
| Role | Project context | Requirement register | Requirement items | Baselines and acceptance | Verification and change | Time and evidence |
|---|---|---|---|---|---|---|
| Admin | Edit | Edit | Edit | Edit | Edit | Edit |
| Delivery Lead | Edit | Edit | Edit | Approve | Edit | Edit |
| Project Manager | Edit | Edit | Edit | Approve | Edit | Edit |
| Business Analyst | View | Edit | Edit | Edit | Edit | Edit |
| QA Engineer | View | View | View | Edit | Edit | Edit |
| Team Member | View | View | Edit | View | View | Edit |
Maintains user access, reference records and the operating setup.
Oversees project scope, baseline decisions and delivery exceptions.
Starts on: Baselines Awaiting Approval
Owns project planning and reviews submitted baselines and delivery time.
Starts on: Baselines Awaiting Approval
Maintains requirement revisions, acceptance detail and baseline submissions.
Starts on: Baselines Awaiting Approval
Records verification findings and checks acceptance evidence.
Starts on: Open Verification Findings
Works assigned requirement items and submits delivery time.
Starts on: Requirement Items In Flight
Start free, then use Proto to change fields, steps and approvals before your team goes live.