Use cases

Six moments where keys and electronic access meet.

In each use case, portierX applies one decision to the mechanical keys and the connected access control systems, and keeps the record.

Someone leaves or changes role

People leave. Access does not. Their cards are blocked in the connected systems, and every key is followed up until it is back.

Explore use case

A contract ends. The person's card is blocked and their key is followed up. Someone brings the key back, the return is recorded, and all access is removed.

Contractors

Each contractor has a sponsor and an end date. When the work ends, cards stop and keys come back.

Explore use case

A contractor has a sponsor and an end date. When the work ends, the card is blocked and the sponsor answers for the key, brings it back, and once it is returned all access is removed.

Keys across depots and sites

Every key and copy is tracked across depots, key safes and issuing desks, against the person who holds it and next to their cards.

Explore use case

Keys are kept at three sites: a depot, a key safe and an issuing desk, where the card was issued. A key is issued from the depot with a signed handover, then a second key from the key safe, and both land on the same person's record next to their card.

A key goes missing

portierX reads what the key opens from the key plan, names who has to act and tracks the follow-up until it is done. A lost card or electronic key is blocked in its own system.

Explore use case

A key and a card are both lost. The loss is recorded, the card is blocked in its own system, the key plan shows the five doors the key opens, and an owner is named for the follow-up.

Protected areas

Every key and card that opens a server room or plant room, master keys included. Access needs approval from whoever answers for the room.

Explore use case

A server room and everything that opens it, master keys included. A key is requested for a technician, the room's owner approves it, and it is issued.

Reviews and audit evidence

Owners confirm who still needs each key and card. The record from request to removal is there when the auditor asks.

Explore use case

An owner reviews who still needs each key and card. One key is still needed, a card that is not needed is blocked, a master key that is not needed is followed up, and the record runs from request to removal.