User Substitution in PDP: time off without stopping processes
In construction, deadlines don’t wait: the inspector goes on vacation, but site issues keep coming in. That’s why PDP implemented User Substitution — temporary employee replacement with task and access handoff.

In construction, deadlines don’t wait: the inspector goes on vacation, but site issues keep coming in just as reliably as notifications on a Monday 😅 So we implemented User Substitution in PDP — temporary employee replacement with task and access handoff.
How it works: for a specified period, the substitute gets the original user’s permissions and can keep working without pauses or manual workarounds. But there’s an important detail: all actions are logged separately. In other words, the system knows the access was “as the inspector,” but the actions were performed by someone else.
For us, this isn’t just a convenient feature, but a critical scenario for real construction workflows, where downtime means extra stress, money, and calls in the style of “so who is actually supposed to close this?”
Now that everyone in IT is focused on security, audit trails, and zero trust, mechanisms like this are no longer nice to have — they’re foundational.