The air in the small office smelled of scorched dust and cold coffee. It was the scent of a laptop fan working too hard on a humid Thursday afternoon. Leah sat in her chair and the fabric was rough against the backs of her legs. She was tired and the rebrand of her career-coaching site was nearly finished.

She opened the user list to delete the accounts she used for testing and she saw the name. The name was dev_tom. The role was Administrator. The last login was three weeks ago.

Tom had built the booking flow fourteen months ago. He was a good developer and he had worked through a weekend in March to fix a broken payment gateway. Leah had paid him and she had sent him a gift basket and she had never thought about him again.

Now his name was on her screen and the date of his login was recent. The site was quiet and the house was quiet but Leah felt a sharp pulse in her neck. She wondered why Tom was there. She wondered if he was looking at her revenue or her client list or the draft of her new book.

The Invisible Digital Key

She opened a new email window and she typed a sentence. She asked Tom if he was doing well. She stopped and she deleted the sentence. She typed a new sentence and she asked Tom why he had logged into her site last month. It looked like an accusation and she deleted that too. She sat in the heat of the office and she felt the weight of the digital key she had never taken back.

The problem was not Tom and the problem was not Leah. The problem was a system that only understands how to give everything or nothing. When Tom started the job he needed to see the settings and he needed to edit the code. Leah had two choices. She could give him her own password and her own identity. She could create a new account and call him an Administrator. Both choices were permanent and both choices were dangerous. She chose the new account and then she forgot the account existed.

Noah B.-L. is a thread tension calibrator and he knows about the points where systems fail. He looks at machines and he sees where the metal pulls too thin. He says that a system under constant tension will always snap at the place where a human has to remember a task. If the system does not end the access then the human must remember to end the access.

Humans are busy and humans are tired and humans do not like to have difficult conversations with people they used to trust.

In a survey of small business owners who manage their own websites, eighty-two people out of a hundred admitted they would rather leave a dormant account active than send an email that might sound suspicious. They value the social peace more than they value the digital lock. They see the name in the list and they feel a ghost in the room and they close the tab. They hope the ghost is friendly and they hope the ghost is not looking at the vault.

The Marriage of Access

The software we use to run our businesses treats access like a marriage. It is built for a world where people join a company and stay for twenty years. It is not built for the contractor who comes for three days to fix a CSS bug.

There is no button for “Access for forty-eight hours” and there is no button for “One-time entry.” There is only the crown of the Administrator. Once you put the crown on a stranger’s head it stays there until you take it off by force.

Taking the crown off feels like an act of aggression. Leah remembered Tom’s help and she remembered his kindness when the site crashed. To delete his account felt like she was firing him a year after the work was done. It felt like she was telling him she no longer trusted him. This is the social tax of poor software design. It turns a routine security task into a personal insult.

The standard response from security experts is to blame the owner. They say you must have a process and they say you must be diligent. They are wrong. Diligence is a limited resource and it is spent on clients and it is spent on taxes and it is spent on the actual work of the business.

A system that requires a human to be perfect is a broken system. The architecture of the web has a gap in the middle. It has the owner and it has the permanent guest and it has nothing in between.

We live in a world of shared keys. We share the keys to our houses and we share the keys to our cars and we share the keys to our data. When you give a physical key to a neighbor you know they have it. You see them in the driveway and you remember the metal in their pocket.

A digital key is invisible. It does not jingle and it does not take up space. It sits in a database and it waits for a login. It is a door that stays unlocked long after the guest has gone home.

Tom might have logged in by mistake. He might have been looking for a snippet of code he wrote a year ago. He might have clicked a bookmarked link and his browser filled the password and he was inside before he realized where he was. It is rarely a crime but it is always a risk.

The risk lives in the silence between the two people. It lives in the “Hi Tom” email that never gets sent.

The solution to the ghost in the user list is a system that understands time. It is a system that knows that a job has a beginning and a job has an end.

It is a tool like HMDIA which allows for session management and force logouts and temporary access controls. When the software handles the exit the human does not have to be the villain.

The access expires and the door locks and the relationship remains intact. There is no email to write and there is no awkwardness to navigate.

Leah looked at the screen and she looked at the “dev_tom” line. She felt the sweat on her palms. She did not want to be a person who was afraid of her own website. She did not want to be a person who suspected a friend of spying.

She clicked the checkbox next to his name and she hovered over the “Delete” option. She hesitated and then she clicked it. She told the system to attribute all of Tom’s old posts to her. She confirmed the choice.

The name disappeared. The list was shorter. Leah felt a small relief and then she felt a small guilt. She had closed the door but she had done it in the dark. If she had used a system that managed the session for her she would have felt nothing at all. She would have finished her coffee and she would have closed her laptop and she would have gone for a walk in the humid air.

Security is often framed as a battle against hackers and a battle against thieves. It is actually a battle against the friction of being human. We leave doors open because closing them is a chore. We leave accounts active because deleting them is a confrontation. We allow the standing risk to exist because we do not have the energy to manage the “Administrator” crown.

The Cost of “Forever”

The ghost in the user list is the price of a system that only knows how to say forever.

The next time you hire someone to fix a page or update a plugin you should think about the exit. You should think about the moment the invoice is paid and the work is done. If your software does not give you a way to limit the time then you are not just hiring a developer. You are inviting a permanent resident into your business. You are giving away a part of your house and you are hoping they never decide to move in.

The rebrand was finished and the site was clean. Leah walked to the window and she opened it to let in the breeze. The smell of the scorched dust was gone. She was the only administrator now. She had the only key. It was a lonely feeling but it was a safe feeling.

She wondered how many other sites Tom was still logged into. She wondered if those owners were staring at their screens and typing emails and deleting them. She hoped they found a way to close the door without feeling like they were breaking a heart.

“The web is built on trust but trust is a heavy thing to carry alone. We need tools that carry the weight for us.”

We need systems that know when the job is done even when we forget. Until then the user list will stay full of ghosts and the owners will stay full of questions. The laptop fan whirred and the room was still and the digital world waited for the next login.