Class of Services (COS)

A COS determines which items can be accessed by a web client and how, setting default for a number of options. A users that belongs to that COS may later change some of these options from the Settings page on the web client.

To create a COS, click the CREATE NEW COS button and enter a name. You can then configure all the options from the left-hand side menu.


Features are settings that allow or forbid the user to access the most used components of Carbonio, both via browser and mobile apps. Some of them can be enabled or disabled via CLI: please refer to section Setting Features from CLI for more information.


Preferences consist of generic options for the various components (Mails, Calendar, Contacts).

The first is the default language to be used by the members of the COS, which includes also the locale, The remaining options concern the appearance of Carbonio in web clients (for example, if e-mails are displayed as conversations, or the calendar shows a month or a work week) and governs the behaviour of some tasks carried out by the user, whether new e-mail contacts are added automatically to Contacts, or how often to check for new e-mails.

Server Pools

In this page it is possible to select on which servers new users can be added to the COS.


If only one server has been defined, no choice is possible.


The Advanced Option allow to configure the user quota, data sources, proxy settings, passwords, and more.

The user quota, is a set of options that limit how much space a user can occupy on the server, or how many contacts he can have. It also encompasses the option to send periodic notifications when the user space raises over a given threshold.

The Data sources, also called polling intervals, allows to define of often to contact the Carbonio infrastructure to update e-mails and calendar. One option allows also to define the shortest interval for polling, that will be used if no other one is configured.

Proxy settings are used to allow domains to be proxyed.

The Password settings permit to tune the length, characters, and duration of the user passwords. It is also possible to reject common passwords.

The Failed Login Policy allows to define the behaviour of Carbonio when a user fails a log in. A typical policy can lock out the user for one hour when three consecutive login attempts fail within 30 minutes.

The Timeout Policy concern the duration of the token’s validity.

The Email Retention Policy define how long e-mail will be stored before being automatically deleted.