Phase 01 · Person, unit, role
Creating
The identity is created from the membership database, from a CSV import or in the administration of the responsible unit. It contains the person’s unit and roles and the services they need.
The administration
Identities and structure
Connecteeva keeps staff, volunteers and members in one system, each person with the unit they belong to and the roles they hold there. Mailbox, file storage, chat and other applications take sign-in and permissions from this source.
The starting point
Regional associations, district branches and local branches decide many things themselves, including their tools. As a result, every new application needs its own accounts, invitations and upkeep.
Unclear contacts
Who currently leads a local branch, and at which address, is often recorded only in a local list. After elections, the mailing lists go out of date.
Accounts in many places
Email, file storage and chat each keep their own user list. When someone stops working with you, their access has to be removed in each one separately, and no overview shows who has access to what.
Only two roles
Many systems only know administrator and user. For a local branch to manage its own people, it would need permissions for the whole association.
One identity per person
Everyone who works for the association or receives a service from it is recorded.
Staff work in the offices of the national association, the regional associations and the district branches, volunteers at every level down to the local branch. Members belong to their local branch and receive only the applications intended for them.
A person can belong to several groups. A local branch chair is also a member and reads the member magazine with the same identity she uses for the branch’s role mailbox. When her role ends, she loses only the permissions that came with it. Her access as a member remains.
Typical applications and permissions by group
| Group | Typical applications | Typical permissions |
|---|---|---|
| Members | Member magazine, member app, advice appointments | Read, update their own details, book appointments |
| Volunteers without a role | Chat, calendar and files of their group | Work within their own group |
| Volunteers with a role | Role mailbox, file storage and mailing lists of the local branch | Write on behalf of the role, manage people in their own unit |
| Staff | Email, specialist applications, website content management | Work according to their job, administration of their own area |
| Administration at regional or national level | Administration interface, reports | Overview of all levels below, stepping in when needed |
Structure
Each person belongs to their local branch and, through it, to the district branch, the regional association and the national association. This lets you address any group directly, such as all volunteers in a regional association or all chairs in a district.
The model comes from our operation for a large social welfare association. There, Connecteeva manages the identities from the national association down to the regional associations.

Role accounts such as chair, treasurer and secretary belong to the local branch and stay when the person changes. The interface is in German.
Rules
When a person’s role changes, their permissions change in every connected application.
We work out levels, groups of people and rules together with you during the introduction.
Membership databases
Connecteeva keeps no second membership list.
Several sources
Each regional association connects its own membership database. Different data models are mapped to one common model.
Continuous synchronisation
Joiners, leavers, moves to another local branch and changes of role are picked up. Accounts are created, changed or locked.
In the other direction
If a member changes their email address in self-service, the change can be passed back to the membership database.
CSV import
To get started, and for units without a connected membership database, people are imported from a CSV file instead of being added one by one.
Lifecycle of an account
Phase 01 · Person, unit, role
The identity is created from the membership database, from a CSV import or in the administration of the responsible unit. It contains the person’s unit and roles and the services they need.
The administration
Phase 02 · One sign-in
The invitation goes out automatically. After the first sign-in, all services enabled for the person are in the portal as tiles. Connected applications use the same sign-in.
Sign-in and claims
Phase 03 · Day to day
Mailbox, calendar, files, chat and video, in the browser or with Thunderbird, Outlook and Apple Mail. At sign-in, each application learns the person’s unit and roles.
The communication services
Phase 04 · Change of role
When the role changes, the permissions change according to the association’s rules. Services can be assigned to each person and withdrawn again.
How this is billed
Phase 05 · Lock and delete
When someone’s involvement ends, the identity is locked or deleted. Role mailboxes and shared storage stay with the association.
Security & data sovereignty
Security and self-service
Protection
Stricter rules where there are more permissions
Self-service
Fewer requests to the office
Example
After the annual general meeting, a new person takes over as treasurer. The previous treasurer remains a member and carries on working in a project group.
In a conversation, we go through your levels, membership databases and existing applications, and the groups of people you want to reach. From this, we draw up an outline of how identity management would be set up for your association 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