← All posts

Project Server and Project Online

Project Server: keeping control of user accounts

Over the years, a Project Server environment piles up accounts: departures, transfers, contractors. Reviewing them regularly serves security, licensing and accurate workload plans.

The PM SIDE team · November 12, 2026 · 4 min read

A Project Server environment lives a long time. People arrive, change teams, leave. Their accounts stay. After a few years, nobody quite knows who has access to what.

Why it matters

  • security: an account left active after a departure is an open door;
  • licensing: every unnecessary account can cost money;
  • workload plans: a departed resource still assigned distorts the team's capacity.

A review in three questions

An account review is not complicated. For each account, three questions are enough: is the person still here? Have they logged in recently? Do their rights match their current role?

The answers sort quickly: active and correct accounts, accounts inactive for a long time to check with managers, and accounts of people who have left to disable, after reassigning their ongoing tasks.

How often

A full review once or twice a year, and a check at every departure. It is one of the maintenance tasks we carry out for the Project Server environments we support, along with monitoring backups and performance.

See these screens in Henry, on your own cases?A 30-minute demonstration, on projects close to yours.
See Henry, 30 min

A question about Henry, More With Project or Project Server? Let's talk.