Connecting iCIMS

#Who is usually in the room

iCIMS tends to sit at the centre of a large talent acquisition organisation, and that changes the shape of the conversation. Recruiting rarely owns the decision alone. An internal IT or HRIS team usually administers the account and decides what API access can be issued; information security wants to know where candidate data travels and under what contract. None of that is an obstacle — it is simply the process, and we plan around it.

So bring your HRIS contact to the first call if you can. They will know what your iCIMS account is able to issue, which is the fact that determines everything downstream.

#How the integration is set up

1. 1

   Introduce us to the systems owner

   Email support@remakecv.com with your organisation name, and say who administers your iCIMS account. We will work with whoever that is, alongside your talent function.

2. 2

   Establish what API access can be issued

   Your iCIMS administrator or their support team determines the credentials available to your account and the terms attached. Their answer defines what we build against, so it comes first.

3. 3

   Hand the credentials over securely

   We will nominate a safe channel. Anything that reaches applicant records deserves password-grade handling — never plain email, never a thread with the whole project team copied in.

4. 4

   We build it and switch it on

   Our team implements the connection and enables it for your company. The relevant controls appear in your RemakeCV dashboard, with no desktop software and nothing for individual recruiters to install.

#What your security review will need

Because this conversation usually reaches an information security team, here are the points they ask about first.

AI processing runs on OpenAI under an enterprise agreement with zero data retention. Candidate data is not retained by OpenAI once your request has been processed, and it is contractually excluded from model training. EU data residency is available on request — say the word and we configure it for your account. A signed Data Processing Agreement is available from support@remakecv.com, along with the current sub-processor list.

The rest — encryption, access control, two-factor authentication, how API keys are stored and revoked — is set out in security, DPAs and sub-processors. Send your reviewers straight there.

#What the workflow looks like

Once the connection is live, the branded document is produced where hiring already happens:

1. Your recruiters and coordinators progress candidates in iCIMS as they do today.
2. The CV is rendered into your organisation's branded template — same template, same editor, same options as any other RemakeCV job.
3. The finished document returns to the candidate record, where the hiring manager and interview panel find it.

Ownership of the connection is settled at scoping rather than assumed. Some of our integrations are held once at company level; others belong to each user, which keeps ATS-side permissions and audit trails attached to the person who acted. In a large talent function that distinction matters, so we put it on the agenda.

#Does the integration change the formatting?

No. Templates, editing, anonymisation, summaries and downloads behave identically whether a CV arrives over a connection or is dragged into the browser. Transport is the only thing an integration decides, so adopting one never obliges you to revisit your output — useful when the template has already been signed off by a brand team.

Where the branded template has yet to be designed, that runs as its own workstream: our team builds it to your organisation's brand and the connection then delivers it. See requesting a custom template.

#Building it yourself

Large organisations often have engineering capacity in-house. The public REST API exposes the processing, retrieval and template endpoints directly, so your own team can wire RemakeCV into iCIMS on its own release schedule — see connecting RemakeCV to any ATS or internal system.

#Which plan includes it?

Business and Enterprise both include it — integrations are not gated behind a tier. See plans and pricing.

#Start the conversation

Email support@remakecv.com with iCIMS and your organisation name. Tell us who administers the account and whether a security review is expected, and we will confirm what the integration will do, what we need from you, and what your reviewers will want to see.