KaiperKit separates scientific role, platform access and participation in specific research activities. Three distinct dimensions for organising scientific teams without treating every member as the same kind of user.
A PhD researcher can be an Editor. A researcher can be a Collaborator on the platform. An external member can have different access levels. KaiperKit records each dimension separately.
Describes the person's function within the research environment.
PI · Researcher · PhD researcher · TechnicianDetermines general reading, editing and administration capabilities.
Owner · Admin · Editor · Collaborator · ViewerConnect members with specific research entities and tasks within the workspace.
Project · Paper · Research line · Thesis · Conference · Funding callThe scientific role adds organisational context to the profile. It is descriptive: it does not automatically grant permissions or determine which entities a member can access.
Permissions depend on the platform role, not on the member's scientific title.
The table summarises the common rules across core entities. Some areas apply additional restrictions. Editors can invite members and edit their scientific role, but only Owners and Admins can change platform roles or remove members.
Assignments record where a person participates in the research. They can be activated or deactivated and can include start dates, end dates and notes.
Entity assignments and task assignments are separate concepts: one places a person within a research context; the other distributes operational work.
Each profile combines scientific identity, access, relationship with the workspace and number of assignments.
Describes an internal relationship with the team.
Identifies collaborators linked from outside the organisation.
The member type is descriptive. Being external does not, by itself, restrict access: that is determined by the platform role and, for Collaborators, by their assignments.
KaiperKit creates an invitation for the specified email address, records the selected roles and activates membership when the person accepts using that same address.
Invitations use a token, expire and record their acceptance. KaiperKit does not currently offer SSO, SCIM or automated provisioning.
Across the core entities, Collaborators can view those for which they have an active and valid assignment. They can also view their own or assigned tasks. They do not have workspace-wide editing access.
The current scope of KaiperKit's team system, explained without confusing scientific identity with access.
Discover research team management where a person's scientific function is not confused with their level of access.