BuildAccess starts with an account.
BuildAria supports email and password authentication, alongside Google and Microsoft sign-in. Password authentication uses hashed passwords rather than storing them in plain text.
Your business deserves
a considered foundation.
Construction records carry commercial and personal information. Access to that information should follow the people and the work it belongs to.
A boundary around each business.
Company context and separate tenant schemas keep business records organised by workspace. Application permissions govern access to modules and actions.
Connections with a purpose.
Connecting a mailbox is a separate action from signing in. The email integration protects stored connection credentials with encryption and uses provider permissions for the connected service.
SHARED RESPONSIBILITYGood habits belong
Good habits belong
in every workspace.
Keep access appropriate as your team and projects change.
- Give each person their own account and the access their role needs.
- Keep your email provider account secure and review connected applications.
- Check recipients and permissions before sharing project documents.
- Review AI drafts and recommendations before using them in a customer or project decision.
For information about collection, use and retention of personal information, read our Privacy Policy.
SECURITY QUESTIONSLet’s discuss what
Let’s discuss what
your business needs.
Ask us about your security requirements, access controls or data handling before introducing BuildAria to your team.
If you think you have found a security issue, contact support privately with the affected page and steps to reproduce it. Please leave passwords, tokens and customer records out of your initial message.
LET’S TALK
Email the team ↗A question about security?
Get in touch about a requirement or report a concern directly to our team.