> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rulebase.co/llms.txt
> Use this file to discover all available pages before exploring further.
# Set up partners and scope access to them
> Create the partners your outsourced work belongs to, keep agent assignment automatic, and limit a partner's own reviewers to their own data.
A partner is an organization whose people do work in your help desk: a BPO, an
outsourcer, a sponsor bank. In Rulebase the partner rides on the agent, not the
ticket: each agent belongs to at most one partner, and a ticket counts as that
partner's when one of its agents does. Use partners to compare an outsourcer
against your in-house team.
Partners also scope access. A member's access can be limited to a partner, so
a team lead at your BPO signs into
your Rulebase and sees their own people and tickets rather than everybody's.
The **Scope** field on invitations and memberships only appears once you have set
a **Partner custom field** on this page. Creating partners by hand does not
unlock it, so if you are here to restrict what an outsourced reviewer can see,
do the **Configure** step below even if you intend to assign people manually.
## Before you start
* Partners live on the **Partners** tab of
[Settings > People](https://app.rulebase.co/settings/people/partners), beside
Members, Invitations, Agents, Teams, and Roles.
* You need an admin role. Without it the tab is read-only: no **Create partner**,
no **Configure**, no way to add or remove people.
* For automatic assignment, you need a dropdown custom field on your people whose
options are the partner names. Only dropdown fields work; a text, number, date,
or yes/no field is offered in the picker, saves without complaint, and then
never files anyone.
## Create a partner
1. Click **Create partner**.
2. Enter the **Name**. This is what appears in filters, routing rule conditions,
and dashboard breakdowns, so use the name your team says out loud.
3. Optionally add **Domains**: type a domain and press Enter for each one. They
are recorded against the partner and shown in the list; they are a label for
your own reference rather than an access rule.
4. Choose the **Type**. The options depend on your organization's own type, so a
fintech is offered Sponsor bank, BPO, and Other, while other organizations see
the full set.
5. Click **Create partner**.
The list then shows each partner with its type, domains, and a **People** count.
Click a row to open it.
## Let the roster maintain itself
To keep assignments current as an outsourcer's headcount changes, point
Rulebase at a field instead of assigning agents by hand.
1. Click **Configure**.
2. Under **Partner custom field**, search for the dropdown field on your people
that names their partner and select it. Fields synced from a help desk are
listed with their source in brackets, so a Zendesk dropdown works here as
readily as one you created yourself.
3. Click **Save**.
From then on, setting that field on an agent files them under the matching
partner, and Rulebase creates the partner itself the first time it sees an option
it has no partner for, named after the option's label. Clearing the field
unassigns them.
The sync happens when an agent's field value is saved, not retroactively. If your
people already carry values in that field, re-save them, or assign the first
batch by hand; existing values do not file themselves.
## Add and remove people by hand
Manual assignment works alongside the field, and it is the quicker path for a
handful of people.
1. Open the partner.
2. Under **People**, click **Add**.
3. Search for the person and select them. They are added immediately.
4. To take someone out, click the **×** at the end of their row.
Removing a person unassigns them from the partner. It does not remove them from
your agent roster, and their historic evaluations keep the partner that was
recorded at the time.
## Scope a member to their partner
Once a partner custom field is configured, **Specific partners** becomes one of
the scope choices for new invitations and for people who already have access.
[Invite members](/guides/access-management/invite-members) covers the invite
dialog. For someone who is already a member:
1. Open the **Members** tab of
[Settings > People](https://app.rulebase.co/settings/people/members).
2. Click their row to open **Edit membership**.
3. Set **Scope** to **Specific partners**, then pick the partners they should
reach. **Entire organization**, **Specific groups**, and **Specific teams** are
the alternatives.
4. Click **Save changes**.
If **Scope** is greyed out, look at the **Role** above it: the control is
disabled while the role is Administrator or Agent, because neither can be
narrowed.
The **Members** and **Invitations** tabs both grow a **Scope** column once
partners are configured; use it to audit who can see everything.
A member scoped to one or more partners can reach only:
* **Agents** belonging to those partners
* **Teams** those partners' agents sit in
* **Tickets** where one of those partners worked
* **QA evaluations** whose scored agent belongs to those partners
The restriction is enforced on the data, not just hidden in the interface, and it
fails closed: a membership scoped to partners with nothing selected sees nothing
rather than everything. Two roles ignore scope: administrators always have full access, and agents are
always limited to themselves. See
[Roles and permissions](/guides/roles-and-permissions).
Deleting a partner unassigns its people and drops it from any membership scoped
to it. A member scoped only to that partner is left scoped to nothing, which means
an empty Rulebase rather than an error message. Re-scope those memberships in the
same sitting.
## Where partners show up afterwards
**Filtering.** Partner is a filter dimension on interaction and evaluation lists.
[Filter by team, partner, brand, and channel](/guides/quality-assurance/filter-interactions)
explains why it sits under a **Ticket** heading despite describing the agent.
**Routing.** **Partner** is available as a routing rule condition, so you can send
one outsourcer's low scores to a different reviewer than your own team's. See
[Create routing rules](/guides/quality-assurance/create-routing-rules).
**Reporting.** Dashboard charts accept a Partner filter where their data source
supports it, which is how a per-partner quality view gets built. See
[Manage dashboard charts](/guides/insights/manage-dashboard-charts).
## Related
* [Invite members](/guides/access-management/invite-members)
* [Create and manage teams](/guides/access-management/create-and-manage-teams)
* [Roles and permissions](/guides/roles-and-permissions)
* [Filter by team, partner, brand, and channel](/guides/quality-assurance/filter-interactions)