Every TruBuild user belongs to an organization. The organization owns projects, packages, members, feature entitlements, and enterprise configuration. For procurement teams, the most important setup decision is not visual branding. It is access design: who can administer the account, who can lead a project, who can work on commercial evaluation, who can work on technical evaluation, and who can only review.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.
1. Create your organization
Open TruBuild
Go to app.trubuild.io or the dedicated regional URL provided for your organization.
Sign in with your corporate identity
Use your corporate email. Enterprise workspaces may use SSO depending on your organization’s configuration.
2. Assign organization administrators
Use organization roles sparingly:| Role | Assign to | Notes |
|---|---|---|
owner | Account owner or procurement systems owner | Keep this group small |
admin | Procurement administrator or IT admin | Use for day-to-day member and workspace setup |
member | Everyone else | Project and package roles grant actual tender access |
3. Confirm feature entitlements
Feature access is granted at organization level. Your administrator can confirm which modules are enabled:| Feature slug | Module |
|---|---|
commercial_eval | Commercial evaluation |
technical_eval | Technical evaluation |
tender_queries | Tender query management |
vendor_db | Vendor database |
ai_chat | AI chat |
4. Invite the project team
For the first tender rollout, invite a small cross-functional group:| Person | Organization role | Project or package role |
|---|---|---|
| Procurement manager | member | project_lead |
| Package buyer | member | package_lead |
| Commercial lead / QS | member | commercial_team or commercial_lead |
| Technical lead / discipline evaluator | member | technical_team or technical_lead |
| Owner reviewer | member | project_viewer or package_viewer |
| External advisor | member | Package-scoped role only |
5. Create the first project
Create a real project that represents a tender program, development, or capital project. Set:- Project name
- Country
- Initial project lead
- Viewer access for owner-side reviewers if required
- Package name
- Currency
- Technical/commercial weighting
- At least two contractors
6. Prepare SSO and regional controls
Enterprise workspaces may include:- SAML or OIDC single sign-on
- Domain-based provisioning
- Region-specific URLs
- Dedicated infrastructure
- Feature entitlements by organization
Checklist
Organization
Organization
- Owner and admin users are confirmed.
- Feature entitlements are correct.
- SSO or corporate login path is tested if applicable.
First project
First project
- Project lead is assigned.
- Owner reviewers have viewer access where needed.
- At least one real package is created.
First package
First package
- Package currency is correct.
- Technical/commercial weighting matches the approved tender strategy.
- Contractor list is complete enough to begin uploads.
- Commercial and technical teams are scoped correctly.
Next
Enterprise rollout
Plan the full rollout model across projects and packages.
Document standards
Prepare tender files before the first commercial or technical round.