Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Every context will have a context name and a context id to identify the context for later provisioning calls. A context can also define which modules (calendar, tasks, email, e.g.) can be used by its users via predefined "module access combinations"; these names are configured on the server side. All users which are created inside a context will inherit the module access rights from the context and can only access the modules which are configured for the context, unless this is changed for the user itself. Additionally, a context can define how much quota can be used by its users to store things like attachments to contacts and calendar appointments, e.g. (Please note that this will not affect the mail quota). 

Anchor
contextAdmin
contextAdmin
Every time a context is created a context admin is created. The context admin is like an ordinary OX Cloud user, except that it can add, remove and edit users within OX Cloud using the provisioning API. In OX Cloud, however, the context admin cannot read, send or receive mail.

...