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.
Client Access
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.
The problem
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.
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.
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.
The client sees your firm's name, logo and colours on your own subdomain. Nothing about the experience advertises the software underneath it.
Contacts request a link and sign in without another password to store or reset — the pattern client-side users actually complete.
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.
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.
Four steps, all from records you already maintain.
Choose a contact already held against the client company in your CRM.
RayCruit sends a branded invitation in the contact's language, from your firm.
They accept the invitation and sign in by secure link — no password to create.
Revoke access when the engagement or the person's role at the client changes.
You can say which person at the client was given access, and when.
The client sees your firm, not a third-party tool with your logo bolted on.
Access follows the individual, so staff turnover at the client does not leave a door open.
The access layer is in place, so client-facing views land on top of it rather than starting from nothing.
Entry is issued, recorded and revocable instead of forwarded.
The client boundary is a separate surface with its own session, which is what makes it defensible.
Invitation email, sign-in and the space itself all carry your firm's identity.
See it in motion
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
Continue across the platform
Client companies, contacts, roles and the relationship history behind every mandate.
Learn moreAnonymised CVs, fit explanations, executive summaries and client booklets on your brand.
Learn morePermission groups, confidential mandates, enterprise sign-in and an append-only audit trail.
Learn moreA demo follows one mandate across every module, which is the only way the connections become obvious.