> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spott.io/llms.txt
> Use this file to discover all available pages before exploring further.

# SAP Fieldglass

> Connect jobs and candidates to your client's SAP Fieldglass instance, and let candidate stages follow their Fieldglass status automatically.

## Overview

**SAP Fieldglass** is SAP's vendor management system. Clients use it to publish
contingent and contract roles to their approved suppliers, collect submissions, and
track each worker through to placement. If you staff for a client who runs Fieldglass,
their requisitions and your submissions already live there.

Connecting Fieldglass to Spott means you work in one system instead of two. Jobs and
candidates are linked to your SAP instance, and once you have set up your stage
mappings, Spott **moves candidates through the pipeline by itself, following their
status in Fieldglass**. No one has to watch the client's portal and drag cards to match
it.

## How it works

1. An admin connects your workspace to your SAP Fieldglass instance.
2. You map each Fieldglass status to one of your [job stages](/docs/settings/stages).
   This is the part you do once.
3. Jobs and candidates in Spott are connected to their counterparts in Fieldglass.
4. When a candidate's status changes in Fieldglass, Spott moves the application to the
   stage you mapped that status to.

Because the movement is a normal stage change, everything that hangs off a stage still
applies: it appears on the application's activity feed, it counts toward your
[pipeline reporting](/docs/settings/stages#how-the-markers-turn-into-numbers), and any
[automation](/docs/settings/automations) with an "application moved" trigger fires as
usual.

<Tip>
  Map your stages before you connect a live job, not after. A mapping added later does
  not go back and reposition candidates who already moved, so the first pipeline you run
  through Fieldglass is the one worth setting up carefully.
</Tip>

## Set up your stage mappings

Your Fieldglass statuses and your Spott stages will not have the same names, and they do
not need to. What matters is that every status your client actually uses points at a
stage, so nothing arrives with nowhere to go.

Work through the client's status list and decide, for each one, where a candidate at
that point belongs in your own pipeline. Several Fieldglass statuses can map to the same
Spott stage, which is usually what you want: a handful of interview-scheduling statuses
can all land on your Interview stage.

## Configure

Ask your Spott contact to walk through the connection with you. Setting it up needs
details from the client's Fieldglass instance, so it is worth doing together the first
time.

<Note>
  Only workspace admins can enable this integration. If you do not see this option,
  contact your workspace admin. Enabling it requires the relevant license or add-on.
</Note>

## Good to know

* **Fieldglass drives the stage, not the other way around.** The sync described here
  moves candidates in Spott to match what the client has done in Fieldglass.

* **Your stage names stay yours.** Mapping means you do not have to rename your pipeline
  to match a client's terminology, and different clients can use different mappings onto
  the same stages.

* **Rejections still come from the client.** A candidate the client turns down in
  Fieldglass reaches the stage you mapped that status to, so point it at the outcome you
  want on your side rather than leaving it unmapped.

<Card title="Set up your pipeline first" icon="bars-staggered" href="/docs/settings/stages">
  **Pipeline stages** in Settings. The stages you map Fieldglass statuses onto, and how
  moving between them feeds your reporting.
</Card>