TruBuild uses three access layers:Documentation Index
Fetch the complete documentation index at: https://docs.trubuild.io/llms.txt
Use this file to discover all available pages before exploring further.
- Organization roles control account-level administration.
- Project roles control broad access to a tender program.
- Package roles control access to a specific tender package.
Organization roles
Organization roles are intentionally small and stable.| Role | Typical user | Can do |
|---|---|---|
owner | Account owner, procurement director, system owner | Full organization administration, member management, admin areas, project access |
admin | System admin, procurement administrator | Organization administration and workspace setup, depending on rollout policy |
member | Normal enterprise user | Access only to projects and packages where they are granted a role |
Enterprise feature access is also controlled at organization level. The implemented feature slugs are
commercial_eval, technical_eval, tender_queries, vendor_db, and ai_chat.Project roles
Project roles are useful when a user needs visibility across a full tender program.| Role | Access level | Typical user | Best for |
|---|---|---|---|
project_lead | Full | Procurement manager, project procurement lead | Creating packages, coordinating teams, reviewing all package data |
commercial_lead | Commercial | Commercial manager, senior QS | Commercial workflows across packages in the project |
technical_lead | Technical | Technical director, engineering manager | Technical workflows across packages in the project |
project_viewer | Viewer | Owner representative, steering committee member | Read-only project visibility |
Package roles
Package roles are the safest default for large enterprise tenders because they scope access to one package.| Role | Access level | Typical user | Best for |
|---|---|---|---|
package_lead | Full | Package manager, procurement lead | Running a specific package end to end |
commercial_team | Commercial | QS, cost consultant, commercial evaluator | BOQ uploads, commercial rounds, pricing review, commercial PTCs |
technical_team | Technical | Discipline evaluator, owner engineer | Technical proposal review, criteria scoring, technical PTCs |
package_viewer | Viewer | Owner reviewer, advisor, award committee reviewer | Read-only package review |
Access levels
TruBuild derives an access level from the user’s highest relevant role.| Access level | What it means |
|---|---|
full | Can manage the project or package and work across commercial and technical areas |
commercial | Can view and work with commercial evaluation areas |
technical | Can view and work with technical evaluation areas |
viewer | Can view permitted package/project data without making evaluation changes |
none | No access to that project or package |
Recommended enterprise assignments
| Person or team | Organization role | Project role | Package role |
|---|---|---|---|
| Procurement director | owner or admin | Optional project_viewer | Optional package_viewer |
| Project procurement manager | member | project_lead | package_lead on high-risk packages |
| Package manager | member | Optional | package_lead |
| Commercial lead | member | commercial_lead if cross-project | commercial_team |
| Commercial evaluator / QS | member | Optional | commercial_team |
| Technical lead | member | technical_lead if cross-project | technical_team |
| Discipline evaluator | member | Optional | technical_team |
| Owner reviewer | member | project_viewer | package_viewer |
| External advisor | member | Avoid unless necessary | Package-scoped role only |
Separation of duties
For owner-led or highly regulated procurement, use these controls:- Keep commercial evaluators on
commercial_team. - Keep technical evaluators on
technical_team. - Give the procurement manager
package_leadorproject_lead. - Give owner representatives
vieweraccess until review meetings require escalation. - Scope external consultants to the package they support.
- Avoid broad project roles for people who only need one package.
Practical examples
- Owner-led tender
- Main contractor package tender
- External advisor
| User | Role setup |
|---|---|
| Owner procurement lead | project_lead |
| Owner technical reviewer | technical_lead or technical_team |
| Cost consultant | commercial_team on assigned packages |
| Legal advisor | package_viewer for tender instructions, qualifications, and award evidence |
| Steering committee | project_viewer or package_viewer |
Permission guidance by workflow
| Workflow | Full access | Commercial access | Technical access | Viewer |
|---|---|---|---|---|
| Package setup and award | Manage | Limited by UI policy | Limited by UI policy | View |
| Commercial evaluation | Manage and review | Manage and review | No commercial write access | View where permitted |
| Technical evaluation | Manage and review | No technical write access | Manage and review | View where permitted |
| Tender queries | Coordinate package queries | Work on commercial queries | Work on technical queries | View |
| AI chat | Project/package scoped | Commercial context where granted | Technical context where granted | Read-only context where granted |
Access review checklist
Before a tender starts
Before a tender starts
- Confirm every package has a
package_lead. - Add commercial and technical users only to the packages they support.
- Grant owner reviewers viewer access where they need oversight.
- Confirm the organization has the right feature entitlements.
Before evaluation starts
Before evaluation starts
- Remove users who helped with bid preparation but should not score.
- Confirm commercial and technical evaluator lists match the approved evaluation plan.
- Confirm external advisors are not over-scoped.
Before award
Before award
- Confirm reviewers can view the award record.
- Confirm only authorized procurement leads can record the award decision.
- Remove temporary external users after their review is complete.
Related
Enterprise rollout
Design the rollout and team model.
Evaluation governance
Apply controls during commercial and technical evaluation.