Skip to main content
Every TruBuild user belongs to an organization. The organization owns projects, packages, members, feature modules, and enterprise sign-in policy. 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. Get this right before the first tender package, not during it.

​
1. Sign in for the first time

TruBuild uses passwordless sign-in. There is no password to create, share, or rotate.
1

Open TruBuild

Go to app.trubuild.io. Enter your corporate email in the Email address field and click Continue.
2

Check your inbox

TruBuild emails you a sign-in link. Open it within 10 minutes; after that it expires and you need a fresh one.
3

Resend if needed

If the email does not arrive, use Resend Link on the login page. The button shows a 30-second countdown before you can send again. Check spam filters if links never arrive; corporate mail gateways sometimes quarantine them.
If your organization enforces single sign-on, the login page sends you to your company identity provider instead of emailing a link. Sign in there with your normal corporate credentials.

​
2. Create your organization

If you sign in and do not belong to any organization yet, TruBuild takes you to the Create Organization page.
1

Name the organization

Enter the organization name. Use the legal entity or business-unit name that appears in your procurement reporting, so exports and audit records match your internal documents.
2

Select the country

Choose your country from the dropdown. This becomes the default country for new projects and drives regional defaults such as suggested package currency.
3

Create it

Click Create Organization. You become the organization Owner and land on the Overview dashboard.
If your company already uses TruBuild, do not create a second organization. Ask an existing Owner or Admin to invite you instead. Duplicate organizations split projects, members, and evaluation history.

​
3. Assign organization administrators

Use organization roles sparingly: Only Owners and Admins can create projects, manage members, and change organization settings.
Do not use organization ownership as a shortcut for tender access. Owners and Admins see everything, including both commercial and technical data. Most evaluators should be Member at organization level and scoped through project or package roles, which is also what separation-of-duties reviews expect.

​
4. Confirm which modules are enabled

Feature modules are enabled at organization level. If a module is not enabled for your organization, its pages and navigation items do not appear at all. If a page is missing for users who already have project or package access, check which modules are enabled before debugging roles. Contact TruBuild support to change them.

​
5. Invite the project team

Invite people from Settings in the sidebar, under the Members section.
1

Send invitations

Enter each person’s email, choose an organization role (Owner, Admin, or Member), and click Send Invite.
2

Track pending invitations

Pending invitations list the email, inviter, and role. You can resend the invitation email or cancel an invite that is no longer needed.
3

Scope tender access

After people join, grant project or package roles so each person sees only the evaluation data they should.
For the first tender rollout, invite a small cross-functional group: See Roles & permissions for the full model.

​
6. Create the first project and package

Only organization Owners and Admins can create projects. Create a real project that represents a tender program, development, or capital project.
1

Create the project

Click Create Project. Enter the project name, then confirm the project country. The country defaults to your organization’s country and drives regional defaults for the project’s packages.
2

Create the first package

From the project, add a package. Set the package name and currency, then use the slider to set the technical weight. The commercial weight adjusts automatically so the two always total 100%.
3

Add contractors

Add the bidders: search the vendor database with Search Existing, or use Add New to enter contractor names manually. Add at least two so comparison and bid leveling have something to compare.
Set the technical/commercial weighting to match the split approved in your tender strategy or evaluation plan before any submissions are scored. Changing weights mid-evaluation invites challenge from bidders and auditors.
For a full pilot path through commercial, technical, and query workflows, see Run your first package.

​
Sign-in security

TruBuild applies account security controls automatically. Knowing them saves support tickets during rollout.
Sessions end after 15 minutes of inactivity by default. You see “You were signed out after 15 minutes of inactivity.” on the login page. Sign in again to continue; no work is lost from completed actions.
Three failed sign-in attempts temporarily lock the account. Wait a few minutes and try again, or contact your administrator.
Organizations can require single sign-on, multi-factor authentication, or both. If your organization requires SSO, email links are blocked and you must sign in through your company identity provider. If MFA is required, complete the MFA step with your identity provider and try again.

​
Enterprise sign-in controls

For enterprise workspaces, coordinate the following with TruBuild support and your internal identity team before a large rollout:
  • Single sign-on through your corporate identity provider
  • Enforced SSO (blocks email-link sign-in for the whole organization)
  • Enforced multi-factor authentication at the identity provider
  • Member seat limits for the organization
Test the sign-in path with a small group before inviting the wider evaluation team.

​
Checklist

  • Owner and Admin users are confirmed and kept to a small group.
  • The enabled modules match what your teams expect.
  • SSO or the email-link sign-in path is tested if applicable.
  • Invitations are sent and pending invites are tracked.
  • Evaluators are Member at organization level.
  • Project and package roles separate commercial and technical access.
  • Project name and country are set.
  • Package currency is correct for the tender.
  • Technical/commercial weighting matches the approved tender strategy.
  • At least two contractors are added so comparison is meaningful.

​
Next

Enterprise rollout

Plan the full rollout model across projects and packages.

Document standards

Prepare tender files before the first commercial or technical round.