Versions and known limitations
insideCRM is updated as a centrally operated platform. Visible changes may therefore affect the interface, permissions, API contract or integration behaviour.
Classifying a change
| Observation | Check first |
|---|---|
| Navigation or wording changed | Open the feature index and affected guide. |
| An action is no longer visible | Compare role, capability, licence and record state. |
| An API client fails after a change | Check the public OpenAPI schema and status code. |
| Only one browser shows an old state | Perform a full reload and update its cache or service worker. |
| Mobile behaviour differs | Check the app version, platform and documented mobile scope. |
Version details for support and integrations
Record the product, host, time with timezone, browser or app version and affected workspace. API reports additionally require the method, path, status code, request ID and schema version. Never include secrets or complete production payloads in tickets or screenshots.
The machine-readable release manifest provides product, language, documentation state and content hashes. It contains no internal source paths.
Permanent boundaries
- Available features depend on product, workspace, licence, capability and role.
- Browsers may restrict background work, media devices and notifications for privacy or power-saving reasons.
- External mail, calendar, telephony and property-portal providers may impose their own limits or delays.
- Offline work is available only where the relevant interface explicitly provides it.
- Large files, bulk imports and global searches may be processed asynchronously.
A limitation is not a release approval, security assessment or SLA commitment. Contractual and support terms are available in the legal centre.