For associations
One identity for every person in the association.
Staff, volunteers and members are managed with their level and their roles. Email, calendar, files, chat and video, as well as other applications, take sign-in and permissions from this identity. Each level can manage its own people.
The starting point
Independent levels, separate systems.
Regional associations, district branches and local branches are often legally and organisationally independent. They decide for themselves on their membership database, email and tools.
Unclear contact details
Who currently leads a local branch, and at which address, is often recorded only in a local list. After elections, the distribution lists go out of date.
Separate solutions side by side
Mailboxes, cloud storage and accounts are set up in parallel at many levels. You pay several times over, and nobody sees who has access where.
Different membership databases
Who is a member of which local branch and who holds which role is recorded in the membership database. Regional associations often use different systems for this.
Every application with its own accounts
A member app or a digital member magazine needs accounts, invitations and upkeep. The effort delays such projects or stops them altogether.
Roles change hands
New people take over as treasurer, secretary or group leader. Old accounts stay open, and successors cannot get into the mailbox and files.
Member data in private mailboxes
Where there is no association address, the work runs through private accounts, with all the member data in them.
How it works
Permissions and visibility follow the structure.
Each person is assigned to the local branch they belong to and, through it, to the district, regional and national association.
National or regional head office
Sets the structure and the rules
- Maps the levels, from the national association down to the local branch.
- Defines which role receives which permissions, for example: the local branch chair receives a role mailbox and access to the local branch’s files.
- Decides which services and applications are available to each level.
- Can step in at lower levels, for example when a role is vacant.
- Sees in the audit log who made which change and when.
Regional association, district and local branch
Can manage its own people
- Has little to maintain itself: most of it is handled by the synchronisation with the membership database.
- Creates accounts for people who are not members, such as helpers or deputies.
- Sees only its own area and the levels below it.
- Delegates administration permissions to the level below.
- Does not need to ask the head office for everyday tasks.
Staff, volunteers, members
All groups of people in one system.
Each person signs in everywhere with the same credentials. What they may do then depends on their role in the association and on the application.
| Group | Typical applications | Typical permissions |
|---|---|---|
| Members | Member magazine, member app, counselling appointments | Read, maintain their own data, book appointments |
| Volunteers without a role | Chat, calendar and files of their group | Work within their own group |
| Volunteers with a role | Role mailbox, files and distribution lists of the local branch | Write on behalf of the role, manage the people at their own level |
| Staff | Email, specialist applications, website content editing | Work according to their position, administer their own area |
| Administration at regional or national level | Administration interface, reports | Overview of all levels below, step in where needed |
A person can belong to several groups. A local branch chair reads the member magazine with the same identity she uses for her role mailbox. When her term ends, she loses only the permissions of the role. Her access as a member remains.
Synchronisation and integration
The data comes from the membership databases.
From the membership databases
Continuous synchronisation
- Each regional association connects its own membership database. Different data models are mapped to one common model.
- Members joining or leaving, moves to another local branch and changes of role are applied. Accounts are created, changed or blocked accordingly.
- If a member changes their email address in the self‑service portal, the change can be passed back to the membership database.
To the applications
Sign-in and accounts
- Applications that support SAML or OpenID Connect are connected without programming. At sign-in they receive the person’s level and roles.
- Where an application needs its own accounts, as email and calendar do, Connecteeva creates them and removes them again.
- For applications without a standard, such as your own member app, custom interfaces are built.
- For a new tool, nobody has to be entered again and no login details are sent out. Everyone authorised can use it as soon as the integration is released.
Example
A national association with 16 regional associations.
You decide how many levels there are.
- The national head office sets the rules Together with us, it describes the levels, the groups of people and the rules by which roles become permissions. It decides which services the regional associations use.
- The North regional association connects its membership database Members, local branches and roles come from there. The accounts are created according to the rules, for example the role mailbox for each local branch chair.
- The treasurer of the Lindenhof local branch changes The change comes from the membership database. The new treasurer receives the treasury mailbox and files. Her predecessor loses the permissions of the role and keeps his access as a member.
- Each level sees its own part The local branch sees only its own people. The regional association sees everything in North and nothing in the other regions. The national head office sees the whole association.

Role accounts such as “Kasse OV Lindenhof” (Lindenhof treasury) belong to the local branch. The interface is in German.
What is included
Identity management and communication services. Services can be booked per person.
Which services a person receives follows from their roles, or is decided by the level that manages them.
One identity for all services
Each person with their level and roles. Create, change and block in one place.
Identities and structureAdministration for each level
Set up levels, the services for each level and administration permissions in one place.
AdministrationConnecting existing systems
Keycloak, SAML and OpenID Connect, synchronisation with membership databases, custom interfaces.
Technology and integrationAssociation addresses for every level
Addresses under your domain, shared calendars and role mailboxes that stay when the person in the role changes.
Email & calendarShared document storage
Minutes, statutes and funding applications in one place, without passing them around through private cloud accounts.
FilesCoordination without private messengers
Channels for working groups, and video meetings that guests join via a link without an account.
Chat & videoThere are also tools for counselling, mailings and mail operations, such as the delivery report for the member magazine for each level.
Introduction
In stages, with no fixed cut-over date
One regional association and a first application make the start, for example email for volunteers. Further regional associations and applications follow in the order you set. Existing systems keep running until their integration has been tested.
Assisted migration costs €89 per hour. With a contract term of two years or more, there is no fee.
How the migration worksPricing and contract
You pay per account and service
An account with email and calendar costs €1.90 a month net. Non-profit associations receive one free mini account for volunteers with every full mailbox.
Each level can sign its own contract, or a higher level signs an umbrella contract for all of them.
What the price depends onWho is behind it
Built from our work for a large social welfare association. In use from the national association down to the regional associations.
Connecteeva comes from czichos.net GmbH, an ICT engineering firm in Berlin that has been in business for more than 20 years.
Operation
In German data centres, operated by us. czichos.net GmbH has no US parent company.
Export
Identities, structure and permissions can be exported. The software behind the services can be replaced.
Data protection
Data processing agreement under the GDPR and technical and organisational measures on request. Your domain belongs to you.
Get your structure reviewed. By phone or video call.
In a conversation we record your levels, membership databases, existing applications and the groups of people you want to reach. From this we prepare a written outline of how the identity management for your association would be set up and which application makes sense as a starting point.
No contract and no payment details.
Prefer to reach us directly? Send an email · call +49 30 994048000
Königsweg 220
14129 Berlin, Germany