The inventory, not the pitch.

Kanban columns you configure, drag ordering, labels, comments and @mentions that notify.

Milestones, members and comments, read back with tasks, quotes and time actuals in one call.

Risks with treatments and comments, maintained by a dedicated agent.

Month, week, day and list views over organisation events.

An editable visual structure backed by a node tree.

A scheduled scan that notifies on tasks, risks and quotes coming due or already overdue.

In-app notifications with per-event and per-channel settings, and a delivery log.

A read-only mirror of Xero invoices and payments, with an ageing view of who owes what.

Needs: Xero

Spend logged against categories and jobs, with a summary. Agents may record spend, never authorise it.

Hours from the tracker you already run, by CSV, authenticated push endpoint or scheduled pull.

Resolves an external tracker's names and IDs onto YumaOS users so hours land on the right person.

Cost and charge rates per person or role, which is what turns imported hours into job cost.

Estimated model cost by agent, model and channel, with a hard cap and alert thresholds.

Templates, segments, recipient lists, scheduling and sending through your configured provider.

Needs: Email provider and a reachable URL

Per-recipient engagement events surfaced as campaign analytics.

Needs: Tracking secret

Signed one-click unsubscribe, a suppression list and consent records. An unanswerable do-not-contact check reads as suppressed.

Needs: Unsubscribe secret

Ingests delivery events from Resend, Azure Communication Services or SES.

Outbound SMS through Twilio, AWS End User Messaging or Azure Communication Services, plus inbound replies.

Needs: SMS provider

Per-campaign assets placed by a placeholder and soft-deleted only, so a sent campaign never breaks.

Renders a template preview with the organisation's branding applied.

Draft, review, approve and publish to connected channels, with every per-target attempt recorded.

Needs: Buffer

Ops, Risk, Docs, Quote, an intent router, and assistants in Slack and Teams, each with its own instructions and tool scope.

One registry serving dashboard chat, the REST API and MCP. Every tool resolves the acting user first.

A panel mounted once in the shell, opened by keyboard shortcut, that knows which of 22 scopes it is in and narrows its tools accordingly.

Destructive calls become rows a human answers while the agent keeps working. Five actions that reach a third party stop the run instead.

Needs: Cannot be disabled

An approver pre-authorises a narrow class of action. The rule can never apply to something the policy marked never-auto.

Queued actions announced in-app, by email for the five blocking ones, with a chase after twelve hours. Notification never decides anything.

Agents pass work through the task record with a hop budget and audit events, so a chain is readable afterwards.

Per-agent instructions, model and allowed tools stored in the database and edited in Settings rather than deployed.

Reusable playbooks an agent can be pointed at, enabled per agent.

Step-by-step record of a run, with sensitive values filtered out of the spans.

Tools answer with a chart, table, metric or diff instead of a wall of JSON.

Resource-scoped working memory, thread-scoped observational memory, and semantic recall across threads.

Needs: Embeddings for recall

Moderation, PII detection and prompt-injection detection where untrusted text reaches an agent, with violations audited.

Needs: Switched on by configuration

A ChatGPT or Codex subscription over OAuth, an OpenAI platform key, Anthropic, or AWS Bedrock, resolved per request.

A thread sidebar with deep links and deletion, recalling beyond the model's context window.

Sessions with self-registration switchable off for a deployed-per-client install.

Sign in with Microsoft, with Entra group to role mapping and a user link table.

Needs: Entra app registration

TOTP with backup codes. Enabling writes an unverified factor until a code is entered, so nobody locks themselves out against a secret they never typed.

WebAuthn with a pinned relying-party ID, and a refusal to issue passkeys against an IP literal or plain HTTP rather than binding them to a name that will break.

Clears another person's factors, revokes their live sessions, and is audited under the administrator's name. Its own permission, not implied by user administration.

Fifty named permissions, two tiers, custom roles, and per-person grants and denies resolved at request time.

Users and Groups endpoints with discovery, filtering, bearer tokens and rate limiting.

Needs: Identity provider

Invite people by email and set their tier.