---
key: give-a-team-member-branch-access
title: Give a team member access to branches
audience: staff
section: administration
routes: ["/settings/org/branches/memberships", "/settings/org/branches"]
permissions: ["branches.memberships.read"]
features: ["settings.org.branches"]
since: 0.0.1
updated: 0.0.1
status: published
summary: Choose which branches a team member can work in and which one they start in, from the Memberships tab of the Branches page.
keywords: [branch access, assign to branch, home branch, default branch, which location, multi-location staff, tech branch]
related: [create-a-branch, choose-the-branch-for-work, add-a-team-member, change-a-team-members-roles]
---

In the sidebar, open **Administration**, then choose **Branches** under **Company**, then the **Memberships** tab. The page address is `/settings/org/branches/memberships`.

A person's branches decide which branches they can switch to at the top of Nova, which branches' work they see when your plan splits work by branch, and which branches they can pick when they create or move work. A person belongs to branches; the work itself carries its own branch (see [[choose-the-branch-for-work]]).

## Before you start

- Your admin has to give your role permission to read branch memberships to see the tab, and permission to write them to change anything. With read-only access the page tells you so and the switches are locked.
- Create the branches first; see [[create-a-branch]].

## Steps

1. In **User**, type the person's name or email and pick them from the list.
2. A card appears for every branch. Turn on the switch for each branch the person may work in. The organization's default branch is marked **Org default**.
3. In **Default Branch**, pick the branch the person should start in when they sign in. Only branches you turned on can be chosen.
4. Press **Save Memberships**.

## What you see

- Until you pick someone, the page asks you to select a user to manage branch memberships.
- The refresh button beside the **Memberships** heading reloads the list if someone else has just changed it.
- Back on the **Scope context** tab, each person can see their own **Active Branch** and **Allowed Branches**.

## If something looks different

- **Default Branch** says no branches are selected: turn on at least one branch switch first.
- **Save Memberships** is missing and the page says you have read-only access: ask your admin for permission to write branch memberships.
- The person cannot see a piece of work: work belongs to the branch saved on the work itself, not the customer's branch. Check the branch on the work order (or project, task, invoice), and give the person that branch here or move the work; see [[choose-the-branch-for-work]].

[[route:/settings/org/branches/memberships|Open Memberships]]