Overview
The numbers for this server right now: how many people have accounts, who is active, what the work looks like, and which app builds are in use.
People
Everyone who can sign in to this server, people and AI agents alike. On a server with passwords, Set temporary password gives a person a one-time password they replace at their first sign-in. Off-board… moves what a person leaves behind — their open tasks and the workspaces they own — before you deactivate them. Roles: Member works, Manager also manages workspaces, OrgAdmin can open this page.
| Name | Role | Active | Agent | Last seen | Build | Joined via |
|---|
Workspaces
Every shared workspace of your organization, its owner and how many people are in it. Hand over… gives a workspace to another person — when its owner leaves, or should no longer run it. They become its owner without being asked and are told once; the previous owner stays a member and its delegates stay delegates. An administrator sees the workspace, its owner and its size — never its tasks.
| Workspace | Owner | Members |
|---|
Join codes
A short code you give somebody so they can create an account on this server. Pick the role they get, how many people may use the code, and when it stops working. Revoke a code the moment it should not work any more.
| Code | Role | Uses | Created | Expires | Status |
|---|
Invite links
A link that puts a person straight into one shared workspace. Best for someone who has no account yet: they open it on their phone or computer and land in the right place. Rotate replaces the link; Revoke ends it.
| # | Workspace | Uses | Created | Expires | Status |
|---|
Integrations
Connect this server to Jira or Azure DevOps so tasks can be created there from LoopTo. Available on the self-hosted enterprise edition.
Company sign-in
Prove your email domain with a DNS record, connect your identity provider, then — when a test sign-in has worked — require it for your people.
This server does not issue licences — it only checks the one it runs under. Licences are issued on LoopTo's own server.
What is what
Hosted server (api.loopto.me): LoopTo's own server, where accounts live for people who did not install their own. Self-hosted server: a company installs the downloadable server on its own machine; its people point the LoopTo app at it. Both are the same software.
Token (personal access token): a long secret string that signs a person's app in — like a password the app keeps. Issue a new one when somebody lost theirs. Join code: a short code for creating an account. Invite link: a link into one workspace.
Installing a licence (self-hosted server): the page "This server's licence" — paste the text LoopTo sent, press Apply. Renewals the same way. No file copying, no restart.
Plan (hosted server only): what a company on this server may add — Free is 10 people, 3 shared workspaces, one agent per person in each workspace, 1 GB; Paid is unlimited. Switched on the Customers page after they pay. A limit stops adding, never working.
Licence: only for a self-hosted server — a signed file saying which company, which size band (up to 25 / 100 / 500 people, or unlimited), until when. The app needs no licence. A customer on this hosted server has no licence file: their limit is the plan on their account (free up to 10 people, then a flat monthly price).
Roles: Member works; Manager also runs workspaces; OrgAdmin can open this page. On LoopTo's own server this page is additionally limited to named accounts.
What an administrator sees: this organization's people, workspaces and settings — never anybody's tasks. In the app an administrator sees exactly what a member in their place sees: their own tasks, the ones looped to or through them, and the whole of a Managed workspace they own or are a delegate of. Workspaces → Hand over… gives a workspace a new owner; People → Off-board… moves what a person leaves behind.
Password (a self-hosted server only): people sign in with their email and a password. Someone who forgot theirs gets a temporary one from People and chooses a new one at the first sign-in. The hosted server keeps Google and tokens.
Company domains (LoopTo's own server only): on a customer's licence, the email domains that company uses and the address of its own server. The LoopTo app asks this server where an email's domain signs in — it sends only the domain, never the address — and opens the company's server by itself; this server refuses to open a new account for those domains and points to the company's server instead. Accounts that already exist here keep working — unless you tick Block existing accounts too beside the domains: then every sign-in of theirs here (Google, tokens, the apps, MCP) points to the company's server, and their open sessions end within 15 minutes. Anyone can ask about a domain, so a routed domain's server address is not a secret.
Email domains (a self-hosted server): your company's email domains and the address your people reach this server at. This server sends them to LoopTo by itself — the domains, the address and its licence, nothing about people — and LoopTo approves each change; from then on, people who sign in to the app with those domains find this server by themselves. A server with no internet shows the list to send LoopTo by hand.
Microsoft Entra (a self-hosted server only): people sign in with their Microsoft work account. The company's IT team decides who may sign in and how, in Entra; this server checks each sign-in came from that tenant, for that app, and makes an account at a new person's first sign-in within the licence's size band. Entra only turns passwords off for everybody except the first admin — the way back in if Microsoft sign-in ever breaks.