Cloud PlatformTeam Collaboration

Team Collaboration

Team and Enterprise tiers turn BioNodulo into a shared lab environment: members, roles, shared workflows, and (on Enterprise) institutional login and audit logs.

Workspaces

A team workspace is a shared space for workflows, runs, and storage. Members of a workspace can see and (per their role) edit shared workflows, while keeping personal drafts private.

Members & roles

RoleCapabilities
OwnerBilling, members, all workflows, workspace settings
AdminManage members and workflows; cannot change billing
MemberCreate, edit, run, and share workflows
ViewerRead-only access to shared workflows and run results

Team tier includes 5 members; Professional includes up to 3; Enterprise is unlimited.

Inviting members

Owners and admins invite collaborators by email from the dashboard (Team section) or via POST /api/team/invite. The invitee receives a branded invitation email (sent by Clerk Organizations) and joins the workspace on accept. Inviting someone as admin requires an owner or existing admin.

Sharing workflows

  • Share links, create a per-workflow link with a viewer (read-only) or editor role. Guests open the workflow in the cloud editor without an account; editor-role guests can also run it, billed to the owning team’s credits. Links can have an expiry and a max-use count, and can be revoked at any time. See Sharing & collaboration.
  • Within a workspace, teammates can see, run, and iterate on team workflows per their role.
  • Export/Import, hand a workflow JSON to anyone, on any tier, including desktop users.
  • Versioning, shared workflows keep a version history so a teammate’s change never silently overwrites your work.

Shared resources

  • Pooled credits. A workspace draws from a shared credit balance.
  • Shared storage. Team files (uploads and run outputs) live in one team-scoped object store. Storage is metered at 3 credits per GB-month beyond the included allowance (5 GB on Free); there is no cap, teams pay for what they keep.
  • Concurrent jobs. Higher concurrency limits let multiple members run at once.

Enterprise add-ons

  • SSO / SAML for institutional login.
  • SCIM directory sync for automated provisioning/deprovisioning.
  • Audit logs (SIEM-ready) of workspace activity.
  • Data residency selection (EU, US, or APAC).
  • Private node registry is planned for proprietary nodes after the registry service is implemented.

See also