Lifecycle
Named company instances with onboard queues, inventory, shipping, and a portal for people who are not on the desk — signed in with Microsoft or on-prem AD.
Why Lifecycle
HR opens the hire. IT runs provision stages. Inventory stays attached to the person. Shipping labels and portal links go out from the same ticket. Finance sees cost when it matters. Dev keeps the cluster healthy.
How it works
01
Onboard, change, or offboard starts on the HR desk with the people and dates that matter.
02
Provision accounts, licenses, and gear on one queue — instructions and runbooks stay with the work.
03
Assets, serials, labels, and tracking stay on the employee record — not a side spreadsheet.
04
Transfers and returns land on a focused portal so people who are not staff never need the full desk.
Desks
After sign-in, staff switch with the Desk control. Access is granted under Settings → Access — no shared “god mode” by default.
Queue, provision stages, inventory, shipping, servers, and runbooks — from hire through return.
Open lifecycle tickets, keep the roster current, and hand work to IT without losing the thread.
Dollar costs and justifications for operators who need FIN beside the IT queue.
Cluster operators manage hosts, uptime, desks on the pool, and join tokens for another node.
Instances & directory
Name an instance on lifecycle.lol — for example contoso.lifecycle.lol. Hosted desks sign in with Microsoft 365 / Entra using a company domain. On-prem installs can prefer Active Directory from Settings → Connections.
End-user portal
Employees get a focused path for transfers and replacements — without a staff login to the IT queue. Links land on portal.lifecycle.lol so the desk stays for operators.
Tokenized portal flows keep shipping and asset handoffs clear for the person holding the device.
Shipping & inventory
Create labels, capture tracking, and remind employees from the ticket — including portal links when they need to act.
Asset numbers, serials, warranties, and assigned users — export when you need a spreadsheet; keep the source of truth in the desk.
Operations depth
Stages, instructions, and urgency live on the ticket so IT and HR see the same path from open to done.
Connect Entra or on-prem AD, prefer a sign-in path, and send desk mail for portal links and return reminders.
Runbooks for servers and lifecycle-svc stay with the operators who need them — not buried in a wiki.
Tenancy
Each desk is a named instance on the pool — staff open their hostname, not a shared multi-tenant chrome. Microsoft sign-in on hosted paths requires a company domain. Help stays on every host so operators never leave the desk to learn the product.
Instance-scoped desks on lifecycle.lol
Microsoft Entra or on-prem Active Directory
Portal tokens for employee actions — not desk credentials
Who it is for
Grant roles, connect directories, run the queue, and keep inventory honest as people join and leave.
Open onboard and offboard without chasing IT in email — the ticket is the handoff.
Watch hosts, capacity, and join tokens from Dev when you run more than one node.
Create instance
Each Setup.exe box is a node. Naming a desk assigns it to a node with spare capacity — this host if it is the only one in the pool. Staff open name.lifecycle.lol; this apex site stays for create and sign-in.
Live on this host
demo.lifecycle.lol
The IT / HR desk on this node. Staff on the LAN can still use the hostname from Setup.
Open the demo deskRecorded names
No other names yet. Demo stays on this node until another host joins.
Ready
Create on lifecycle.lol, or open Help if you are installing with Lifecycle-Setup.exe on your own host.