Projects
Team workspaces and collaboration
Organize your lab work into projects. Each project is a focused workspace with its own members, experiments, protocols, and samples — with role-based access to keep everything tidy.
Overview
PCR Optimization v3
12 exp · 4 members
Antibody binding screen
8 exp · 6 members
Cell viability — Compound C
4 exp · 3 members
Method development — LC-MS
17 exp · 5 members
Project
PCR Optimization v3
12 experiments · 4 members · updated 2h ago
Members
Sarah Chen
Marcus Webb
Priya Nair
Jonas Müller
Recent activity
S. Chen updated experiment "PCR Run #14"
12m ago
M. Webb commented on "Gel Electrophoresis"
2h ago
P. Nair attached protocol "PCR Standard v2"
4h ago
S. Chen created experiment "PCR Run #14"
1d ago
Scope
Visibility
Org members: read-only
External: none
Role-based access
Owner, Editor, Viewer. Grant the right level of access to each member without complex configuration.
Scoped workspaces
Experiments, protocols, and samples are scoped to their project. No cross-project noise.
Team management
Invite org members to projects instantly. Remove or change roles at any time.
Cross-project visibility
Org admins see across all projects. Researchers see only what they're part of.
Designed for how labs work
Projects map naturally to research initiatives — a grant, a product line, a collaborative study. Everything stays contained.
Activity and history
See recent activity across the project — who ran what, when experiments were updated, and what changed.
Scale from one to many
A single scientist runs one project. A 200-person org runs dozens. NextLabs scales with you.
Built for real lab workflows
Grant-funded research
Each grant is a project — its scope, members, and deliverables stay contained. When the grant ends, archive the project as a self-contained unit ready for any audit or follow-on application.
Industry collaboration with external partners
Bring partner scientists into a single project without giving them access to the rest of your org. They see what you intend them to see, contribute under their own identity, and lose access cleanly when the collaboration ends.
Internal R&D programs
A drug discovery campaign has one project. Each target inside the program has experiments, protocols, samples, and inventory scoped to it. Cross-program insight is admin-only — researchers stay focused on their target.
Educational and teaching labs
Each rotation, course, or thesis project is its own workspace. Students see only what is theirs. Instructors see all rotations. Onboarding a new cohort takes minutes instead of half a day of permission setup.
Works with your existing tools
Projects act as the unit of work that everything else attaches to. The integrations you set up at org level apply across projects, and project-specific tools sit underneath.
- Slack channel mapping per project for activity notifications
- Google Calendar two-way sync for project meetings and milestones
- Per-project Google Drive folder for shared external files
- GitHub-style activity feed of all changes across the project
- Role-based access — Owner, Editor, Viewer with optional custom scopes
- API tokens scoped to a single project for downstream pipelines
Frequently asked questions
Can a person belong to multiple projects?
Yes. Each project membership has its own role. A senior researcher can be Owner of two projects, Editor on three more, and Viewer on a fourth — all without any conflict in permissions.
What is the difference between organization and project?
An organization is your company or lab — billing, members, branding live here. A project is a focused workspace inside the org with its own data and access. Most labs need one org and many projects.
Can external collaborators join a single project?
Yes. Invite them as project-only members. They see no other projects, no organization-wide data, and lose access when removed. Common for industry-academia and multi-institution work.
How do we archive a finished project?
Projects can be archived to read-only — data preserved, no new edits accepted, members notified. Archived projects do not count toward active project quotas. Unarchive at any time if the work resumes.
Can org admins see across all projects?
Yes. Org admins have read access to every project for compliance, audit, and rollup reporting. Write access still requires explicit project membership — admins can see, but cannot silently modify, project work.