Core Concepts

Before you start using LexasCMS, it is useful to understand some of the core concepts and terminology that you will come across.


A user is anyone that has an account and they can be a part of multiple organisations. After creating an account, a user can either create their own organisation or be invited into an existing one.


An organisation is the billable entity to which users and spaces can be added. When a space is created, it is both linked and billed to the organisation that it was created within.

When a user is added to an organisation, they are given a role that dictates which actions they can perform and the information they can see within that organisation.

The available user roles are described below:

  • Admin - Capable of performing any action within an organisation including creating and deleting spaces, managing billing information and managing content.
  • Editor - Limited to managing the content for all spaces within an organisation. Editors cannot manage a spaces content model.


A space acts as a container for your content and is created within an organisation. Creating multiple spaces allows you to separate your content depending on your project’s needs.

You can create as many spaces as you need within an organisation.

Content Model

A content model defines the structure of the content that is contained within a space and consists of locales and content types.

Locales allow you to define the languages that your content can be translated into. A space can either have one locale or multiple depending on your requirements.

Content types are the main building blocks for your content. They define the specific types of content (e.g. Articles, Promotions etc.) that can be created within your space and the fields that those pieces of content are comprised of.

For more information about modelling content, click here.

Content Item

A content item is an entry of content that has been created within a space. They are created using one of the content types defined in the space’s content model and contain one or more variations.

See below for more information about variations.


A variation can be seen as an instance of a particular content item. Content items are composed of one or more variations, on each of which you can define a priority and also schedule both when the variation should become active and when it should expire.

Simple use cases may only require content items to contain one variation, whereas more advanced use cases such as those where content changes are planned weeks or months in advance will require multiple to be created.

By combining the priority and scheduling rules in variations, you can quickly and easily plan and orchestrate complex content strategies.

© 2020 Status200 Ltd.