# Project members and access

> Decide who can open a By Dawn project, give people a project role and run access, and invite people from outside your organization.

This page helps you decide who can open a project and what each person can do in it. By the end you'll have
chosen whether the project is open or restricted, and added people with the right role.

Open the project, then **Settings › This project › Members & access**: "Who can open this project,
and what they can do." Everyone who can open the project can see who has access. Project admins and the
organization's owners and admins can change it. Everyone else sees "Only project admins and org admins can
change who has access."

## Open or restricted

The first row sets the project's visibility:

- **Open**: "Everyone in" your organization "can open and work in this project." This is how a new project
  starts.
- **Restricted**: "Only the people and teams below can open this project." Anyone else in the organization
  doesn't see it in their project list.

Organization owners and admins can always open every project, open or restricted, and they appear in the list
as **Org owner** or **Org admin**: "Full access through their organization role". You don't need to add them.

On an open project, the list ends with **Everyone else in** your organization, marked **Org member**. They can
work in the project without being added. Add someone only to give them a different role, or to keep their access
if you restrict the project later.

## Project roles

| Role | Can |
| --- | --- |
| **viewer** | "Can open the project and read its board and tickets, but can't change anything." |
| **member** | "Can create, edit and move tickets and do the day-to-day work." |
| **admin** | "Everything a member can do, plus managing members, visibility and project settings." |

A project has no owner. Its admins, together with the organization's owners and admins, look after it.

## Run access

The **Runs** column decides whether someone can start agent runs on the project's tickets:

| Runs | Means |
| --- | --- |
| **Plan & build** | "Can start planning runs and build runs." |
| **Plan only** | "Can start planning runs, but not build runs." |
| **No runs** | "Can't start runs." |

You can only change it for a **member**, who starts on **Plan & build**. "Project admins can always start
planning and build runs." and "Viewers can't start runs." Use **Plan only** for someone who should be able to
ask an agent for a plan but not let it change code.

## Add people from your organization

1. Choose **Add people**. By Dawn lists everyone in the organization who isn't on the project yet. "They get access
   straight away — no invite needed."

2. Pick one or more people. **Search by name or email** narrows the list, and **Select all** or **Select
   matches** picks everyone shown.

3. Pick their role (it starts at **member**), and choose **Add**.

## Give a team access

Give a whole team a role on the project, so you don't have to add its people one by one. "Everyone on the team gets
this role, and so does anyone who joins it later. Taking someone off the team takes away the access it gave them."

1. Choose **Add team**.

2. Under **Choose a team**, pick the team. Each team shows how many people are on it.

3. Pick the team's role, and choose **Add team**.

The team appears under **People with access** as "Everyone on this team", with its own role and **Runs** value,
which you change the same way as a person's. **Remove** takes the team's access away at once. Someone on the team
who also has a role of their own gets the higher of the two, so a person's own role never narrows what their team
gives them.

Giving a team access doesn't make it the owner of the project's tickets. That's the project's **Teams** setting
(see [Attach a team to a project](https://docs.bydawn.com/teams/#attach-a-team-to-a-project)). [Teams](https://docs.bydawn.com/teams/) explains how to set up a
team and who's on it.

## Invite someone from outside

1. Choose **Invite by email**: "For people outside your organization — accepting adds them to the organization
   and this project."

2. Type their email and pick their project role, then choose **Invite**.

They join the organization as a **member** and the project with the role you picked. The invitation lasts 7
days and appears under **Pending invites**, where you can **Resend** it (with a new link and 7 more days) or
**Revoke** it. If the email belongs to someone already in the organization, By Dawn says so and offers **Add them
instead**. [Members and invites](https://docs.bydawn.com/members/#accept-an-invitation) explains accepting an invitation.

## Change or remove someone

Pick a new role or **Runs** value in the person's row, or choose **Remove**. Each change takes effect at once.
You can't change your own role or remove yourself here, so ask another admin.

Removing someone from a restricted project stops them opening it. On an open project they can still open it
as an organization member, with no project role of their own.

A role your identity provider gives through a [group mapping](https://docs.bydawn.com/scim/#map-groups-to-roles) shows an **IdP**
badge. Changing it here keeps it as you set it. To remove the person, take them out of the group in your
identity provider, or change their role here first.

> **Caution:** By Dawn doesn't stop a project losing its last project admin. That's safe, because the organization's owners and
> admins can always manage it, but it's worth keeping one admin per project so someone close to the work can.

## FAQ

**Can I add a team to a project?**

Yes, with **Add team** (see [Give a team access](#give-a-team-access)). Your identity provider's
[group mappings](https://docs.bydawn.com/scim/#map-groups-to-roles) can also give people a project role.

**Someone in the organization can't see a project. Why?**

It's restricted and they aren't on it. A project admin, or an organization owner or admin, can add them here.

**Can agents from another project work in this one?**

Only if this project gives them access. See [Agent access](https://docs.bydawn.com/agent-access/).

## Where to go next

- [Agent access](https://docs.bydawn.com/agent-access/): what agents may do in this project, and from other projects.
- [Members and invites](https://docs.bydawn.com/members/): the organization's members and their roles.

Source: https://docs.bydawn.com/project-access/