Settings · make the numbers yours

Every seat dollar in your reports uses $30 a seat until you set your real price.

Your Copilot seat price

What you pay Microsoft per seat per month, from your order form.

assumption until saved

Who may see the organization's numbers

Sponsors see every report. Everyone else sees only their own page.

When you save, every seat dollar in the three reports and the Traffic Lights is re-priced the same minute, and the "assumption" marks turn into "counted". Reports already frozen, decks already exported and cards already delivered keep the figures they were made with.

4 of 12 dials set by your organization

counted from your saved settings

Seat price — default Cowork budget — set Budget enforcement — set Measured billing — default Renewal date — set Still-need survey — default Adoption goal — default Sponsors — set Prod approvers — default Advisor access — default AI model — default Brand — default

set by your organization 4still the platform default 8

2 sponsors and the Entra leader role can open everything; no advisor has access.

Team visibilityDepartment heads see their champions by name, and every person may opt out. Contoso's leaders chose this. A person who opted out is counted and never named. Teams below five people are merged, as everywhere in Aristo. · Team visibility

Who holds each authority, what it can do and what it cannot
Authority	Who holds it	Can	Cannot
Leader	your Entra app role (Leader or Sponsor), or the Entra group you named as leaders	Open every page, set the seat price and budgets, pause outreach, decide proposals and requests	Approve a request they raised themselves
Sponsor	2 sponsors · you and the CFO's office	Everything a leader can — the list is a second door to the same authority	Approve a request they raised themselves
Advisor you name	no advisor has access	Read the pages the grant covers, until it ends; it writes nothing	Change any setting, or see anything after the grant ends or is revoked
Department owner or approver	named on each department’s budget (Budgets & requests)	Decide their own department’s requests; see their department’s page	See the whole organization’s money
Maker	anyone who builds an agent or a skill	Nothing more than before — making something is credit, not access	Open a page or change a setting because they built something
PhoenixHalo (the platform operator)	the vendor, not your organization	Run the platform: registration, the module switches, the rollback	Be granted or removed from here — it is the vendor’s own access
Everyone else	a work account with none of the above	Their own page, and asking for access	Open any page that carries the organization’s money

This is the illustrative organization, so nothing here is saved — in your own tenant each of these saves right here, in place, and the History tab keeps who changed it and when.

👑 Sponsors — who sees the org numbers

The leaders your admin has named. Only sponsors see Strategy, Money and Proof; everyone else sees only their own page. One email address per line.

2 named today — you, the CFO's office. Type the full list to replace it; leave the box empty and nothing changes.

✍️ Who may approve an agent for Prod

Promotion to Prod needs a passing assay and a fresh human approval. Choose where you administer who can give it. Whoever forged an agent can never approve it — that holds in both models and is not a setting. Until you choose one, no agent can be promoted to Prod: Aristo will not hand this authority to everyone by default.

Authority model A named list, kept hereYou maintain the approvers in Aristo. An Entra security groupYou maintain them in Entra, where you already administer access. Membership is the authority.

👥 Team visibility

Department heads see their champions by name, and every person may opt out. Contoso's leaders chose this.

A person who opted out is counted and never named. Teams below five people are merged, as everywhere in Aristo.

🤝 Microsoft seller notify (opt-in)

Optionally let your Microsoft account team see when your org crosses 90% of the funded Cowork budget — a natural moment for a fund / seat / renewal conversation. Consent-first: nothing is shared unless you name a contact and check the box. Org-level aggregate only — never any individual’s numbers, measured spend only.

I consent to notify this contact at 90%

No contact is named, so nothing is ever sent outside your organization.

🔑 Advisor access — a Microsoft seller or a partner you name

Name an advisor by work email who may read this account’s aggregate report. Read-only, k-anonymous (five or more), 90 days by default and one-click revocable — a strict subset of the illustrative organization’s leader view, and it stops the moment you revoke. Nothing is shared until you grant it here.

No advisors have access yet.

Service desk

The Service Desk Agent is not switched on for this sample company.

Not connected

Not connected. Answers stay in Teams. When you need more help, Aristo gives you filled-in text to submit in your service desk.

What you would enter: your ServiceNow instance address and a ServiceNow user sign-in or OAuth client details.

Does Aristo keep a copy of your tickets? No. Tickets stay in ServiceNow. Aristo keeps its request record, including the person's words and the answer and context shown, who asked and where, the ticket number and identifier, and state and update markers. Each person gets the ServiceNow number and that ticket's updates in Teams.

Aristo can only open new tickets - never edit or close them. Take this back here at any time.

This is the illustrative organization — it is never written to, so there is nothing here to set. In your own tenant this control writes the same field the classic settings screen writes, records the same audit action, and every surface that reads the setting moves with it.

For administrators: how this page behaves Four rules and three read-only switches

Your Azure OpenAI key is checked with one live call before it is saved, sealed, and never shown again — only its last characters are displayed.
Every change is confirmed by reading the saved value back, so what you see after saving is what is in effect, and refreshing the page cannot repeat a change.
When a control may not be used, the page says so in words rather than hiding it; the illustrative organization is read-only and says what each control would do in your tenant.
There is no filter, export or loading state here: the list is short, the export is the change history, and every value is on the page before it reaches you.

Availability and rollback

Three switches, none of them yours to flip from this page.

Scroll sideways for the remaining columns.

The three availability switches, their current state, and who holds each one. All read-only on this page.
Switch	State	What it does and who holds it
These pages	On	Switched on in the deployment; switching them off removes them entirely rather than hiding them behind a message.
Platform-wide rollback	Lifted	A fleet-wide switch, held by the Aristo operator, that returns every organization to the previous report generation.
This organization's report generation	Following the platform default	A per-organization pin set at your organization's request; unset means you follow the platform default.