Permissions & data

The Associate is powerful, but it operates inside the same permission system as the rest of Bluprint — never beyond it. It can't see a workspace you can't see, and it can't make a change you couldn't make yourself.

AI access by role

Your company role decides which model tiers you can use and what the Associate is allowed to do on your behalf:

Role	Model tiers	What the Associate can do	Workspaces
Owner / Admin	Standard + Max	Everything — read, change, plan timelines, generate documents, manage projects	All
Manager	Standard + Max	Read, change, plan timelines, generate documents	All
Member	Standard + Max	Read and make changes (no document generation)	Their workspaces
Viewer	Standard	Read and answer only — no changes	Their workspaces
Guest	Standard	Read and make changes, limited scope	Assigned only
Billing	—	No AI access	—

A few things follow from this:

• Read-only really is read-only. A Viewer can ask the Associate to explain, summarise, and analyse — but it will never change their project.
• Timeline planning and document generation are Max-only, and only for roles that include them.
• If a capability isn't explicitly granted, it's denied. Unknown or unrecognised actions fail safe rather than slipping through.

Where your data goes

All of the Associate's AI processing runs on AWS infrastructure hosted in Australia. Your project data is processed and stored within Australia and is not sent to third-party AI services. That's a deliberate design choice: it keeps your information inside the country to meet Australian data-residency requirements and supports compliance controls such as SOC 2.

Next

• Review & approve
• Roles & Permissions
• How it works