Your Microsoft 365. Your data. Your record.

Bunya Command Centre is built inside your firm’s own Microsoft 365 tenancy. This page sets out plainly how access, records, AI and ownership are handled, and what we don’t claim.

Written for principals, licensees and anyone doing due diligence. The controls below are Microsoft 365 features; which ones apply, and how, is agreed for your firm in its solution design.

Book a demo
Record history · Example FamilyIllustrative example
  1. 17 Jun · Super statements uploadedJordan Example, client services · filed to the client folder
    Filed
  2. 18 Jun · SoA request pack preparedBy the SoA request workflow
    AI-prepared
  3. 18 Jun · Two fact-find fields changedAlex Example, adviser · corrected before approval
    Changed by Alex
  4. 18 Jun · SoA request pack approvedAlex Example, adviser · ready for paraplanning
    Approved · 10:42

01 · Your tenancy

Built in your tenancy. Run under your administration.

Command Centre is built inside your firm’s own Microsoft 365 tenancy. Client records, documents and approvals stay in your environment, under your firm’s Microsoft administration.

How delivery works ↗

Records

Client and advice records are held in Microsoft Dataverse in your tenancy.

Documents

Files and conversation records are kept in SharePoint in your tenancy, with the client they belong to.

Administration

Microsoft licences and administration stay with your firm, as part of the agreed cost picture.

02 · Access control

The right people. The right records.

Access is agreed for your firm, configured, and tested with your people before go-live.

By role

Permissions set by role, so advisers, paraplanners and client services see what their work needs.

By team

Access can be limited to a team or business unit.

By record

Individual records can be restricted to the people working on them.

By field

Sensitive fields can be hidden or locked for roles that don’t need them.

Sign-in

People sign in with their Microsoft 365 accounts, not a separate Bunya password.

MFA & conditional access

Your Microsoft multi-factor authentication and conditional access policies apply.

03 · Audit trail

Who changed what. And when.

Changes to client records can be audited with who made them and when, and approvals are kept with the record they belong to. Which records are audited is agreed for your firm. The record history at the top of this page is an example.

With file notes and approvals kept on the client record, the evidence is already there when someone asks what was done.

See compliance & evidence ↗

04 · AI with guardrails

AI prepares the work. People make the calls.

A clickthrough is never advice approval. Advisers keep the strategy and product judgement.

See how AI workflows work ↗

Human approval gate

AI-prepared work waits for a person before it is used or actioned. A person on your team approves it before it moves on.

Labelled

Work prepared by an AI workflow is marked as AI-prepared, so reviewers know what they are checking.

Recorded

AI usage can be recorded with the client record. Your scope defines which events are recorded, who can see them and how long they are kept.

Scoped

Each AI workflow uses only the information agreed for it, within the permissions of the person running it.

05 · Residency & backups

Residency, backups and testing. Confirmed in your design.

Each of these is confirmed for your firm as part of the solution design.

Residency

Client data stays in the Microsoft region of your own tenancy, confirmed with you in the solution design.

Backups

Backup and restore for your environment are set out in your solution design.

Releases

Changes are built and tested before they reach the environment your team works in.

06 · Ownership & handover

Your agreement sets the rights. And the handover.

Your agreement defines the delivered components, documentation, rights and handover. Microsoft licences, usage and ongoing services remain part of the cost picture.

How getting started works ↗

07 · What we don’t claim

Few claims. Each one confirmed.

Diligence is easier when the claims are few and true. Here is what you won’t find us saying.

  • No certifications listed yet

    We don’t list security certifications or independent audits until they are confirmed.

  • Software doesn’t do your compliance

    Compliance stays with your licensee and your people. Command Centre keeps the evidence of what was done.

  • AI isn’t always right

    That is why every AI-prepared item is checked by a person before it is used.

  • No connection is live until it is

    Specialist tools are connected by agreement, and only once tested for your firm.

Questions

Security and data questions. Straight answers.

01Where is our client data stored?
In your firm’s own Microsoft 365 environment. Structured records in Dataverse and documents in SharePoint. Data location, retention and any connected AI or third-party processing are reviewed as part of the solution design.
02Can Bunya’s team see our client data?
Access for Bunya’s team is agreed with your firm and used only for the work you ask us to do.
03Is our data used to train AI models?
The AI services used, and their data-use terms, are reviewed with your firm as part of the solution design.
04Can different team members have different access?
Yes. Access rules are agreed for your firm, then configured and tested before go-live.
05What happens if we stop working with Bunya?
Your agreement defines the delivered components, documentation, rights and handover.
06Can we run our own security review?
Yes. Bring your questions to the demo, or send them ahead to info@bunya.ai.

Read all FAQs ↗

Your tenancy Access control Audit trail Human approval MFA Backups Data residency Handover Licensees Due diligence

Ask us anything about your data.

Book a demo

One meeting covers the demo and your questions. You can also send them ahead to info@bunya.ai.

Optional add-onBunya Voice →