# Connecting SAP SuccessFactors > RemakeCV connects to SAP SuccessFactors. Our team builds the integration against API credentials issued on your own tenant, so candidates from every country and business area reach decision-makers in one consistent branded format. Source: https://www.remakecv.com/help/integrations/sap-successfactors Last updated: 2026-08-22 --- RemakeCV connects to SAP SuccessFactors. Our team builds and configures the integration for your talent function using API credentials issued on your own SuccessFactors tenant, and from there it sits alongside our other ATS integrations — a candidate's CV becomes a branded, optionally anonymised document and goes back to their record. Email support@remakecv.com and we will scope it with you. ## Why scoping is real work on a SuccessFactors tenant Most ATS platforms look broadly the same from one customer to the next. SuccessFactors does not. A tenant is configured around one organisation's job architecture, country requirements and approval routes, often over several years, so two customers running the identical product can present very different surfaces to anything connecting to them. The first conversation we have with you is therefore genuine discovery rather than a form to complete: we ask what your tenant permits instead of carrying assumptions over from somebody else's. Geography is the other constant at this scale. When hiring runs across several countries, CVs arrive in whatever each local market treats as normal — different lengths, different ordering, different ideas about what belongs on the page at all. A single house structure is what lets a panel in one country read a shortlist assembled in another without decoding the layout first. ## How the integration is set up ### Describe how your hiring runs today Email support@remakecv.com with your organisation name, the countries and business areas involved, and who prepares a candidate document before a decision-maker sees it. ### Find out what your own tenant can issue Whoever owns SuccessFactors internally decides what API access is available and on what terms. That answer belongs to your tenant alone, and it is the thing we build against. ### Hand the credentials over safely We will nominate a channel for it. Anything that reaches applicant data deserves the care a production secret gets, so keep it out of ordinary mail threads and shared mailboxes. ### We build it, then switch it on for you Our team implements the connection and enables it for your company. The relevant controls appear in your RemakeCV dashboard afterwards — recruiters and coordinators install nothing locally. > **Note:** How far the finished integration reaches is set by the access your tenant grants, not by us: collecting a candidate's CV, filing the branded version back against them, or both directions. Given how much SuccessFactors configurations differ, we put that scope in writing with you during scoping and confirm it before any build work begins. ## What the workflow looks like With the connection running, the branded CV arrives as a by-product of work your recruiters are doing anyway: 1. They stay in SuccessFactors, on the same requisitions and the same candidate records as before. 2. The CV is rendered into your organisation's branded template, anonymised on the way through where your process calls for it. 3. The finished version is filed back against the candidate, ready for whoever opens that record next. The middle step is ordinary RemakeCV, so anything a pilot team has already learned still applies. See [uploading a CV](https://www.remakecv.com/help/formatting-cvs/uploading-a-cv.md) and [reviewing and editing](https://www.remakecv.com/help/formatting-cvs/reviewing-and-editing.md). One practical note: on a platform this size, the people who use the output and the people who control the tenant are rarely the same team. Bringing your HR systems contact into the conversation early saves scoping the work twice. ## Does the integration change the formatting? No. Templates, editing, anonymisation, summaries and downloads behave identically whether a CV arrived over a connection or was dropped into the browser by hand. The connection settles the route the file takes and nothing beyond that, so adopting one asks nothing of your existing output. Groups hiring under more than one employer brand, or presenting differently by region, usually ask whether that can be reconciled. [Template variants](https://www.remakecv.com/help/templates-and-branding/template-variants.md) exist for exactly that — the visible identity changes while the underlying structure stays fixed, and the fixed part is what keeps candidates comparable across the group. Where the design has yet to be drawn, it is built alongside the connection: see [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md). ## Building it yourself Where your organisation has engineering capacity in-house and would rather own the connection, the [public REST API](https://www.remakecv.com/help/api-reference/introduction.md) exposes the processing, retrieval and template endpoints directly. See [connecting RemakeCV to any ATS or internal system](https://www.remakecv.com/help/integrations/using-the-api-instead.md) for what they cover. ## Which plan includes it? Neither plan treats integrations as an extra. See [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md). ## Start the conversation Email support@remakecv.com with **SAP SuccessFactors**, your organisation name and the countries you would start with. We will confirm what the integration can do on your tenant, what we need from you, and how your talent function will use it day to day. ## Frequently asked questions ### Does RemakeCV integrate with SAP SuccessFactors? Yes. Our team builds and configures the SAP SuccessFactors integration for your talent function using API credentials issued on your own tenant, and it then works alongside our other ATS integrations. Because SuccessFactors tenants are configured differently from one organisation to the next, we scope yours specifically — email support@remakecv.com to start that. ### What do I need to provide? API credentials issued on your SuccessFactors tenant, arranged by whoever owns the platform internally — often an HR systems group rather than the recruiters themselves — plus a short note on the countries and business areas you would begin with. Send both to support@remakecv.com and our team takes the build from there. ### Will it work the same as the other integrations? Yes. The same templates, template variants, editor, anonymisation, summaries and downloads apply. An integration decides only how a CV travels between two systems; the document a hiring manager opens is the same either way. ### Can I use RemakeCV with SAP SuccessFactors before the integration is set up? Yes. RemakeCV works standalone in the browser — upload a CV, format it into your branded template, anonymise it where needed and download it. Talent functions often begin this way with a single country or team while tenant-side access is being arranged.