Identities and structure

One identity per person.

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

Every application keeps its own accounts.

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

Staff, volunteers and members in one system.

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

GroupTypical applicationsTypical permissions
MembersMember magazine, member app, advice appointmentsRead, update their own details, book appointments
Volunteers without a roleChat, calendar and files of their groupWork within their own group
Volunteers with a roleRole mailbox, file storage and mailing lists of the local branchWrite on behalf of the role, manage people in their own unit
StaffEmail, specialist applications, website content managementWork according to their job, administration of their own area
Administration at regional or national levelAdministration interface, reportsOverview of all levels below, stepping in when needed

Structure

Access is organised like the association. Each level can manage its own people.

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.

National associationsees all levelssteps in when needed
Regional associationsees its district branchescan manage itself
District branchsees its local branchescan manage itself
Local branchsees only its own peoplecan manage itself

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.

  1. Self-administration is possible, not required Most of the work is done by the synchronisation with the membership databases. The local branch itself adds a deputy or a helper who is not a member.
  2. Each unit sees only its own area Whoever manages a district branch sees that district branch and its local branches. Neighbouring districts and higher levels stay hidden.
  3. The level above assigns administration The parent level decides who may manage a unit. Without this approval, nobody manages anything.
  4. Higher levels can step in If a local branch has nobody to look after its accounts, the district branch or regional association takes over this work.
  5. Every change is logged The audit log records who changed what and when, at every level.
admin.connecteeva.eu
Administration with sample data, German interface: the tree from Musterverband e. V. through Landesverband Nord and Kreisverband Nordstadt down to Ortsverband Lindenhof, with its people and role accounts

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

Rules turn roles into permissions.

When a person’s role changes, their permissions change in every connected application.

Local branch chairVolunteers, local branch
  • Local branch role mailbox
  • Local branch file storage
  • Manage people in the local branch
TreasurerVolunteers, local branch
  • Treasurer’s role mailbox
  • Finance folder in file storage
AdviserStaff, district office
  • Mailbox and calendar
  • Advice application of their own district
MemberMembers
  • Member magazine of the regional association
  • Own details and appointments in the member app

We work out levels, groups of people and rules together with you during the introduction.

Membership databases

Assignments come from your 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

From creation to departure. In one place, for all applications.

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
admin.connecteeva.eu
Form for creating a user, with sample data for Sabine Wolf: username, organisation Ortsverband Lindenhof and two-factor authentication switched on

Phase 02 · One sign-in

Signing 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
portal.connecteeva.eu
The portal after sign-in, with tiles for video meetings, email and calendar, chat and file storage

Phase 03 · Day to day

Daily use

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
ox.connecteeva.eu
Mailbox in OX App Suite with folder list and inbox

Phase 04 · Change of role

A new 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
admin.connecteeva.eu
Editing a user, Services tab, with the assigned services chat, file storage, video meetings and email and calendar, and below them the settings for email and calendar

Phase 05 · Lock and delete

Leaving

When someone’s involvement ends, the identity is locked or deleted. Role mailboxes and shared storage stay with the association.

Security & data sovereignty
admin.connecteeva.eu
Dialog asking whether to delete the user, with Sabine Wolf’s account and the buttons Cancel and Delete user

Security and self-service

One sign-in for many applications needs strong protection.

Protection

Stricter rules where there are more permissions

  • Two-factor authentication as you specify: for everyone, by role or optional.
  • Stricter rules for accounts with administrative permissions or access to member data, if you choose.
  • Immediate locking of all access when a person leaves or an account is compromised.
  • Audit log of all sign-ins and administrative actions.
  • Overview of recent sign-ins to find unused accounts.

Self-service

Fewer requests to the office

  • Reset your own password, without calling the office.
  • Set up your second factor and manage your devices yourself.
  • Change your own email address and phone number.
  • See all enabled applications in the portal and open them from there.

Example

The local branch gets a new treasurer.

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.

  1. The role comes from the membership database The local branch records the change in its membership database. At the next synchronisation, the successor’s identity receives the treasurer role. Without a connected membership database, the local branch enters it in the administration.
  2. The permissions follow the rule The successor gets access to the treasurer’s role mailbox and the Finance folder. The email of past years stays in the mailbox.
  3. The previous treasurer loses only these permissions Her access as a member and her services for the project group remain.
  4. District branch and regional association have nothing to do The change is recorded in the audit log with a timestamp and shows up in the overview of the higher levels.

Have your structure reviewed. By phone or video call.

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.

We set up trial access and usually send the login details to your contact email within one working day.

No contract and no payment details.

Prefer to reach us directly? Send an email · call +49 30 994048000

Address czichos.net GmbH
Königsweg 220
14129 Berlin, Germany