Robotair Organization⿻
Estimated time to read: 2 minutes
Concept Overview⿻
A Robotair Organization is a logical workspace that enables team-based collaboration and resource sharing. It acts as a container for all robots, builds, deployments, secrets, and configurations associated with your robotics operation.
Organization help structure access, enforce role-based controls, and allow for smooth multi-user collaboration across projects and teams.
Robotair Organization are also extensible you can invite users from outside your organization (e.g., partners, contractors) and give them scoped permissions.
Role in the Platform⿻
Organization form the security and governance boundary in Robotair. All actions, deployments, and telemetry are scoped to the organization to which the resource belongs. Each user has explicit roles and permissions that determine what they can view, modify, or control.
Robotair also allows cross-organization participation. For instance, a robotics vendor can share a robot or deployment access with a system integrator by inviting them to a specific org or sub-group.
Functional Capabilities⿻
- Invite and manage users within your organization
- Assign roles such as Admin, Developer, Observer
- Share builds, robots, fleets, and deployments internally
- Collaborate with external users by granting scoped access
- Centralize secrets, registry credentials, and CI templates under one org
Role Hierarchy and Collaboration Topology⿻
flowchart TB
subgraph Org[Acme Robotics Inc.]
A1["Alice
(Admin)"]
A2["Bob
(Developer)"]
A3["Carol
(QA)"]
A4["Eve
(DevOps)"]
end
subgraph Projects[Acme Robotics Resources]
R1["Robots"]
R2["Builds"]
R3["Deployments"]
R4["Secrets & Registries"]
end
A1 --> R1
A2 --> R2
A2 --> R3
A3 --> R1
A4 --> R2
A4 --> R4
subgraph External[External Collaborators]
E1["Dave
(Partner)"]
E2["Mina
(Integrator)"]
end
A1 -.-> E1
A1 -.-> E2
E1 --> R3
E2 --> R2
Robotair Organization provide a structured, scalable foundation for collaborative robotics software development. Whether your team consists of a few developers or multiple departments working with external vendors, Organization ensure proper access boundaries, auditability, and operational clarity across the full deployment lifecycle.