When the login leaves with someone

One person knows how the site works. When they leave, everyday updates become archaeology: shared passwords, old emails, and a freelancer nobody has called in a year.

Theatre websites often have a single owner in practice, even when the brand belongs to the company. One marketing manager set the site up with an agency. One freelancer still has the only admin account. One staff member is the person everyone writes to when a date changes.

That arrangement works until the person leaves. The handover is rarely a clean list of logins and a documented way to publish a show. It is a shared password in a notebook, an agency contact that bounced, and a WordPress dashboard nobody else has opened since the last season launch.

The next cast change becomes archaeology. Someone digs through old emails for “the website person.” Someone resets a password and breaks a plugin. Someone pays for a few hours of rescue work so a sold-out night can finally say sold out.

The risk was built into the tool. If publishing means understanding a general-purpose CMS, the company will keep that knowledge in one head. Everyone else will stay away from the publish button, because the cost of a mistake feels higher than the cost of waiting.

A theatre website should not depend on a single person’s memory of where the date field lives. The people who run the season should be able to open a production, change a name, and publish. The platform should carry the hosting and the updates. The company should keep more than one person who can press the button.

When someone leaves, the website should stay. The season does. The audience still arrives with the same questions. The login should not be the thing that walks out the door.

All posts

Early access

Theatre.show is in development.

We are building the first version now. Join the early access list to hear when it is ready and follow the development of the platform.

Join the early access list