Skip to content
CogniYukti

Portals

Every tracker has a candidate portal. Almost none of them answer a data request.

Most of what a candidate emails a recruiter about is status, an offer, or their own data. Two of those are ordinary. The third is the one that decides whether a DPDP obligation is a screen or a person's Tuesday.

Start with the honest framing

A candidate portal is not a differentiator, and we do not claim it as one.

Everybody has one. So the question is not whether it exists but which four things it actually does, and we would rather list four true ones than five that read better.

They can see where each application stands. They can accept or decline an offer, with a reason on the decline that lands on the record. They can apply to another opening in one tap. And they can exercise their own data rights, which is the part worth the rest of this page.

  • One tap to another opening

    Every listing is flagged with whether they have already applied, and applying twice returns the same application rather than a second one.

  • Every identity they have with you

    Somebody who applied twice under two records sees both, rather than whichever one the magic link happened to resolve.

  • A deliberately narrow interview view

    When, where, the stage, the focus areas, the panel size — and no interviewer names, so a last-minute swap is not a broken promise.

  • Referrals, and chains of them

    A candidate who was not right often knows who is, and the chain is walked back when a hire produces a bounty.

The part that is not table stakes

A data request that is answered, not acknowledged.

An access request runs immediately and comes back with a count per category, then a download link that expires. An erasure request runs immediately too, and reports what it cleared.

And where it cannot run, it says so to the candidate's face: a record under legal hold is refused, with the reason. That refusal matters more than the success case. A product that quietly queues an erasure it is not allowed to perform has made a promise on your behalf that you will be the one to break.

Access requestanswered now
  • Applications3
  • Interviews5
  • Documents2
  • Messages0
  • Consents recorded4
A count per category, then a download link that expires. Not a ticket, not an email promising fourteen days.
Erasure requestrefused

This record is under a legal hold and cannot be erased while the hold is in place.

The refusal is the feature. A product that silently queues an erasure it cannot perform has made a promise on your behalf that you will have to break.

Without a hold, the erasure runs and reports back what it cleared — keeping the consent record, so you can still prove what was agreed.
Illustrative
  • Erasure keeps the proof it was consented

    The personal detail goes; the record that consent existed stays, so you can still answer an auditor about a person who is no longer in your database.

  • Retention is per client, strictest wins

    Somebody submitted to two clients purges on the earlier deadline — and never while they have a live application anywhere, or a hold.

Scope, stated

What it does not do yet.

Can candidates schedule and reschedule their own interviews?

Not from the portal on their own initiative. When a recruiter sends a self-schedule link, the candidate picks a time in one tap from inside the portal, already signed in. There is no rescheduling and no live availability check — that is a real gap and we will not demo around it.

Can they sign the offer there?

They accept or decline, with an optional reason on the decline, recorded as candidate-initiated. Electronic signature sits on the letter path, which is a different surface.

Can they manage consent from the portal?

No. Data access and erasure requests, yes. Consent itself is captured elsewhere and is not a portal control today.

Can they edit their own profile or upload documents?

Not today. What they can change is their application state through the actions above.

Can candidates see internal notes, or who submitted them?

No. Internal notes, attribution, the vendor who represented them, and the client-facing status are all excluded by construction rather than by a setting somebody could get wrong.

How do they sign in?

A link sent to them. There is no password to forget and none to breach.

Book a demo

Look at it as a candidate.

Then press erasure on a record with a legal hold. What comes back is the paragraph your DPO will want to read.