Key concepts

The terms the Studio and this manual use.

The Studio uses a small set of terms, and this manual uses them the same way.

Organisations and Studio users

Organisation: the customer, as it exists in the Studio. It owns its registers, its membership definition, its communities and its frontends. Pannoniqa AG is one organisation.
Studio user: a person who signs in to the Studio to administer one or more organisations. The Studio lists them under "Studio users".
Studio role: what a Studio user may do in one organisation: "Owner", "Administrator", "Community manager", "Frontend manager", "Frontend user manager" or "Editor". A Studio user holds one Studio role in each of their organisations. Each task page in this manual starts with the Studio roles that can do it.

Members

Register: a list of people who may qualify as members, each identified by a member code. An internal register is kept in the Studio, by upload or by hand, such as Pannoniqa's "Retirees". An external register stays in the organisation's own system and is asked live, such as "SAP HR".
Member code: the identifier of one person across all registers of an organisation. The same person has the same member code in every register.
Membership definition: the organisation's one ordered list of registers, each with its filters and outcome. It decides who may become a member.
Membership check: the Studio's answer to whether a person is an eligible member: valid, not valid or unavailable. It runs when a person first becomes a member, at each of their sign-ins, and when a frontend's backend asks.
Organisation membership: the record that a member code belongs to a verified member of the organisation. All organisation memberships together are the members directory.
Community: a named filter over the members directory, such as "Active employees" or "Retirees". It decides which members may use the frontends it is assigned to. A member's communities follow from their last membership check; nobody assigns them by hand.

Frontend: an app the organisation's people sign in to: a website, such as the "Pannoniqa Portal", a mobile app, such as the "Pannoniqa App", or an external app the organisation connected. Every frontend has exactly one community.
Login with appsolut: the one sign-in for all of an organisation's frontends. The first sign-in also checks the person against the registers and makes them a member.
Frontend user: a person's account with one organisation, used to sign in to all of its frontends. A frontend user is never a Studio user: the Studio and the frontends have separate accounts.
Community Portal: the frontend component of appsolut ONE, a website with content, benefits and services that the organisation connects to the Studio as a frontend. The Portal has its own documentation.

Organisations and Studio users

Organisation: the customer, as it exists in the Studio. It owns its registers, its membership definition, its communities and its frontends. Pannoniqa AG is one organisation.

Studio user: a person who signs in to the Studio to administer one or more organisations. The Studio lists them under "Studio users".

Studio role: what a Studio user may do in one organisation: "Owner", "Administrator", "Community manager", "Frontend manager", "Frontend user manager" or "Editor". A Studio user holds one Studio role in each of their organisations. Each task page in this manual starts with the Studio roles that can do it.

Members

Register: a list of people who may qualify as members, each identified by a member code. An internal register is kept in the Studio, by upload or by hand, such as Pannoniqa's "Retirees". An external register stays in the organisation's own system and is asked live, such as "SAP HR".

Member code: the identifier of one person across all registers of an organisation. The same person has the same member code in every register.

Membership definition: the organisation's one ordered list of registers, each with its filters and outcome. It decides who may become a member.

Membership check: the Studio's answer to whether a person is an eligible member: valid, not valid or unavailable. It runs when a person first becomes a member, at each of their sign-ins, and when a frontend's backend asks.

Organisation membership: the record that a member code belongs to a verified member of the organisation. All organisation memberships together are the members directory.

Community: a named filter over the members directory, such as "Active employees" or "Retirees". It decides which members may use the frontends it is assigned to. A member's communities follow from their last membership check; nobody assigns them by hand.

Frontends and sign-in

Frontend: an app the organisation's people sign in to: a website, such as the "Pannoniqa Portal", a mobile app, such as the "Pannoniqa App", or an external app the organisation connected. Every frontend has exactly one community.

Login with appsolut: the one sign-in for all of an organisation's frontends. The first sign-in also checks the person against the registers and makes them a member.

Frontend user: a person's account with one organisation, used to sign in to all of its frontends. A frontend user is never a Studio user: the Studio and the frontends have separate accounts.

Community Portal: the frontend component of appsolut ONE, a website with content, benefits and services that the organisation connects to the Studio as a frontend. The Portal has its own documentation.