---
title: "Correct WelcomeKit Scopes for Jungle Integration"
img: https://s3.us-east-2.amazonaws.com/unified-article-images/correct_welcomekit_scopes_for_jungle_integration-icon.png
date: 2026-04-14T14:32:00.000Z
tag: Guides
description: "This guide outlines the required WelcomeKit scopes per Unified object for the Jungle integration."
url: "https://unified.to/blog/correct_welcomekit_scopes_for_jungle_integration"
---

# Correct WelcomeKit Scopes for Jungle Integration
------
_April 14, 2026_

This guide outlines the required WelcomeKit scopes per Unified object for the Jungle integration.


## Scope Mapping (by Unified Object)


| Unified Object                                | Required Scope(s)                                                                                                                       | Partnership (su_*) Needed? |
| --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | -------------------------- |
| **ATS · Job (**`ats_job`**)**             | `su_jobs_r`                                                                                                                             | Yes                        |
| **ATS · Candidate (**`ats_candidate`**)** | **Read:** `candidates_r` AND `my_candidates_r` <br> **Write:** `candidates_rw` AND `my_candidates_rw`                                       | No                         |
| **ATS · Document (**`ats_document`**)**   | **Read:** `documents_r` AND (`candidates_r` & `my_candidates_r`) <br> **Write:** `documents_rw` AND (`candidates_rw` & `my_candidates_rw`) | No                         |
| **ATS · Activity (**`ats_activity`**)**   | **Read:** `emails_r` AND (`candidates_r` & `my_candidates_r`) <br> **Write:** `comments_w` AND (`candidates_rw` & `my_candidates_rw`)      | No                         |
| **HRIS · Company (**`hris_company`**)**   | **Read:** `su_organizations_r`                                                                                                          | Yes                        |
| HRIS · Location (hris_location)               | Read: `offices_r` & `su_offices_r` <br> Write: `offices_rw`                                                                                  | Yes                        |
| HRIS · Group (hris_group)                     | Read: `departments_r` & `departments_rw` & `su_departments_r` <br> Write: `departments_rw`                                                  | Yes                        |
---


## Important Notes


### Partnership-only scopes

- `su_jobs_r` → Required for listing jobs
- `su_organizations_r` → Required for listing organizations
- `su_offices_r`  → Required for listing locations
- `su_departments_r` → Required for listing groups

These require WelcomeKit partnership approval.


### **Non-partner access (scope overrides)**


If you do **not** have WelcomeKit partnership approval, you won't be able to use the partnership-only scopes. Instead, request the standard non-partner scopes by overriding the defaults for this integration. Each Unified permission (like `ats_job_read`) maps to a default set of the provider's raw scopes, and you can replace that default per integration via the integration's scope override setting. Update the `WorkspaceIntegration` object with an `overriden_scopes` map keyed by the Unified permission, where each value is a comma-separated list of the provider's raw scopes:


`{ "overriden_scopes": { "ats_job": "jobs_r" } }`


With this override, Unified requests `jobs_r` (org-scoped jobs) instead of `su_jobs_r`. At runtime, the connector lists jobs via `GET /jobs?organization_reference=...` using the organization cached on the connection during auth setup, and falls back to `GET /users/current` for organization discovery — so non-partner keys never depend on the `su_*` scopes. For full details, see [Overriding scopes per integration](https://docs.unified.to/concepts/scopes#overriding-scopes-per-integration).


---


### Candidate-dependent scopes


The following always require candidate access:

- Documents → require candidate read/write scopes
- Emails → require candidate read scopes
- Comments → require candidate write scopes

---


## How to Get Partnership Access (Jungle / WelcomeKit)


To access partnership-only scopes (`su_*`), you will need to be approved by WelcomeKit.


### Steps:

1. **Reach out to WelcomeKit support or your account manager (**[https://help.welcometothejungle.com/en](https://help.welcometothejungle.com/en))
    - Request access to partnership scopes
    - Clearly mention your use case (e.g. job syncing, org-level data access)
2. **Provide integration details**
    - Your application name
    - What data you intend to access
    - Whether access is read-only or includes write operations
3. **Explain your end-user flow**
    - How users connect their WelcomeKit account
    - Why elevated (partnership) access is required
4. **Await approval**
    - Once approved, the scopes will be enabled for your app
    - You can then include `su_*` scopes in your [OAuth](/embeddedauth) flow