What changed

This page records user-visible changes to the Business-Gym documentation — what the pages you read now say, what they say more plainly than before, and what they have stopped implying. It is not an internal release log: you will find no build numbers, deployments or ticket references here.

Entries are newest first. Only changes that can be verified from the published documentation and the integrations status matrix are listed. Where a change cannot be verified, it is left out rather than guessed at, which is why this page is short.

What is the most recent change?

The documentation site was rebuilt on a new publishing framework, and the part you actually notice is getting around it — searching, reading in the dark, and finding a page without knowing its name. What is new for you as a reader:

• Full-text search across every published page, opened with Ctrl+K (or Cmd+K on a Mac).
• Light, dark and system themes — the site follows your operating system unless you pick one.
• A grouped sidebar — Getting started, Concepts, Heads, Approvals, Guides, Commercial, Integrations, Use cases and Reference — in place of the flat page list.
• A German edition — every published page also exists in German at the same address with /de in front, reachable from the language switcher in the site header.

Every existing address still works. No page moved and no redirect was needed, so any link you saved or shared before the rebuild still lands on the same page. Diagrams are now rendered as real text at build time rather than as pictures, which means the words inside them are searchable and readable by a screen reader.

What changed about how connections are documented?

Connections are now documented as a status matrix rather than a capability list. Each connector states three separate things — what Business-Gym reads, what it writes, and what it only proposes for you to approve — instead of one blurred “supported” column.

The practical effect is that the short columns are now visible. Four connectors can write anything at all (email, Facebook and Instagram, LinkedIn, and creating a Dynamics lead), every one of them human-approved. Everything else reads or proposes.

DATEV now has its own page that opens by saying it is not connected, because the previous silence read as “probably works”. Google Ads is documented as read-only by construction, and SharePoint and calendar as read-only today.

Note

Several limits sit behind interface surfaces that look ready to use. The matrix is the authority — if a connector is not listed as writing, the button offering it is preparation, not a live path.

What changed about seeing whether an approved action ran?

The documentation now tells you where to confirm that an action you approved actually happened, which was previously left to you to work out. Approving is your decision; the outcome is a separate, recorded fact.

In Approvals, the History tab is a read-only list of decided items. Each row shows your decision and the time, and beneath it the execution outcome — executed, skipped or failed. Where the outcome has a real artifact, such as a send, the outcome links through to its row in the outbound ledger.

Where nothing has been recorded, the row says “no execution recorded yet” rather than showing nothing. An empty history renders an honest empty state instead of invented rows. Working the queue in full is covered in working the approval queue.

What has not changed, and will not?

The approval floor has not moved, and no entry on this page has ever moved it. Business-Gym proposes; a person decides. Anything that sends externally, and anything that touches money, is approved by a human every time.

This is worth stating in a changelog specifically because a changelog is where a reader expects to find that kind of thing quietly relaxed. It is not going to appear here — the floor is described in autonomy and the hard floor, and it holds at every autonomy level.

What is still not available?

Several things people ask for are genuinely absent, and this page will not pretend otherwise until they exist. These are current gaps, not roadmap entries:

• A native mobile app, and push notifications. There is no mobile app and no push infrastructure. Nothing on this page has ever announced one.
• An in-product changelog or “what’s new” notification. Nothing in the app tells you when documentation changes. This page is the record; you have to come and read it.
• Per-entry dates on this page. Entries are ordered newest first without individual dates, because a date that cannot be verified is worse than no date.

How do you know a page is current?

Every published page carries a last-updated date in its metadata, which is the date search engines and AI assistants read for that page. It is not printed at the top of the page, so this changelog is the human-readable version of the same signal.

The whole published set is also available as one plain-text file at /llms-full.txt, with a shorter index at /llms.txt. If you are pointing an assistant at Business-Gym documentation, use those rather than scraping pages one at a time.

Why does this page not list every change?

Because most changes are not things you can act on, and a long list of them buries the few that are. A build number, a refactor or an internal deployment changes nothing about what you can do tomorrow morning.

The test for inclusion is simple: would you behave differently having read it? A connector that started writing somewhere, a limit that was removed, a screen that now shows you something it did not — those belong here. Everything else does not.

If a change you can see in the product is missing from this page, that is a documentation gap worth reporting. If a change is described here that the product does not do, that is a worse one.

Next: check what your connections can actually do in the integrations matrix, or start from getting started if you are new. Short answers live in the FAQ, and terms are defined in the glossary.