Licences
How Licences decide which features a Community Portal has.
Not every Community Portal has every feature. A Portal is sold in Licences, and each Licence brings a set of features: its collections in the admin, its pages on the Portal and its workflows. Pages in this documentation about a licensed feature name the Licence in one line at the top.
The Licences
| Licence | Brings |
|---|---|
Content Management (content-management) | Pages, Posts and Post Categories, Videos, and their Configuration |
Travelling (travelling) | Travels with Hotels, Travel Topics, Destinations, Room Types and the other travel lists, the Booking button and its Booking Requests, Catalogs and Booking Channels, and the travel Configuration |
Benefits (benefits) | Benefits with Benefit Topics, Benefit Types and Benefit Variants, the Redeem button and its Redemptions, and the benefit Configuration |
Member Shop (member-shop) | Catalogs, Booking Channels and the Member Shop Configuration |
Membership (membership) | Membership Enquiries and the Membership Configuration |
Some features belong to more than one Licence, and either is enough: Catalogs and Booking Channels come with Travelling as well as with Member Shop, because a travel's Booking button reads its Catalog. The Member Shop Configuration comes with Travelling as well, because it holds the Default Catalog. Badges come with Travelling and with Benefits.
An Option is an addition to one Licence. The Option analytics adds to Content Management, and a Portal can hold it only together with Content Management.
What every Portal has
Whatever its Licences, every Portal has its Header, Footer and Configuration, its users and their Backend Roles, Images, Files, Layout Templates and Countries. These are the Portal itself, so no Licence switches them off.
What a missing Licence means
A feature whose Licence the Portal does not hold is not there at all. Its collections do not appear in the admin, nobody can read or write them through the Portal's API, and its pages answer "not found". The Portal's visitors do not see a switched-off button; they see no button.
For example, a Portal with Content Management and Benefits but without Travelling shows no "Travelling" group in the admin, has no travel pages and no Booking button, and receives no booking requests.
Who decides
The Licences a Portal holds are part of its deployment configuration, which appsolut sets when it sets up the Portal. They are never stored in the Portal's database, so nobody can change them in the admin.
A Portal editor with the Backend Role admin sees the Portal's Licences and Options on the admin dashboard, under "Licensing". On a development or test installation, which is not a production deployment, the panel says that everything is granted: there, every Licence is switched on.
To add a Licence to your Portal, contact appsolut.