Documentation/Portal
Back
  • Getting started
    • The three roles
    • Licences
  • Portal in the Studio
  • Editing the Portal
    • Sign in and Backend Roles
    • Pages, Layout Blocks and Layout Templates
    • Records and Taxonomies
    • Catalogs and Seasons
    • Drafts, publishing and preview
    • Translations
    • Images, videos and files
    • Site settings
    • Booking Requests, Redemptions and Membership Enquiries
    • The Portal's users
  • Using the Portal
    • Book a travel
    • Redeem a benefit
    • Write to the membership office

Getting started

What a Community Portal is, and how this documentation is organised.

appsolut ONE is the enterprise community server. It has two parts: the Studio, its admin app, and the Community Portal, a customer-facing website your organisation connects to the Studio. This documentation is about the Community Portal, the Portal for short.

What a Community Portal is

A Community Portal is your organisation's website for its community: the employees, retirees, members and partners it wants to reach. It carries your own content, such as pages and news, and personalised services such as benefits, travels and vouchers.

Every Portal is its own website with its own address, content and settings. One organisation's Portal never shows another organisation's content, and a Portal offers only the features its organisation has licensed (see Licences).

The Portal is a frontend of the Studio. The Studio decides who a member is and which members may use the Portal; the Portal shows them content and services. Today, visitors confirm that they are members with their member code when they book a travel or redeem a benefit. Portals are moving to Login with appsolut, the one sign-in for all of an organisation's frontends; once your Portal offers it, people sign in to it with that account.

An example

The examples in this documentation use Pannoniqa AG, a fictional manufacturer. Its Community Portal, the "Pannoniqa Portal", is for all staff: active employees, found in the HR system, and retirees, kept in a register in the Studio. It offers benefits at partners in the region, travels organised by the works council, and pages about the Portal itself.

How this documentation is organised

Three roles work with a Community Portal, and the sections follow them (see The three roles):

  • Portal in the Studio: for the Studio user who connects the Portal and decides who may use it.
  • Editing the Portal: for the Portal editor who maintains the content in the Portal's admin.
  • Using the Portal: for the people who use the Portal and its services.

In this section

  • The three roles: who works with a Portal, and where.
  • Licences: how Licences decide which features a Portal has.