The right access, with an audit trail
Invite your whole team, plus your kwaliteitsborger, with precise role-based permissions. The platform then logs every change on its own. Owner, editor, viewer, and inspector roles control who can see and do what. Meanwhile an audit trail builds the who-did-what history that any project record needs to hold up when someone checks it, on a Wkb project or any other.
Open access and no record is a liability
Construction projects involve many hands: the contractor, subcontractors, the client, the kwaliteitsborger. Without role-based access, every one of them can change anything, including records that are supposed to stay fixed. And without a log, you can't show who did what or when. On any project that has to stand up to scrutiny that's a real liability, and under the Wkb the dossier has to demonstrate a controlled process. An editable history with no accountability is exactly what a reviewer won't accept.
Role-based access plus a running log
- Give each member a role that fits their job: owner, editor, viewer, or inspector.
- Permissions decide what each person can see and change across the project.
- Every change is recorded in an audit trail you can hand to the bevoegd gezag.
- Invite your kwaliteitsborger and external parties with exactly the access they need, nothing more.
Key capabilities
Role-based permissions
Owner, editor, viewer, and inspector roles set what each person can see and change, so access matches the job.
Scoped invitations
Invite your team, client, and kwaliteitsborger with the access their role needs, and nothing it doesn't.
Project-wide audit trail
Every change is logged with who and when. That's the defensible history any project record needs, and exactly what a Wkb dossier has to show.
Built for scrutiny
A controlled, accountable record is what a client, an auditor, or the bevoegd gezag expects when the record comes up for review.
Frequently asked questions
- What roles can I assign to team members?
- You can assign owner, editor, viewer, and inspector roles, each with a different level of access. Permissions then decide exactly what every person can see and change across the project.
- Can I give my kwaliteitsborger limited access?
- Yes. You can invite external parties, including your kwaliteitsborger, with the access their role needs and nothing more. They can do their job without seeing the rest of the project.
- Is there a record of who changed what?
- Every change is captured in a project-wide audit trail with the user and timestamp. That gives you an accountable, defensible history that holds up under review, whether it's a client, an auditor, or the bevoegd gezag checking a Wkb dossier.
For whom
A visual tour of the workflow.