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. Max is included on paid plans; on the Free plan, every role uses Standard.
| 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.
- Heavy work is Max-only: timeline rewrites and what-if capacity plans, dependency fixes, generated files (decks, spreadsheets, PDFs) and document revisions. Timeline analysis and document creation work on both tiers, for the roles that include them.
- If a capability isn't explicitly granted, it's denied. Unknown or unrecognised actions fail safe rather than slipping through.
The Associate can't exceed you
The simplest way to think about it: the Associate is you, with help. It can do the things your role permits, and nothing it proposes can give you access you didn't already have.
Where your data goes
On Alesko Std, all of the Associate's AI processing runs on AWS infrastructure hosted in Australia. Your project data is processed and stored within Australia, which keeps your information inside the country to meet Australian data-residency requirements and supports compliance controls such as SOC 2.
Alesko Max is powered by Anthropic, so prompts sent with Max may be processed outside Australia; your stored project data stays in Australia either way. The model picker shows this before you choose Max.
Choose Std to keep processing onshore
If a conversation needs to stay in Australia, use Alesko Std. We're in open beta — over time we plan to host models ourselves and bring Max onshore too.¹
¹ During open beta, application logs and error traces are processed by Pydantic Logfire, a third-party observability service whose servers may be located outside Australia.
Next
Last updated: 2026-09-30