Admin console

Visible across every page in the app.

Pick a primary and secondary colour for this tenant. Live preview applies immediately. Save to persist.

What appears on the home Recent activity card.

Just the host: https://my123456.sapbydesign.com. Most tenants only need the shared base URL. Per-module overrides exist for split prod/test routing — leave blank to fall back to the base URL.

Single Entra app registration shared across every module that sends or reads email — supplier-reply drafts (Invoices), AR Copy-Invoice replies, and Expense email submission. Needs Mail.Send + Mail.ReadWrite (admin-consented).

Persistent storage shared across Invoices (raw + processed PDFs), Chat (uploads + AI-generated files) and Expenses (receipts). Containers are auto-created on first use. Blank connection string = local disk only (lost on redeploy).

Each module's mailbox is configured on its own settings page (Configure → from the Modules tab). The Microsoft Graph credentials above authorise every mailbox.

Limits for both user uploads and AI-generated files.

Tenant-specific lore appended to every chat prompt. company codes, naming quirks, internal terms. Keep it short.

Behaviour of the Dashboards module.

Map each company code to its own intercompany GL account. The engine derives the company pairs from this.

SAP analytics filters used to pull the cash-ledger and trial-balance snapshots.

Where the agent reads from and how it replies.

Subject and body the agent uses when replying. Placeholders are replaced server-side.

Restrict which senders the agent will reply to.

SAP ByD has no standard service for expense report creation, so each tenant builds a custom development that exposes one. Until the endpoint is configured, submitted expenses stay in prepared state with the payload saved on the record. Authentication uses the tenant's main SAP credentials (sap_username / sap_password). no separate auth needed.

Routes expense reports through manager review before they hit SAP. With approval on, a Submit click flips the report to pending_approval and emails the assigned approver instead of posting straight to SAP — the approver clicks Approve to release it. Users with the expenses:bypass_approval permission (typically finance) skip approval entirely.

Soft warnings shown on the receipt review screen and rolled up on the report submission modal. v1 covers per-category amount caps, receipt-required-above thresholds, and duplicate detection (same merchant + amount within ±N days). Rules are advisory — they never block a submission. Hard-block rules will land with the approval workflow.

Used when an employee picks "Claim mileage instead" on the upload page. The total is computed as distance × rate; the resulting expense item lands in their My Receipts list alongside scanned receipts. UK HMRC default for cars is 0.45 GBP/mile up to the first 10,000 miles in a tax year; tiered rates aren't surfaced in v1 — set the dominant rate.

Let employees submit receipts by emailing them to a shared mailbox. A Logic App / Power Automate flow forwards each email to the endpoint below; matched senders are auto-bound to their SAP employee, unmatched senders land in an admin queue (status=needs_assignment) for re-assignment.

Pick which SAP data sources this tenant's chat and dashboards can read. Per-entity customisations are preserved across toggles.

Microsoft Entra ID SSO. Three values from the customer's Entra app registration. See the setup guide.

Control concurrent sessions and multi-factor authentication policy for this tenant.

What the chat actually sees for the signed-in user. opted-in entities, role-trimmed list, resolvable URLs, active SAP base. Run when chat reports too few sources.

Pings ClamAV, reports the signature DB version, and runs an EICAR end-to-end test. All three must be green or every upload is blocked (unless security.malware_fail_open=true).