Add a Finance Manager or a Marketing Assistant, read its report, and keep the Our business page right

A Finance Manager or a Marketing Assistant is a role on your team in Sasha. Set it up from Apps, read its report and email, and correct the Our business page.

Where

Apps in the side menu. A role that is not added yet shows Set up next to its name. After setup, the role opens like any other app, in a panel on the right.

Who

Only an admin adds a role, changes its Settings and what it may read, and saves a Review. Admin and staff users press Run now. People who may edit the Company project change the Our business page.

Needs

A working AI provider, an email sender on your Sasha, and a read-only connection for each source the role needs (for a Finance Manager, at least your cloud bill).

What it is

Sasha can add digital team members. Each one looks after one part of your business and works from what Sasha already knows about you. Two roles are available:

A Finance Manager reports monthly by default. A Marketing Assistant reports weekly by default. Each one sends one short email after each run and has its own page in Sasha.

The example on this page is Northwind Advisory, a small consultancy with two products, Advisory and Training.

This page tells you how to add a role, what each tab shows, how shared costs are split and what the email says. The details of the tabs are for the Finance Manager; the Marketing Assistant has the same tabs, plus Tagged links.

Add a role

1. Open Apps in the side menu. Business apps and roles come first. Starter apps, such as Time Sheet Entry, are under Examples.
2. As an admin, click a role with Set up next to its name, for example Finance Manager. A panel says what it does, Questions it answers and What it needs.
3. Click Set it up. Sasha puts "Set up our Finance Manager." in the chat box. Press Send.
4. Sasha reads your documents and asks only about the gaps. It writes the Our business page and shows it to you before it saves it.
5. When Sasha wants to save a setting or start a run, a Confirm box opens in the chat. It names the app and says what will change. Press Confirm to let it go ahead, or Decline to stop it. Sasha makes no change until you press Confirm.

You can also start in chat: "Set up our Finance Manager". Only an admin can add a role. A role that is added shows in Apps for everyone with access to it, and the Set up row goes.

