Alliance Business Suite 2.2 has been live in production since October 2. It carries everything from 2.1.2, The Composable Platform, so it's a big one. Here's what changes for you and your team.
Notifications that reach the right people
- You choose how you hear about things. Set your notification preferences per category and per channel. Administrators set what a workspace allows and what members get by default. A setting you can't change shows as locked, with the reason.
- Security and legal notices always reach you. You can't switch those categories off.
- People hear once, from the right event. The Suite works out who needs to know, checks that each person may see what the notification is about, applies their preferences, and then delivers. Someone who qualifies for several reasons gets one notification, and you're not notified about your own actions.
- Administrators can see why someone wasn't notified. Every recipient and channel leaves a recorded decision, so you can answer the question after the fact.
- Notifications arrive in the app and by email.
- Delivery records match what really happened. A notification whose outcome was never confirmed is reconciled and settled.
The right access for every person and every action
- Permissions on every feature and every action. Role-based access control now covers the whole platform, so you decide exactly who can see and do what.
- Approvals are fair and current. Each approver gets one vote at each stage, and an approval is refused if the policy it was granted under changed in the meantime.
Workflows and assistants that work from your data
- AI agents as workflow steps. A workflow can hand a governed AI agent a question or a task and use its answer in later steps. The agent runs under the workflow's own identity, its permissions are checked, and it leaves an audit record.
- Assistants and workflows can search your workspace through the same permission-checked search you use yourself, so they see only what they're allowed to see.
- Assistants that remember. An assistant can remember useful details about the person it's helping and use them in later conversations, so you don't repeat yourself. What it remembers stays private to that assistant and that person, stays inside your workspace, and is governed like every other AI action. An administrator can turn it off for the whole environment.
- See what an assistant did, step by step. Each assistant run keeps its own identity and a record of its steps, so you can read back completed agent work.
- Work runs once, even after an interruption. If a workflow or assistant step pauses for approval or the system restarts, the work isn't repeated.
Your people, organized
- Workforce management. Set up employee types, job titles, schedules, time intervals, and rounding policies in one place.
Money, invoices, and subscriptions you can trust
- New businesses start in their own currency. The currency comes from the business's country, so a business in Colombia starts in pesos. You can change it at any time. Where a country has no single currency, the business starts in US dollars.
- Invoices show when they expire and the effective rate applied. The server works out both figures, so every screen shows the same number, and payments get a matching summary view.
- Subscriptions bill the right person. A subscription identifies its subscriber from the subscribed contact and matches each payment to its own invoice.
- Payments are settled once. Every payment confirmation arrives through one path, with automatic recovery if it's interrupted, so a payment is settled once and consistently.
- Wallet screens show only that wallet's records. When you open a business or contact wallet, you see the records that belong to it.
- Invoices carry the right lines and quantities. Order quantities flow through to invoice lines, and lines from a child order are invoiced once.
- Every accounting entry shows who made it and for whom. When an assistant or an automation posts on behalf of a person, both are recorded and both show when you read the entry back.
Signing and licensing you can verify
- Signing keys that never leave their vault. The Suite can create a key that can't be exported and link it to its certificate, so signing happens in place.
- Signatures name both parties. Every signature and trust record shows who signed and who it was signed for, across all four signing providers.
- Licenses are checked against a trust manifest. If the manifest is missing or unusable, every license is refused, so what you're entitled to is verified, not assumed.
Fewer surprises for administrators
- See and resolve stuck integration messages. Administrators can find messages that got stuck between systems and clear them.
- Emails go out even when a stylesheet can't load.
- The approver inbox lists requests in a fixed order, so nothing jumps around while you work.
- A record keeps its type. Once you create a contact, workforce, or account relation, its type is fixed, so it stays in the lists where you expect to find it.
- Forms protect your data when a record can't load. If a record doesn't load, its edit form won't save, so the record behind it stays intact.
- Clearer answers when something's missing or off. Sign-in guides you to a step your account still needs instead of failing, and health checks report missing configuration as degraded instead of passing quietly.
- The workflow designer runs under a strict browser security policy, so it loads where your organization enforces one.
A cleaner public site
- One address for every page. www addresses redirect to the main address.
- Only published content is public. Public catalog, blog, job, and course pages show only what you've published.
- Invoices and quotes are private. Only the people they were sent to can see them.
Protection for your accounts and your data
- Accounts lock after repeated failed sign-in attempts, on every password sign-in path.
- Sign-in uses the stronger S256 method for proof-key exchange on every app.
- Stored payment methods and bank accounts belong to their wallet. Each is scoped to the wallet that owns it.
- Your workspace stays yours. We hardened workspace isolation across AI agents and skills, point of sale and order lines, Learning, Social, notifications, CRM contacts, system options, and the order and quote viewers in Studio.
- Public pages show only public fields. The public catalog, public pricing, the merchant directory, and the public course catalog show only what a business chose to publish.
- Learning stays private. Confidential learning records stay inside your workspace, and only the holder can read a learning certificate.
- Guest carts stay with their visitor. Cart merging is confined to the visitor's own cart, and cart data no longer stores the visitor's network address.
- Approval lists show a summary, not ticket details, and a decision counts only while the ticket is still at the stage it was made for.
- Requests through a proxy are trusted only within an explicit boundary.
- Configuration secrets are handled more safely when the Suite starts.
For developers
- Suite UI Kit. One component design system across Studio.
- Apps can revoke their own sign-in tokens. When your app signs someone out, it can retire that session's tokens right away instead of waiting for them to expire.
- Wallet data within a workspace. Service clients can request a business or contact wallet's locations, accounts, and related records within a named workspace, the same way Studio does.
- Faster developer setup. Setting up a development environment is faster, works on Linux as well as Windows, and the repositories clone over HTTPS without extra credentials.
- Not found means not found. Asking the API for a record that doesn't exist returns not found, not a server error.
What's next
ABS 2.3 is already live too, and its post covers what it brings and what's coming in 2.4.
ABS is our Business OS for the AI and superintelligence era, and each release moves it closer.
The ABS team, Fenix Alliance Group