Skip to content
Lazurio Documentation

Device approval

In Lazurio’s target model, an Organization that reaches its Environments through a tailnet lets in only devices its Admin approved (decision 0192). That decision is in force as the target, but the transition is not complete. How a device gets access today can still differ between tailnets, as Reach an Environment through Tailscale says. Your Admin, or your Organization’s own rules, tell you how it works in yours.

What you do

Section titled “What you do”

Register the device yourself: sign in to your Organization’s tailnet in the Tailscale app with your Lazurio account, as the Tailscale guide describes.

Registration alone does not guarantee access. If the Environment’s address still does not open, the device may not have access yet. Ask the Admin to approve or add it, and say which device it is and its name in Tailscale: see How to ask the Admin.

When you need no device in the tailnet

Section titled “When you need no device in the tailnet”
  • An Organization with public addresses (decision 0213) needs no tailnet and no device approval. You sign in with your Lazurio account, but only to the web interface: Launchpad, chat, MausBot and Buddy. There is no SSH and no phone pairing for people there.
  • A phone paired through the ChatGPT app, where your Environment offers pairing (Phone and computer). The phone needs no tailnet. You create the pairing code inside the Environment, though, so you must already be able to open it.

When you lose a device

Section titled “When you lose a device”

Tell the Admin at once, so they remove its access. If you paired the lost phone through ChatGPT, also remove it under Paired phones in Settings → Connections. In the target model you will be able to remove your own lost device yourself (decision 0192). Until Lazurio offers that, the Admin does it.

For the Admin

Section titled “For the Admin”
  • Approve a specific device by its record in the tailnet (node, key, owner), never by its name alone. A name can be changed and proves nothing.
  • Approving a device for the Organization’s Environments opens nothing in a person’s Personal Environment.
  • In the target model you approve and remove devices with a click in the Organization’s Dashboard. Until then the path depends on your Organization. Where it is in place, it is a reviewed change to the Organization’s server configuration. Your Organization’s rules say which path applies.