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.
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 |
|---|---|
| Enterprise and Provider Edition | The features meant for organizations rather than individuals, and the ones that ship only with the 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.
Compliance
| Topic | What it covers |
|---|---|
| Accessibility | Conformance status, known gaps and the per-release history |
| Accessibility Conformance Report | The formal ACR / VPAT for the current release |
| Data protection | Cookies set by the UI and the data they hold |
Browser and device support
The supported browsers, operating systems and minimum screen sizes are listed under Browser support.