BCINexus · Working together
Teams, labs & enterprise
A team is a private workspace that sits before publication. Work shared into one is visible to its members and to nobody else — it is not a soft form of publishing.
Teams and labs
- 1
Create the team
The creator becomes its owner. Team plan and seat limits come from the plan behind it.
- 2
Invite members by email
Invitations are accepted from the invitee's own account, so membership is always tied to a real, verified user.
- 3
Share studies and datasets in
Sharing a study to a team gives members access under their team role. Nothing becomes public as a result.
- 4
Work, then publish from it
When the work is ready, it goes through the same submission and review path as anything else.
Team roles
| Role | What it can do |
|---|---|
| Owner | Everything, including billing, seats, and deleting the team. |
| Admin | Manage members and shared content. Can leave internal comments on work authored by team members — those comments are never shared with anyone outside the team, and an admin cannot approve or publish anything. |
| Editor | The working default. Create, edit, and contribute to shared studies and datasets. |
| Reader | View and download shared content. |
Roles are presets, not walls
Each role expands to a permission set, and individual permissions can be overridden per member when the preset is not quite right. The override wins where it is set.
Per-study collaboration roles
Individual studies carry their own collaboration roles — owner, admin, researcher, reviewer, and viewer — which are independent of team membership. That is how you bring one external collaborator onto one study without adding them to the whole lab.
Other ways to share
- Team workspace
- Ongoing collaboration with a stable group. The right default for a lab.
- Cloud package
- A packaged export of a study for handing to someone outside the platform.
- Publication
- The public record. Irreversible in practice — see corrections in moderation and integrity.
Details of local study sharing and dataset manifests are in the BCILattice lab plan guide.
Enterprise
The enterprise layer exists for institutions that cannot run on a consumer sign-up flow — universities, hospitals, and medtech companies with procurement and compliance obligations.
- Single sign-on through OIDC or SAML, with a default role applied to newly provisioned users and an allowlist controlling where sign-in may redirect.
- SCIM provisioning, so joiners and leavers are handled by your identity provider rather than by hand.
- Custom seat and team limits instead of plan-fixed ones.
- Audit logs covering authentication, publication transitions, review decisions, moderation actions, and licensing events.
- On-premise and air-gapped deployment where data cannot leave your network at all.
- Compliance-readiness review and a support contract with a defined response time.
Getting started with enterprise
Procurement, security questionnaires, and DPA review are handled directly. Start from the enterprise guide or talk to engineering.
Related
Something missing or out of date? Email support or request a doc page. Include the page name and what you expected to find.