Labfolder and SciSure for Research are Electronic Lab Notebook (ELN) platforms used by research teams to document experiments, organize research data, and collaborate securely.
Both systems support laboratory documentation and compliance requirements; however, they differ in several areas, including data structure, permission management, file handling, collaboration workflows, integrations, and overall platform extensibility. SciSure for Research extends these capabilities further and is also designed to support GxP environments, making it better suited for regulated research settings with highly controlled research settings.
This article summarizes the main differences between the two platforms.
User and Permission Management
Labfolder and SciSure differ in how permissions and user roles are managed.
| Feature | Labfolder | SciSure |
| Role types | You choose from fixed roles (Main Group Admin, Subgroup Admin, User), and each role already has predefined permissions. | You can create roles or permission levels that match how your team works. |
| Flexibility | If a role doesn’t fit your needs, you cannot easily adjust what that role can do. | You can adjust what each role can do, so different users can have different levels of access. |
| How permissions work | Permissions (view, edit, delete element) are set at the project level through share settings (e.g., contributive, collaborative), and apply to all entries and elements within that project. | Permissions (view, edit, delete) are defined in each user role, where admins decide what actions are allowed for different functions. |
| Level of control | When a user is given access, it applies to the entire project, so they have the same permissions for all entries and elements within it. | Access can be set more precisely, so a user can have different permissions for different experiments or items (e.g., edit one experiment but only view another). |
Labfolder provides a simple permission structure, typically based on Admin and User roles, with access managed at the folder or project level.
SciSure for Research provides granular permission management, allowing administrators to configure custom roles and detailed access rights at both the project/study level and down to individual experiments. This enables precise control over who can view, edit, or manage specific resources across the workspace, offering a clear advantage over Labfolder in terms of flexibility and control.
Learn more about roles and permissions in SciSure for Research:
Data Structure and Organization
Labfolder and SciSure for Research organize experimental data in a very similar way. The overall structure will feel familiar, even though the naming and organization differ slightly.
| Labfolder | SciSure |
| Folder → Subfolder → Project → Entry → Entry Element | Project → Study → Experiment → Section |
In Labfolder, experiments are documented as entries within a project, with each entry containing elements such as text, files, images, or tables.
In SciSure, research data is organized as experiments within a study, and each experiment contains sections that store similar types of content such as text, files, images, protocols, tables etc
Mapping between Labfolder and SciSure
- Entry (Labfolder) → Experiment (SciSure)
- Entry Elements (Labfolder) → Sections (SciSure)
- Project (Labfolder) → Study (SciSure)
- Folder (Labfolder) → Project (SciSure)
What this means in practice
In Labfolder, teams typically define their own folder and project structures, which can vary across users and require alignment to maintain consistency.
In SciSure, the structure is predefined (Project → Study → Experiment → Sections), providing a consistent framework for organizing data across all projects.
Learn more about structuring projects, studies, and experiments in SciSure
Templates and Protocol Management
Both platforms allow teams to standardize experimental documentation using templates.
| Feature | Labfolder | SciSure for Research |
| Experiment templates | Templates are used to structure experiments to reuse (e.g., layout, sections, content fields) | Templates are used to structure entries and can also include instructions or procedures in the form of protocols. |
| Protocols | Not available as a separate feature. | Protocols are a separate feature used to define and manage step-by-step experimental procedures. |
In Labfolder, templates can be created and shared to standardize how experiments are documented, helping maintain a consistent structure across entries.
In SciSure for Research, templates also support consistent documentation, while introducing a more structured approach to managing experimental workflows. In addition to templates, protocols are handled as a separate feature, allowing procedures to be defined and reused independently. SciSure also supports versioning of templates and protocols, making it easier to track changes and maintain consistency over time.
This approach provides clearer organization and greater control over both how experiments are documented and how they are performed.
Learn more about setting up protocols in SciSure for Research
File Handling and Editing
Both systems allow files to be attached to experimental records, but their editing capabilities differ. 
| Feature | Labfolder | SciSure for Research |
| File attachments | Any file type can be uploaded | Any file type can be uploaded |
| Image handling | Images can be previewed and annotated | Images can be previewed and annotated |
| Excel files | Can be extracted into entries and edited | Can be edited directly using eLabWebEdit or added as new files |
| PDF files | Can be previewed only | Can be edited using eLabWebEdit |
| Word (DOCX) files | Content can be extracted into entries and then edited | Can be edited directly using eLabWebEdit or created directly within experiment sections |
| PowerPoint files | Not supported for editing within the platform | Can be edited using eLabWebEdit |
| Editing approach | Files are often converted (extracted) into entries for editing | Files remain in their original format and can be edited directly |
| Create new files | Not supported within entries | New PDF, Excel, and Word files can be created directly within experiment sections |
What this means in practice
In Labfolder, files are primarily used as attachments. They can be previewed directly, and in some cases converted (extracted) into entry content for further editing.
For example:
- Excel and Word files are typically extracted into entries before they can be edited
- PDF files can be previewed but not edited
- Images can be annotated within the platform
In SciSure for Research, files can be used more directly within experiments without the need for conversion:
- Files remain in their original format
- Excel, Word, PowerPoint, and PDF files can be opened and edited using eLabWebEdit
- New files (e.g., Word, Excel, PDF) can be created directly within experiment sections
- Images can also be annotated, similar to Labfolder
This approach allows users to work with files directly, without needing to extract or convert them first, resulting in a more streamlined and efficient workflow.
What is eLabWebEdit
eLabWebEdit enables users to open and edit supported file formats directly within SciSure, without downloading them locally. This supports a more integrated workflow, particularly when working with Office documents and selected scientific file types.
Learn more about Office Online Server
Learn more about managing and exporting experiment files
Collaboration Features
Both platforms support collaboration between researchers, with SciSure for Research offering additional structure and flexibility in how interactions, tasks, and notifications are managed.
| Feature | Labfolder | SciSure for Research |
| Comments | Comments can be added at the entry level | Comments can be added at the experiment and section level, allowing more precise discussions |
| User tagging | Not supported within specific sections | Users can be tagged directly in comments or sections, enabling targeted communication |
| Task management | Tasks can be created and assigned | Tasks can be created and linked to specific experiments, protocols, or inventory items |
| Notifications | Basic notifications for activities (e.g., comments, sharing) | Advanced notifications, including automation-based triggers for actions and updates |
| Resource sharing | Entries and templates can be shared with other users | Experiments, protocols, and other resources can be shared across users and teams |
| Project groups | Collaboration is managed through groups and shared projects. There is no dedicated layer to group multiple projects together. | Project Groups provide an additional layer above projects, allowing multiple projects to be grouped and shared with a defined set of users. Members of a Project Group can automatically be added as collaborators to projects and experiments within that group. |
What this means in practice
In Labfolder, collaboration is mainly centered around entries:
- Comments are added at the entry level, so discussions are tied to the entire entry
- Tasks and notifications help coordinate work, but are generally not linked to specific parts of the data
- Sharing is focused on entries and templates
In SciSure, collaboration is more granular and structured:
- Comments can be added at the experiment or section level, allowing discussions on specific parts of an experiment
- Users can be tagged directly, making it easier to involve the right person in a specific context
- Tasks can be linked to specific items such as experiments, protocols, or inventory, improving traceability
- Notifications can be automated, allowing users to stay informed based on defined triggers and workflows
- Collaboration is organized across projects, studies, and experiments, supporting clearer team workflows
What are Project Groups in SciSure?
In SciSure, Project Groups introduce an additional organizational layer above projects. This allows related projects to be grouped together and managed within a shared structure in the Experiment Browser.
In comparison, Labfolder organizes work through projects and folders, with collaboration typically managed at the project or group level.
How Project Groups work
Project Groups can be used to:
-
Organize related projects
Multiple projects can be grouped together under a single Project Group, helping structure work across teams, research areas, or principal investigators (PIs) -
Manage collaboration across projects
When a project is part of a Project Group, collaboration settings can be configured so that all members of the Project Group can be added as collaborators to experiments within that project -
Enable cross-group collaboration
Users from other lab groups can be added to a Project Group, allowing collaboration across different teams
(Note: external users must belong to a licensed eLabJournal group)
What this means for your workflow
Project Groups allow you to manage multiple related projects within a single structure and apply collaboration settings more consistently. Instead of configuring access separately for each project, you can define it once at the Project Group level and apply it across all included projects.
Please note that users require the appropriate permissions to view or create Project Groups
Learn more about Project Groups here
Traceability and Compliance
Both platforms support traceability and regulatory compliance, with SciSure for Research offering a more comprehensive and structured approach to managing and controlling research records.
| Feature | Labfolder | SciSure for Research |
| Change tracking | Entry history shows what was added, edited, or deleted, along with timestamps | Tracks changes across records such as experiments, protocols, and samples, including who made the change, when it was made, and what was changed |
| Access to previous content | Previous entry states can be viewed, elements can be copied or downloaded from history | Earlier versions can be reviewed and compared (protocols) and restored (experiments) |
| Version handling | No full version rollback is possible | Provides structured version control for protocols (tracking, comparison, reuse) and controlled restoration for experiments |
| Electronic signatures | Electronic signatures are limited to entries | Electronic signatures can be applied to experiments, templates, and protocols, with traceability of signing actions |
| Export | Export entries/projects (e.g., PDF, XHTML archive) | Export experiments, studies, or projects in formats like PDF, HTML, JSON, XML, including all linked data and files |
In Labfolder, change tracking is available through entry history, and earlier content can be accessed or recovered manually by coping or downloading removed content.
In SciSure, this is handled in two distinct ways:
- Protocols use structured version control, allowing users to track changes, compare versions, and reuse previous versions
- Experiments support restoring sections, enabling users to revert to a previous state when needed
Electronic signatures in SciSure can be applied across experiments, templates, and protocols, with full traceability of signing actions. This supports controlled documentation and compliance workflows.
Learn more about electronic signatures and compliance
SciSure also provides expanded export capabilities, allowing users to export data at the experiment, study, or project level. Exports can be generated in formats such as PDF, HTML, JSON, and XML, and include all related data and linked files in a single package.
Learn more about exporting data in SciSure
Integrations and Extensibility
Both platforms support integrations with external tools and services, allowing users to connect their ELN with other systems and workflows.
| Feature | Labfolder | SciSure for Research |
| API | Open REST API for integrating external applications | Open REST API for integrating external systems and workflows |
| Developer tools | API-based integrations | Developer Hub and SDK (Software Development Kit) for building and managing custom integrations |
| External integrations | Integrations via API and selected tools (e.g., Dropbox, Figshare) | Prebuilt integrations with tools such as Protocols.io, CloneAssist, Microsoft Office Online, Google Drive, and Dropbox, along with additional add-ons |
What this means in practice
In Labfolder, integrations are primarily handled through its Open REST API, allowing data exchange with external systems. Integrations with selected tools are available, but extending functionality typically requires custom development.
In SciSure for Research, integrations are supported through a broader ecosystem:
- An Open REST API for connecting external systems
- A Developer Hub and Software Development Kit (SDK) for building custom integrations
- Prebuilt integrations with tools such as Protocols.io, CloneAssist, Microsoft Office Online, Google Drive, and Dropbox
This allows organizations to:
- build custom integrations tailored to their workflows
- connect with commonly used laboratory and data tools
- extend the platform as requirements evolve
Explore available integrations in SciSure
Mobile Access
| Feature | Labfolder | SciSure for Research |
| Mobile access | Mobile browser | Dedicated mobile app and browser access |
Labfolder can be accessed on mobile devices through a mobile web browser.
In SciSure for Research, users can access the platform both through a mobile web browser and a dedicated mobile application. The mobile app supports key tasks such as viewing and editing experiments, following procedures, scanning barcodes for samples or equipment, and capturing notes or images that sync with the platform.
Learn more about the SciSure for Research mobile application