Carbon

    Platform

    Team & Access

    Governance by default

    Permissions, projects, and lab governance. Roles and resource permissions keep sensitive rigs and datasets where they belong, with an audit trail throughout.

    Shared instruments and shared data need rules that match how a lab actually works, PIs, staff, students, and auditors all touching the same benches with very different latitude. Carbon models that directly, scopes access down to individual rigs and datasets, and records every action against a name.

    Role-based access
    RBAC
    Role-based access
    Level permissions
    Resource
    Level permissions
    Action audit trail
    Full
    Action audit trail

    Roles that match the lab.

    PIs, staff, and students get the access their work requires, no more, no less.

    Isolation where it matters.

    Resource permissions keep restricted instruments and datasets inside the projects that own them.

    An audit trail by construction.

    Commands, edits, and access decisions are recorded, review is a query, not a quarter-long scramble.

    RESOURCE ACCESS · TEAM ROLESCRYO RIGRF BENCHDATASETSANALYSISBILLINGOWNERRESEARCHERSTUDENTAUDITORFULLREADNONECUSTOM ROLES SUPPORTED

    How it works

    01

    Model

    Define roles that match the lab, PIs, staff, students, auditors, each with custom permissions.

    02

    Scope

    Resource permissions keep sensitive rigs and datasets inside the projects that own them.

    03

    Audit

    Every command, edit, and access decision is recorded and queryable after the fact.