Feature Catalog
This catalog describes what App Suite UI does, from a user and customer perspective. It is written for product management, presales, partners, support and customers. The matching switches and their defaults are documented in the Deployment Guide; this catalog links to them rather than repeating them.
Highlights
A subjective pick, not a ranking: the handful of things worth knowing about if you only read one page of this catalog. Every one of them arrived during the 8.x line.
Undo the last action and Undo send — take back a delete or a move anywhere in the product, and take back a message in the seconds after it leaves.
Snooze a message — put a message out of the inbox until the morning you can actually do something about it.
Schedule a message for later — write it now, let it arrive when the recipient is at their desk.
Side panel — the calendar or the task list beside the inbox, answering what the day looks like without giving up what you were reading.
Categories across apps — one set of the user's own labels, shared by mail, calendar, contacts and tasks rather than reinvented in each.
Use a shared account — a team mailbox and calendar several people work in, without anybody sharing a password. (Enterprise)
Soon
Drive on storage you already run. Drive already connects OpenCloud and Nextcloud alongside its own file store. The step still to come is dropping the requirement for that file store underneath, so a storage you already operate can be the only one.
The applications
Each application is a separate module, switched on per user by a capability. A user who does not have the capability does not see the app at all — or sees an upsell trigger in its place, where that is configured.
| Application | Capability | What it is |
|---|---|---|
webmail | Reading, writing and organizing email | |
| Calendar | calendar | Appointments, invitations, scheduling and resources |
| Address Book | contacts | Contacts, address books and distribution lists |
| Tasks | tasks | Personal, delegated and shared task lists |
| Drive | infostore | File storage, sharing and preview |
| Portal | portal | A dashboard of widgets — Provider Edition only |
General covers what is the same everywhere: navigation, search, notifications, settings and appearance, signing in and account security, onboarding and devices, shared content and categories, and delegation.
Across the applications
| Page | What it covers |
|---|---|
| On a phone | What the product is like on a phone, and what a progressive web app is |
| Enterprise features | The features meant for organizations rather than for individuals |
| Provider Edition | The features that ship only with the separately licensed Provider Edition |
How availability works
Whether a user actually sees a feature is decided by three independent layers. A feature appears only when all three allow it.
- Capabilities are granted by the Middleware per user, context or configuration cascade — they express what a user is licensed and permissioned to use (for example
webmail,calendar,infostore,dynamic-theme). A missing capability hides the feature, and may instead show an upsell trigger. - Feature toggles are deployment-wide switches under
io.ox/core//features/. They turn a feature on or off for everyone, cannot be changed by the user, and are the mechanism used to roll new functionality out gradually. See feature toggles for the list and defaults. - Settings are the user's own preferences, within whatever the deployment left unprotected. An operator can change a default and protect it, which removes the choice from the user — see Configuration.
Some features add a fourth condition that cannot be configured away, such as a minimum Middleware version or a device class. Those are called out on the feature's own page.
Looking for a specific switch?
The settings list is the reference for every documented setting and feature toggle with its default value.
Browser and device support
The supported browsers, operating systems and minimum screen sizes are listed under Browser support.