# Remote

### What you get

* **Unified global directory** — Remote employees, EOR workers, and contractors all appear in Siit with the right worker type.
* **Lifecycle triggers** — Start date, End date, and Birthday flow into Siit as workflow triggers.
* **Country and entity context** — country, legal entity, and contract type are synced so you can route and approve by location.
* **Manager resolution** — Remote's manager assignments power auto‑selected approvers.
* **Contractor‑aware workflows** — differentiate between employees and contractors in every automation.

### What syncs from Remote

| Category        | Fields                                                                   |
| --------------- | ------------------------------------------------------------------------ |
| Identity        | Full name, preferred name, work email, Remote worker ID                  |
| Role            | Job title, seniority                                                     |
| Org structure   | Manager, team, country, legal entity                                     |
| Employment      | Worker type (EOR Employee, Direct Employee, Contractor), contract status |
| Lifecycle dates | Start date, end date, date of birth                                      |

Work email is the canonical identifier.

### Before you connect

* A Remote admin to generate an API token.
* Work email populated on every worker record. For EOR employees, this is the corporate email you issue them — not their Remote login.

### Connect Remote

1. In Remote, generate an API token for Siit with read access to people, contracts, and organization data.
2. In Siit, go to **Settings → Integrations**, find **Remote** in the HRIS section, and click **Connect**.
3. Paste the API token, then click **Authorize**.
4. Review the imported people and field mapping (including Worker Type → Employment Type) and click **Finish setup**.

Need a more detailed walkthrough? Reach out to support via the in‑app chat.

### After the connection

* Confirm your **People list** matches Remote's active workforce.
* In **Settings → People → Fields**, set Remote as the source of truth for country, contract type, and legal entity if you're also connected to an IdP.
* Most Remote customers start with offboarding automation driven by contract end date.

### Sync frequency

Remote data refreshes automatically every few hours. Trigger an immediate refresh from **Settings → Integrations → Remote → Sync now**.

### Common workflows

**Global Day‑1 onboarding.** *Trigger: Start date. Actions: create IdP account, assign apps by team, ship equipment if Worker Type = Employee, send country‑specific welcome.*

**Contractor offboarding.** *Trigger: End date, Condition: Worker Type = Contractor. Actions: revoke app access, notify manager, close Slack access.*

**Entity‑specific approval.** *Condition: Requester's entity = "Acme SAS" → Approver = French HR lead.*

### Troubleshooting

**Workers missing.** Only active and upcoming contracts sync by default. Confirm contract status and work email in Remote.

**Contractor vs employee mis‑labeled.** Open **Settings → Integrations → Remote → Mapping** and check Worker Type → Employment Type.

**Manager field empty.** In Remote, check the worker has a reporting manager set on their profile.

**"Unauthorized" on connect.** The API token was revoked. Generate a new one and update Siit.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.siit.io/integrations/hris/remote.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.