Security by design

Your project data should beprotected by the system itself.

Buildiante is designed around specific security mechanisms: tenant isolation at the database layer, server-enforced permissions, controlled verification workflows, and an audit trail across the project.

Buildiante Security

Organization security controls

Protection active

Security layers

Tenant isolation

Database-level enforcement

Authorization

Server-side permission checks

Verification

Independent approval controls

Audit trail

Traceable project activity

Request authorization

BOQ approval

Estimate #EST-1048

Authorized
UserMichael Carter
RoleProject Manager
ActionApprove estimate
Permissionestimating.approve
Permission verified server-side
Security model

Four layers working together.

Security is not one feature. Buildiante applies multiple controls at different points in the system so one mechanism does not have to carry the entire responsibility.

01

Tenant isolation

Your organization stays separated from every other organization.

Buildiante uses PostgreSQL row-level security to enforce tenant boundaries at the database layer. Tenant isolation does not depend solely on application-level filtering.

02

Server-enforced permissions

Access is determined by role and checked on every request.

The interface can hide actions a user cannot perform, but authorization is enforced on the server. Client-side controls are never treated as the security boundary.

03

Four-eyes verification

Important actions can require independent verification.

Where four-eyes rules apply, the person who performs the original action cannot also complete its verification. The rule is enforced server-side.

04

Audit trail

Important changes leave a traceable history.

Status changes and other auditable actions are recorded with the actor, timestamp, and relevant before-and-after information.

Tenant isolation

Your organization has its own data boundary.

Buildiante is multi-tenant, but tenant separation is not treated as a simple convention in application queries. PostgreSQL row-level security provides an additional database-level enforcement layer.

Every record belongs to an organization context.
Database policies enforce tenant boundaries.
Application-level filtering is not the only protection.
The same isolation model applies across project data.

PostgreSQL

Database security layer

Organization A
Isolated
Organization B
Isolated
Organization C
Isolated
Row-level security enforced
Access control

The browser is not the security boundary.

Users see the actions available to their role, but the real authorization decision happens on the server for every request.

Client-side UI controls improve the experience. Server-side authorization enforces the rule.

RolePrimary access
Owner
Organization-level control
Admin
Administration and configuration
Estimator
Estimating and BOQ workflows
Project Manager
Project planning and coordination
Field Supervisor
Field operations
Audit trail

Know who changed what.

Important project actions can be traced back to the person, time, and change that created them.

Project activity

Riverside Commercial Center

Audit history

BOQ approved

Michael Carter · Estimate #EST-1048

Today · 2:18 PM

Variation submitted

Sarah Mitchell · Variation #VAR-011

Today · 11:42 AM

Punch item verified

Daniel Brooks · Punch #PL-084

Yesterday · 4:26 PM

HSE incident updated

James Wilson · Incident #HSE-019

Yesterday · 1:05 PM
Activity remains associated with the project record
Learn more

Want the implementation details?

Explore how roles, permissions, four-eyes verification, and tenant isolation work in the Buildiante Help Center.

Visit Help Center
Security

Trust the system behind your project data.

See how Buildiante handles project access, tenant isolation, verification, and auditability on your own workflows.