Account
Access and team
Who can use TrialONE, and how a team works in one workspace.
Access is by request
We onboard a few robotics teams at a time, and a founder approves each one by hand. Request access with your work email. You can sign in with Google, GitHub or email before the approval; until it arrives the app shows where your request stands.
Keys
| Key | Starts with | For |
|---|---|---|
| CLI key | t1cli_ | A robot or laptop that runs TrialONE and posts runs. One per machine, under Settings, CLI keys. |
| Agent key | t1mcp_ | A coding agent over MCP. It reads issues and reports repairs, and cannot post runs. |
The database keeps only a hash of each key, so a key is shown exactly once. A revoked key can no longer post runs, and the machine that used it stops running TrialONE at its next daily check.
A team
A workspace is one account that several people work in. Invite people by email under Settings, Team. An invitation arrives by email, and when the address already has an account it also waits inside the app.
| Role | Can |
|---|---|
| Owner | Everything, including the workspace itself. |
| Admin | Invite and remove people, and see and revoke the keys of everyone in the workspace. |
| Member | Work on issues, assign them, and create their own keys. |
Issues can be assigned to a person, and every action (a claimed repair, a state change, an assignment) is kept with who did it.
Something missing or wrong here? Tell us.