All features

Client Access

Give a client contact their own way in — under your brand.

Client collaboration usually runs on shared inboxes and forwarded attachments, and nobody can say afterwards who saw what. RayCruit lets you invite a named contact at a client company into your own branded space, on your own subdomain, with sign-in by secure link rather than another password to manage.

  • Invitations to named contacts, not a shared login
  • Your brand and your subdomain, not ours
  • Passwordless sign-in by secure link
  • Completely separated from the recruiter workspace
Concept diagram
Recruiter workspaceStays internal
  • Your pipeline
  • Other clients
  • Internal notes and scoring
Tenant boundaryInvite a named contactSecure sign-in
Customer portalSees only this
  • Their own contact record
  • Your brand, your subdomain

The problem

Client-facing work runs through channels you do not control.

A shortlist leaves as an email attachment and immediately stops being traceable. It gets forwarded, renamed, printed. When a question comes back weeks later, nobody can reconstruct which version the client actually saw, or who at the client company ever received it.

  • Attachments forwarded beyond the people you sent them to
  • No record of which contact received which material
  • Shared client logins that outlive the person who used them
  • Sensitive candidate material sitting in mail archives you cannot reach

A door you control, with your name on it.

Client access is issued per person and tied to your tenant. The contact you invite is a contact you already hold in the CRM, and the space they land in is branded as yours.

01

Invitations tied to a named contact

You invite a specific person from a specific client company — the same contact record your mandates already reference. Access belongs to that person, not to a mailbox the whole client team shares.

02

Your brand, your subdomain

The client sees your firm's name, logo and colours on your own subdomain. Nothing about the experience advertises the software underneath it.

03

Sign-in by secure link

Contacts request a link and sign in without another password to store or reset — the pattern client-side users actually complete.

04

Hard separation from your workspace

The client space runs behind its own boundary. It cannot reach your pipeline, your other clients, your candidate pool or anything a recruiter sees, because it is a different surface with its own session — not the recruiter application with things hidden.

05

Access you can withdraw

An invitation can be re-sent or revoked, and a contact removed at the client company loses their way in without anyone changing a shared password.

How client access is issued.

Four steps, all from records you already maintain.

  1. 01

    Pick the contact

    Choose a contact already held against the client company in your CRM.

  2. 02

    Send the invitation

    RayCruit sends a branded invitation in the contact's language, from your firm.

  3. 03

    The contact signs in

    They accept the invitation and sign in by secure link — no password to create.

  4. 04

    Withdraw when it ends

    Revoke access when the engagement or the person's role at the client changes.

Where this matters

Named accountability

You can say which person at the client was given access, and when.

Brand in front of the client

The client sees your firm, not a third-party tool with your logo bolted on.

No shared credentials

Access follows the individual, so staff turnover at the client does not leave a door open.

A base to build on

The access layer is in place, so client-facing views land on top of it rather than starting from nothing.

What changes

Client access stops being an inbox

Entry is issued, recorded and revocable instead of forwarded.

Isolation you can explain

The client boundary is a separate surface with its own session, which is what makes it defensible.

Branded from the first screen

Invitation email, sign-in and the space itself all carry your firm's identity.

See it in motion

The platform, end to end, in two minutes.

How the modules hand over to each other in the real product — customer and mandate, candidate and matrix, the workspace where a pairing is decided, and the material that goes to the client.

2 min

See the modules working together.

A demo follows one mandate across every module, which is the only way the connections become obvious.