The Lumis has an API for conducting audits. It is possible to register some operations originating from users such as: creation of a channel, creation of a page, removal of a content version, etc.

The data recorded in each operation are:

• Category;
• Type;
• User Identifier;
• User Login;
• Title;
• Description.

It is possible to determine how long the Audit entries will be kept in the database. Also, it is possible to enable and disable types of Audit. – this determines whether the entries will be saved in the database or not. All entries are logged in the log file regardless of whether they are enabled or not.

The "Category" field represents an area of the Lumis Portal. The "Type" field represents a type of operation possible for a specific area. Thus, each category groups some types of possible operations. The existing categories are: “Audit”, “Structure”, “Portal Studio”, “Content” and “Website”.

The "Structure" category groups operations related to the structure of the Portal, such as:        

• Add, update and remove channel;
• Add, update and remove page;
• Add, update and remove service instance;
• Add, update and remove interface instance;
• Clear cache of pages and/or channels via Portal Studio;

The "Content" category groups operations performed on contents, such as:        

• Add, update and remove content version;
• Block and unblock Content Locale;

The "Portal Studio" category groups operations performed in the portal studio, such as:        

• Clear portal, channel and page cache;

The "Audit" category groups operations performed regarding audit administration, such as:        

• Enable / disable audit functionality;

The "Website" category groups operations regarding the website, such as:        

• Add, update and remove website;
• Add, update and remove URLs of a website;

The "Title" field presents a summary of the operation performed.

The description varies according to the component that is registering the operation. Each component constructs the text that will be used as a description according to the data that is relevant to the operation. Some information that may be available in the description of an audit entry are: service interface identifier, page identifier and name, service instance identifier, etc.
Below is an example of an audit entry in the log file:

Permissioning

• Manage service instance: Allows managing all the data of this service instance, including deleting it entirely.
• Edit content of service instance: Allows managing all the data of this service instance with publisher profile.
• View service instance: Allows viewing public data of this service instance.

Interfaces

• Audit
• Audit Item Detail
• Types
• Configuration