When migrating from Labfolder to SciSure for Research, one of the key areas to understand is how user roles and permissions are structured.
Both systems are designed to ensure controlled access to research data, but they differ in how access is defined and managed. Understanding this helps ensure a smooth transition and correct access setup after migration.
In SciSure for Research, access control is designed to be more flexible and granular, allowing organizations to define permissions based on actual responsibilities within projects and workflows rather than fixed role types.
Labfolder Role Structure
In Labfolder, roles are defined at group level:
Main Group Admin
- Full control over the entire workspace
- Manages users, sub-groups, and permissions
- Oversees overall structure and access rights
Sub Group Admin
- Manages users within a specific sub-group
- Controls permissions for that sub-group only
- Does not have full workspace control
Regular User
- Can create and edit entries in assigned groups
- No rights to manage users or permissions
This structure is hierarchical and group-based, meaning access is primarily defined by organizational grouping.
SciSure Role and Permission Model
SciSure for Research does not rely on fixed role types such as “Main Admin” or “Sub Admin.” Instead, it uses a permission-based model where access is built by assigning specific rights to users.
Permissions can define actions such as:
- Viewing and accessing data
- Creating and editing experiments
- Managing users and system settings (admin-level permissions)
- Controlling access at project, study, or experiment level
This approach allows organizations to define roles more precisely based on actual responsibilities in the lab.
A key advantage of this model is flexibility: roles can be adapted to different teams, workflows, or research structures without being restricted to a fixed hierarchy.
Learn more about how roles and permissions work in SciSure
How User Roles Can Be Mapped After Migration
During migration from Labfolder to SciSure for Research, roles are not transferred as fixed equivalents. Instead, they are mapped into SciSure’s permission system.
Main Group Admin → SciSure Administrator
- Full system and user management capabilities
- Can configure permissions and access structures
- Manages overall workspace organization
Sub Group Admin → Custom Permission Set
- No direct equivalent in SciSure
- Responsibilities are recreated using project-, study-, or experiment-level permissions
- Allows more targeted control instead of fixed sub-group boundaries
Regular User → Standard User
- Can create and edit experiments
- Works within assigned projects or studies
- No administrative permissions
This transition replaces rigid group hierarchies with a more flexible and scalable permission model.
Key Structural Differences
| Area | Labfolder | SciSure |
| Role structure | Fixed roles (Admin, Sub Admin, User) | Flexible roles built from permissions |
| Access control | Group and sub-group based | Project, study, and experiment based |
| Permission model | Defined by role type | Defined by individual permissions (view, edit, manage, etc.) |
| Admin hierarchy | Main + Sub Group Admin levels | No fixed hierarchy; configurable access |
| Flexibility | Limited role flexibility | Highly adaptable permission design |
Benefits of SciSure’s Approach
The permission model in SciSure for Research offers several practical advantages:
- More precise access control tailored to real lab responsibilities
- Greater flexibility to support different team structures
- Scalability across projects, studies, and departments
- Reduced dependency on rigid group hierarchies
-
Easier adaptation for evolving organizational needs
This makes it easier for labs to design access structures that match how they actually work, rather than adapting workflows to predefined roles.
What Changes After Migration
- Roles from Labfolder are not transferred as fixed role types and are reconfigured in SciSure for Research using its permission-based access model
- Labfolder sub-group structures are not directly replicated and are instead represented within SciSure’s project- and study-based organization structure
- In SciSure, access is managed through configurable permissions rather than predefined hierarchical group roles, allowing access to be tailored to the lab’s setup
- After migration, it is recommended to review user permissions to ensure they reflect the intended responsibilities and workflows within the new SciSure environment
Labfolder uses a fixed role hierarchy, while SciSure uses a flexible permission system. After migration, user roles must be reassigned and configured to match SciSure’s project- and permission-based structure.
Learn how to update or assign user roles
Learn more about configuring permissions