The client portal
A client contact reaches their portal by a link rather than by making an account, because the person who approves timesheets at a hirer will not create a password to do it.
- Weeks waiting on them, signed off in one act or sent back with a reason.
- The vacancy brief, with a trail of their own requests against it.
- Sent invoices, and nothing that has only been raised.
- The compliance position on the people working for them, as status rather than evidence. The underlying documents stay with the agency, because they are the agency's obligation and often somebody else's personal data.
The worker portal
Contractors and agency workers get their own passwordless way in, and it is where the paperwork the law says they receive actually lands.
- Their rota, with shifts to accept or decline.
- Their own weeks, entered by them where the agency works that way, joining the same approval chain.
- Their documents: the Key Information Document, the assignment confirmation, and anything else issued to them.
- Change requests, so a change of address or bank details is a request the agency actions and the record remembers, rather than a text message somebody forgets.
- Roles put to them, which only they can accept. Acceptance creates the application through the ordinary door with consent recorded.
Nobody sees another agency's anything. Every table carries the tenant, every query is scoped to it, and a portal link opens exactly one record.
Data rights
Consent is captured with the wording it was given under, so what somebody agreed to is recoverable rather than inferred. Subject access exports, retention and erasure are all real acts on the record, and erasure knows when the law says a record has to be kept.
Walk in as each of them
The demo opens all three faces on one agency: the staff desk, a client and a worker. Nothing in it is real.