Sasha never asks for a key in chat. You add each key in Settings, Tools (Give Sasha's AI more tools, such as web research, analytics or your own MCP servers, and control which tools it may use).

Set up

Until a role is ready, it opens on Set up: three steps, each ticked when it is done.

1. Write the Our business page. Ask Sasha to write it sends the request into the Studio chat. Where the chat cannot take it, the page shows the request to copy.
2. Connect the sources it needs. Each source that is not read yet has a note on how to connect it.
3. Run the first report.

Then the role opens on Report. A person who is not an admin sees the steps and "Ask an admin to set this up."

The tabs

The bar has Report, Improve this, Our business, Settings (admins only) and Help. A Marketing Assistant also has Tagged links. Held items shows on the bar while an item waits. The ⋯ menu has the rest.

Report

Run now builds the report for the current period and sends the email. Admin and staff users can press it.

After a run, the Report tab shows the report:

• The total for the period, and the split by product.
• A table: Product, Direct, Shared share, Full cost, Share %. Direct is the product's own costs. Shared share is its part of the shared costs. Full cost is the two together.
• Every cost line, like a ledger: one row per line, grouped by product, the largest first. A line that a shared-cost rule placed has a … that shows the rule. Tick Show where each figure came from to see the source of each line.
• Under each product, "Shared costs apportioned to" that product lists its part of each shared cost.
• A last Shared group lists each shared cost once, with the reason it is shared on its line, how it is split and its full amount. It says "apportioned to the products above, counted once", so the total does not count a cost twice.

"E" after an amount marks an estimate. Period picks an earlier report.

Improve this

The steps from the latest report. The number on the tab is how many steps wait.

• Warnings: what the last run could not check or read.
• Do these next: at most three things to do, the largest first by money at stake. Each shows what it is worth, who owns it and where its figures came from, for example "From: your AWS bill (2 lines)".
• Make this report better: the steps that make the report more complete.
• What it cannot see yet: one line for each source that was not read.

Each step has a request after "Tell Sasha:". Copy it and paste it into Studio chat. For example: Tell Sasha: "Find our Cloudflare plans in our documents and add them to the Finance Manager."

Our business

Every role reads one page about your business. The tab shows it one line per item. Press Edit to change it, then Save. The next report uses your change. Your save counts as checked, and there is no undo, so check before you save. Only someone who may edit the Company project can change the page.

Below the lists are Notes about the business, and then How costs are assigned and shared. Sasha writes that last section on every save. It says, in order, how each cost line gets its product:

1. The line's own product tag, or its supplier, names a product.
2. Else the line comes from one of your accounts that has a product. A Stripe account takes money for one product, so its card payments and card fees go to that product.
3. Else its tag value is in the tag map.
4. Else the first shared-cost rule whose words are in the line's name decides, until its Until date.
5. Else the line's supplier on the page decides.
6. Else the line has no product, and the report asks you to fix it.

The page is a document, company/our-business.md in the Company project. You can open it there and read it like any other document. When the page cannot be read, for example after a typing mistake, the report runs with its last good copy, and its first step is "Fix line N of the Our business page".

Where your costs come from is on the same tab. It lists the sources to connect for the full picture, each with why Sasha lists it, a request to paste and a folded How. A Marketing Assistant shows Where your figures come from.

Settings

Admins only. Each field has one or two sentences under it on what it does. Help has the same words, field by field.

• Owner of the actions: the person named on each action.
• Who gets the report and Who hears about problems: email addresses, one per line. Only addresses on your organisation's allowed email domains get it. Sasha refuses to save an address that is not allowed.
• Budget per product for one period. A product that spends more becomes a thing to do.
• Costs you enter by hand: costs that no connection reads, such as payroll or insurance.
• Under Advanced: the currency, the size of a change that is listed, how far from its usual size a cost must be to be flagged, the allowed gap between sales and card payments, and problems you already know about.

Your products, suppliers and shared costs are on the Our business tab, not in Settings.

The ⋯ menu

• Trends: costs by product, period by period.
• History: the last run, then every run.
• Review (admins): grade the latest report from A ("right and useful as it is") to D ("wrong or not useful"), and write questions about the figures. The next run answers each question at the top of its email.
• Held items: what the role wanted to do and was not allowed to. Approve or dismiss each one.
• What it may read: the sources, whether the last run read them, and the tools the role may use. Staff can open it. Only an admin can change it.

How shared costs are split

A cost that serves several products goes to shared, for example tax on the whole cloud bill. The report splits each shared cost into the products, by the method in How shared is split:

• Only products with their own costs in the period get a share.
• A product marked Company overhead keeps its own costs and gets no share.
• To give all of a cost to one product, choose that product in Goes to, not shared.
• The parts add up exactly to each shared cost, so the total does not change.

For Northwind, "Load Balancing" goes to shared and is split by requests per product. Until Sasha reads the requests, it is split by what Advisory and Training spend.

The email

Each run sends one email to the people in Who gets the report.

1. When anything is missing, the first line starts "Not complete:", for example "Not complete: Card payments are not connected, so the total is too low." The subject then ends "(not complete)". The report is always sent.
2. The headline: "September 2026 cost: 4,210.00 GBP." Then the full cost per product, with direct and shared parts: "By cost centre: advisory 2,338.89 GBP (2,000.00 direct + 338.89 shared), training 1,871.11 GBP (1,600.00 direct + 271.11 shared)." A line after it says how much is shared and how it is split.
3. Do these next: at most three things to do, each with "Tell Sasha:" and a request to paste.
4. Make this report better: a short list of setup steps, each with a request to paste.
5. More detail: a few more findings.

The email shows no tool names or ids. The app keeps the detail.

Two or more Stripe accounts

A business can take card payments in more than one Stripe account, for example one for each product.

1. In each Stripe account, make a restricted key with read access to Balance, Charges, PaymentIntents, Invoices, Subscriptions, Prices and Products, and None for Customers and everything else.
2. In Sasha, open Settings → Tools → Stripe Billing Workspace and click Add a Stripe account. Type the Account label, for example training. Sasha names the connection stripe-training.
3. Paste the key in Restricted key and click Add Server. Sasha refuses a secret key, because a secret key can change data.
4. On the Our business page, add a row in Accounts for each Stripe account: its account number, Whose Ours, its Product and its Connection (stripe-training).
5. Check in What it may read that the role may read each Stripe connection. If one is missing, tell Sasha "let the Finance Manager read it".

If one account is not read, the report still goes out, marked not complete, with a step "Connect the training Stripe account" and a request to paste. Paste a key only in the connection form, never in a chat. For the connection form, see Give Sasha's AI more tools, such as web research, analytics or your own MCP servers, and control which tools it may use.

Confirm boxes

A person, not the AI, approves each change.

• In Studio chat. When Sasha wants to change a role's setting or start a run, a Confirm box opens in the chat with the app's name and what will change. The change happens only after you press Confirm. Decline stops it.
• Inside a role's page. An admin change (Settings, Review, who gets the report, what it may read, or Resume) opens a Confirm dialog in the Studio window, outside the app. It shows the value now and the new value. Cancel changes nothing. If the app is open outside the Studio window, it says the change needs the Studio window.

When the app will not load

A person with manage access sees ⋯ in the app panel header. Edit raw data opens the app's stored rows. It is for when the app will not load: changes there skip the app's own checks, so use the app itself when you can. Back to app returns to the app. The same view opens by itself when the app fails to start. See Use the apps in your Sasha, understand who can reach them, and know what each bundled app does today.

Limits to know

• Only an admin adds a role. Today the person who runs your Sasha sets the schedule after you approve a test run.
• The Our business page has no undo. Check before you save.
• A split by requests or by use is by spend until Sasha can read those figures.
• Budgets compare a product's own costs, not its full cost.
• Sasha can only send to the email domains that your Sasha allows.