Identity and access

The CLI and SDK use your saved sign-in:

your computer

servo login
servo whoami

On a headless machine, follow the printed link and code. servo logout signs out locally; servo logout --everywhere ends all your sign-ins. Connect your Hugging Face account to import checkpoints.

Robot identity

Python on the robot computer acts as the robot through the agent. Enroll that computer:

robot computer

servo agent install --name yam-cell-01

An organization admin approves its printed code with servo robot approve CODE --name yam-cell-01. --run keeps the robot agent running in the foreground after enrollment. Robot registration is not required for checkpoint inference. Grant a person access to a robot:

CLI
Python

your computer

servo access grant alice@lab.example --robot yam-cell-01 --role write
servo access list --robot yam-cell-01

Grant and list access:

your computer

import servo

sv = servo.Servo()
sv.access.grant("alice@lab.example", robot="yam-cell-01", role="write")
print(sv.access.list(robot="yam-cell-01"))

Role	Permission
`read`	Inspect robot and sessions
`write`	Start and stop robot sessions
`admin`	Grant and revoke access

Organization admins have admin access to all robots; organization API keys retain access to all robots. An organization member or API key can deploy and stop models. A Google Group can replace the email after an admin connects Google Workspace; group access requires Google to be reachable. Revoke access:

CLI
Python

your computer

servo access revoke alice@lab.example --robot yam-cell-01

Revoke the same grant:

your computer

sv.access.revoke("alice@lab.example", robot="yam-cell-01")

Open sessions recheck access when renewing. An organization admin can run servo robot remove NAME to revoke the robot’s installations while retaining its history.

Get started

Guides

Reference

Identity and access

Robot identity

​Robot identity

​Share access

Robot identity

Share access