One working system
A starter set up and a leaver closed out, step by step.
We have no IT person, so accounts and laptops fall to the office manager.
IT operations desk
A starter, leaver or access request is checked against the company's written policy and carried out step by step on a sample directory, risky access waits for the person the policy names, and a morning check lists what needs fixing.
What it does
Form, policy, steps, close out, in four steps.
A starter form arrives
The form gives a name, a role, a manager, a first day and one extra system asked for. That is all the desk needs to plan the work.
Every line of the policy is applied
Standard accounts come first, then what the role adds. A free licence is confirmed on each system, and a laptop is picked from stock only if it is encrypted and recently updated; an older one is passed over with the reason shown.
The steps are carried out and written down
Accounts are opened one by one and the licence counts move as they are used. The log gains a row for each step, including the one left for a person and the one still waiting.
A leaver is closed out in the same manner
Sign in is blocked across the leaver's accounts, mail is forwarded to the manager until a set date, and the licences return to the pool. Handing over admin rights waits for the partner the policy names.
Ownership
You own it. All of it.
A checklist that runs the same way every time is worth more than the software under it. Yours would be written from your own policy and kept in your accounts, with a log that shows what was done for every person who ever joined or left.
Hire or own
What the hire costs, and what this costs
Add up how much of the advertised job is joiners, leavers and access. That portion can be delivered as a system at a fixed fee, so the administrator you bring in is not spending Mondays on account forms.
What this role is paid, and what that comes to with benefits, is on the systems administrator salary page.
When the hire is the right call
A systems administrator is the right hire when you run servers, a network and equipment that need hands and judgment on site. The desk does not patch a server, trace a network fault or answer the phone when something is down.
Read this first
What you are looking at, said plainly
Demonstration system, sample data
Nothing here touches a real directory. The people, accounts, laptops and licences are sample rows, approval is a button with no sign in, and the leaver form handles a last day of today only. The clock on screen is a label and no speed is claimed.
What it costs
Three public prices. Nothing per user.
Jim Glaser Law takes reference calls.Ask in your note and we set it up.
One step
Send me a version customized for my company
Questions buyers ask
Before you ask for your version
Is this connected to a real directory?
No. The demonstration runs on a sample directory inside the app. A version for your company is built against the directory you use, after scoping.
Does it do everything a systems administrator does?
No. It covers starters, leavers, access requests and a morning check, a core part of the role. Servers, networks, hardware faults and projects stay with a person.
What stops it making a mistake with access?
The written policy. Each request is checked line by line, anything outside the role is held for the manager with an end date, and the same starter cannot be set up twice.
What does the morning check cover?
Backups that failed overnight, licences due to renew and laptops behind on updates or not encrypted, each with a suggested fix. On the demonstration these act on sample data.
What does a customized version look like?
The same desk with your roles, your systems and your policy wording, running on invented staff. It is built without access to anything of yours.