Platform Backbone
Identity & Access
Robotics infrastructure is shared infrastructure across data, ML, platform, support, and field operations teams. Identity & Access define who can act inside rFabric, what scope they can act on, and how every critical action stays attributable.
What This Surface Owns
Authentication
Humans, services, CI workflows, and robot-side agents all need first-class credentials rather than shared secrets and informal access paths.
- SSO-backed user identity
- Service credentials for automation and integrations
- Device and robot credentials for edge activity
Authorization
Permissions follow real robotics workflows rather than generic app roles.
- Data and annotation actions
- Training and model-promotion actions
- Release, rollout, rollback, and fleet actions
- Intervention and operational escalation paths
Actor Model
Human users
Human actions need clear attribution because approvals, promotion, teleoperation, and maintenance are operationally meaningful events.
- Researchers, data operators, release managers, support, and field teams
- Role assignment mapped to real scopes and responsibilities
- Approval and escalation events attributable to named people
Service identities
Automation should not masquerade as a human session.
- Workflow runners
- CI and release automation
- Internal platform services
- Integration workers and partner systems
Robot and device identities
Robot-side activity has different trust and failure properties than human or service activity.
- Unique credentials for upload, telemetry, artifact delivery, and update coordination
- Device- or site-aware scope where appropriate
- Rotation and revocation without losing fleet continuity
Why Teams Care
Operational safety
Rollout, rollback, and teleoperation can be restricted to the right actors without leaving dangerous side paths open.
Reliable auditability
Critical lifecycle actions stay attributable across UI activity, API calls, workflow execution, and robot-side activity.
Clear separation of concerns
Identity & Access focus on actors and permissions. Structural isolation and policy inheritance belong to Governance & Tenancy.
Shared but safe adoption
Multiple teams can work inside one platform without collapsing into access sprawl or informal admin shortcuts.