Getting Started







UNA Concepts

UNA CMS is based around a set of defined concepts. Before starting to work with UNA, it's a good idea to familiarise yourself with the following:


User-generated content items like Posts, Videos, Discussions, Updates and Photos. Usually the Apps that allow publishing of content items are called Content Apps.


Context refers to apps that can work as containers for content or context items from other apps. Groups, Spaces, Events are Context Apps. People and Organisations are Profile Apps and Context Apps, too.


Profiles represent a user in the frontend. A profile is assigned a Membership Level and can perform actions based on the permissions granted to that level. Profiles can be administrators, moderators, standard members, or any custom level configured in the Permissions Builder.


Some accounts in UNA can be operators. Only operators have access to Studio. Operators can have their own roles, which define access to categories of apps in Studio. The full-access operator account is called "Master." Operator accounts can access site configuration; they don't need to have profiles.


Site configuration is done in UNA Studio. The Studio is a no-code interface designed for site operators. The Studio is intentionally separated from site administration and moderation, allowing for separation of concerns and greater operational scalability.


We call all UNA components apps. These may be content modules, context modules, profile modules, templates, language packs, service tools, integrations, and core apps. While we may use the word "apps" to refer to mobile applications or third-party software, generally in UNA, apps are the components within UNA CMS that can be found in Studio.


Pages represent data in the frontend. Page can have different page layouts, layouts consist of cells, cells contain blocks. All these is buildable using intuitive drag&drop interface.


Data in UNA is stored and displayed according to the structure defined by forms. Forms is actually a builder where you can add/edit/delete fields for different data.


As a Community Management System, UNA heavily relies on its permissions system. Accounts and profiles are associated with membership levels that can be granted rights to perform specific actions. Membership levels are also used to define the visibility of menus, menu items, forms, form views, form fields, pages, blocks, contexts, and content instances.