What ONE does
Membership and sign-in, built in. Everything an organisation needs to know who belongs to its communities, and to let them in.
Member registers
Internal registers you upload or edit in the Studio, and external registers, such as SAP HR, that stay in your own system and are asked live.
Membership definition
One ordered list of your registers, with filters and outcomes, decides who may become a member. Every saved version is kept.
Communities
Active employees, retirees, all staff: communities decide who may use which portal or app, and follow every membership check.
Login with appsolut
One sign-in for all your frontends, on sign-in screens in your colours. Members confirm their membership once, with their member code.
Frontends and Members API
Connect your portals and apps as frontends. Their backends ask the Members API who is a member, without a copy of your registers.
Servers in the EU
The servers and databases of the Studio and of the Community Portals run in data centres in Frankfurt, Germany.
How it works
Three steps to your community
Connect your registers
Upload a list of retirees, or connect your HR system through the appsolut register API.
Define who is a member
Put your registers in order, set what each one decides, and form communities for your portals and apps.
Members sign in once
With Login with appsolut, members sign up, confirm their membership once and reach every frontend with one account.
Sign-in screens in your colours
Members sign in on screens that carry your organisation's name, colour, logo and legal links, in their language and in light or dark mode.
Rules, not lists
Put your registers in order and set what each one decides. The Studio asks them from top to bottom, and the first register that decides wins.
