> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/integrations/integrations-hris/deel-integration.md). # Connect Deel Connect Deel to Siit by choosing a sandbox or production account and authorizing through Deel with a user who has sufficient rights, so Siit syncs your employee data ### Connecting to Deel πŸ’πŸ»β€β™‚οΈ *Siit will only have access to the same information as the user configuring the connection*\*,\*\* so in order for the integration to work properly make sure that a Deel user with sufficient rights is configuring the integration.\* Select **Connect** in the Deel row to open the configuration dialog.
1. **Select if you want to connect a Deel Sandbox or Production Account**\ ​ 2. How to set up: Step 1 – Select I want to authenticate through Deel’s website and click Next. Step 2– Then Pick Deel production. Step 3 – Follow the instruction to authorize Siit integration. Step 4 –You will then be taken to the Deel login screen. Step 5 –You will be redirected to Siit and your integration is now active.\ ​\ Hooray, you are done! πŸŽ‰ From now on, Siit will synchronize your employee information from Deel with Siit including information about employee's **role**, **department**, **office**, and **Start date**... --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.siit.io/guides/integrations/integrations-hris/deel-integration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.