Account and apps
1A cooperative, three people in the portal.
Wohnbau Rheinaue eG has its company account with a payment method, and a record in DNS, the internet's address book, proves that the domain wohnbau-rheinaue.example is its own. Three people work in the portal: Katrin Behrens from the board as owner, Jonas Albers in IT administration and Petra Lindner in the security and audit role. Everyone else lets flats and repairs heating, with the apps and without the portal at all.
2A setup becomes a change.
In the catalog Jonas picks the setup Secure passwords: a central sign-in and a password manager, both Managed Apps that gh0stservice runs with backups and updates. It turns into a change with apps, connections and costs on one page. The setup only fills it in: what stands at the end is two apps, each under its own contract. As the owner Katrin approves the costs and consents to the change, both with her passkey, a sign-in by fingerprint, face or security key. The consent covers exactly this one change.
3Servers of its own for the mail, after gh0stservice's review.
Mail needs servers of its own: the mail server sends and receives under IP addresses of its own and runs on a server pool used by the cooperative alone. Jonas requests the pool in the portal, and gh0stservice reviews the request before an offer comes. Once Jonas confirms the offer, the pool is set up.
4For mail, gh0stservice has a say.
Then Jonas orders the setup Email. The change brings the mail server and webmail and orders the mail's two own IP addresses along with them; Katrin approves the costs and consents. gh0stservice approves a higher limit, since a new account starts with up to three Managed Apps. The platform checks the DNS records once the cooperative has published them at its provider. Each app is handed over only after its first backup and a restore test, in which a backup is actually played back.
5Mailboxes for the sign-in's people.
The mail server and webmail are running now. So that every person the central sign-in knows also gets a mailbox, Jonas opens the environment map, the portal's map of every app and connection, and connects the central sign-in to the mail server there. That is a change too, and Jonas consents to it with his passkey.
Its own identity provider
6gh0stservice prepares, Jonas consents.
The cooperative keeps running its identity provider with its directory itself: the service its people already sign in with today. Connecting it is work by the hour, as the service description says. gh0stservice enters the identity provider and the directory as external services, in a change on the cooperative's behalf, and Jonas consents to it with his passkey.
7Jonas sets the credentials himself.
For the central sign-in the identity provider has issued credentials, the access keys the sign-in identifies itself with there, and the directory has a key of its own. Jonas sets them himself in the portal. Only IT administration and the owner may do that, not gh0stservice on the cooperative's behalf. The values go to the platform once, land in the secret store, the platform's protected store for keys and passwords, and are shown nowhere afterwards.
8The central sign-in gets to know the cooperative's people.
A second change, again prepared by gh0stservice, connects the central sign-in to both services. It takes the sign-in from the identity provider over OpenID Connect, the common standard for it; the directory reports the people to it over SCIM, the standard directories use to pass people on. The platform accepts an outside sign-in only together with a source that reports who leaves the cooperative. Jonas consents, and both connections are ready.
The people
9The directory sends its people.
So that gh0stcloud may create and change people in the central sign-in, Katrin switches people management on, as a change with her passkey; only an owner can do that. Then the directory sends its people, about 120 of them, and from now on reports by itself who joins and who leaves. IT sets up units and groups in the Studio, the company directory in the portal.
10Units, mailboxes, access: one review, one consent.
In the Studio Jonas sets up three units: administration, lettings and maintenance, plus a group for IT. Each unit gets its access profile, and every person from the directory goes into their unit and gets a mailbox. Before anything is applied the Studio shows what changes, for people and per app; then Jonas consents with his passkey, and the platform creates the mailboxes, groups and access.
11Jana signs in with her cooperative account.
Jana Wolff from lettings opens webmail, picks the cooperative's button on the central sign-in and signs in at its own identity provider. The central sign-in links this sign-in by user name to Jana's account from the directory, and the same way opens the password manager too. No app may act inside the sign-in on Jana's behalf: the sign-in refuses every app a token for itself, a token being a kind of pass with an expiry date.
Leaving and returning
12Lars leaves. Sign-in, mailbox and password manager are closed.
Lars Petersen's apprenticeship in maintenance ends, and Jonas switches him off in the cooperative's own directory. The directory reports it, and the platform locks Lars out of the central sign-in, his mailbox and the password manager; nobody has to do anything in the portal for that. Even if the identity provider still let him through, the central sign-in now turns him away. If Jonas deletes him from the directory altogether, the sign-in locks him out just the same, and his user name stays taken.
13Lars comes back.
Then the cooperative takes Lars on after all, and Jonas switches him back on in the directory. Sign-in, mailbox and password manager are open again, and Lars reads his mail.
Wrap-up
14Its own directory, and gh0stservice runs the rest.
The cooperative's people sign in with their existing accounts. Its own directory reports who joins, and whoever leaves is locked out on gh0stcloud too, after one click there. gh0stservice runs the sign-in, mail and the password manager from Cologne, in Hetzner data centres in Germany. Built in-house, the cooperative would need a platform of its own and a team to run it; the comparison further down works out what each way costs.
Wohnbau Rheinaue eG, a housing cooperative, is a made-up example.