Can a team or organization use LRO?

Yes. LRO works just as well for one person as for a whole team. You can start as a single user and keep it personal, or turn the account into an organization and bring colleagues in — sharing the same machines, permissions, billing and audit trail.

From a personal account to an organization

Any standalone account can become a corporate one: you give the organization a name, and your account becomes its first org-admin. From that point the account is no longer a lone user — it's the owner of an organization that other people can join.

Invite your team

An org-admin invites teammates by email. Each invite is a single-use, time-limited link; the recipient signs in (or signs up) and joins the organization. Members can also leave on their own, and the panel keeps a list of pending and recent invites so you can revoke one that hasn't been used.

Two roles: admin and member

Inside an organization a person is either:

• Org-admin — manages members and invites, and can see and manage every agent, endpoint and permission that belongs to the organization.
• Member — works with the agents and endpoints they own or have been granted, without the org-wide management view.

Promotion and demotion is itself a deliberate, audited action, so changing who holds the keys leaves a record.

Share machines, keep least privilege

Sharing is not all-or-nothing. Agents and endpoints are shared by granting per-user, per-endpoint permissions — optionally with an expiry — so each teammate reaches only the specific machines they need and nothing more. An org-admin has the full picture across the team; a member sees only their slice. That maps directly onto least-privilege and separation-of-duties expectations.

One shared balance

An organization has its own balance. The team's agents and their traffic are billed against that shared organization balance rather than against individual personal wallets, so finance is centralised — one place to top up, one place to track spend — instead of scattered across each person's account.

Who did what is on the record

Every organization action — invites issued and accepted, members joining, leaving and changing role, permissions granted and revoked, billing changes — is written to an append-only audit log scoped to the organization, with the acting user and their IP. For a team, that's the difference between “someone changed access” and “this person changed this access at this time.”