Project settings is the leads' place. Organisation Owners and Admins see it on every project. A project's Product Owner and Scrum Masters see it on their own project, and each of them gets the tabs their role covers. Developers and Stakeholders don't have it in their menu. If they open its address, they see No access to project settings. They use the project's things where they work instead: the board, the backlog and the work item.

Who gets which tab

Set the project's roles

1. Open the People tab.
2. Choose the Product Owner (one per project), the Scrum Masters, the Developers and the Stakeholders. On a Private project, this is also where you add people.

Making someone a Scrum Master is for Owners, Admins, the Product Owner and Scrum Masters. Choosing the Product Owner is for Owners, Admins and the current Product Owner, or a Scrum Master while there's none. Nobody can change someone with a higher organisation role than their own.

Archive or delete a project

1. Open Archive & delete (Owners and Admins only).
2. Archive project hides it from the active list and makes it read-only. Everything is kept, and it doesn't count against your plan's project limit.
3. Delete project moves it to Projects › Deleted. An Admin can restore it for 90 days. After that it's removed for good.

More on setting up a project: Part 2 · People & visibility. Components: Components.

Every project has its own copy of its workflow, so changes here reshape this project's board and nothing else. Its Scrum Masters, and Owners and Admins, can change it. The Product Owner can while the project has no Scrum Master.

Shape the stages

1. Click Add stage, name it and choose its category: To Do, In Progress or Done. The category decides what counts as started and finished in reports.
2. Rename a stage, drag it to reorder, or remove it. A stage that still holds work items can't be removed until they're moved.
3. Optional: give a stage a WIP limit — the most items it may hold at once. Leave it empty, or 0, for no limit.

Limit the moves

1. Under Stage Transitions, tick which stages an item may move to from each one.
2. With no transitions ticked, every move is allowed.

Add entry rules to a stage

1. Open a stage's entry rules.
2. Under Who may move items here, tick Product Owner, Scrum Master, Developer and/or The assignee. With none ticked, anyone who can edit work items may. Owners and Admins follow the same rules.
3. Under Before an item enters, add Required fields (built-in or custom), and tick All sub-tasks done or All blocking items done if you need them.

When a move is refused, the board says why where the person is working. More: Stage entry rules.

Set a Definition of Done

1. Under Definition of Done, type an item in Add an item… and add it. Repeat for each check.
2. When someone moves a work item to Done with something unticked, Flow asks them to confirm.

Templates are starting points for new projects. A project copies its template when it's created, so a template never changes a project that already exists. Templates are managed by Owners and Admins.

Add a template

1. Click New template.
2. Pick a starting point — Blank or one of the built-in sets — and click Next.
3. Name it and click Create workflow.

Remove a template

1. Click the bin icon on its row and confirm Delete template. It stops being offered for new projects. Projects made from it keep their own copy. The Default template can't be deleted.

The sections down the side are General, Security, Custom fields, Workflow templates, and under Connections Slack and GitHub. Below them, links go to the Members, Teams, pods & roles and Billing pages. Your own photo, password, two-factor and notifications aren't here — they're in Your account.

Owners and Admins change everything here, except the two-factor rule, which is the Owner's. Members and Stakeholders don't see organisation settings at all: Settings isn't in their menu, and the page says “No access to organisation settings”.

Name, timezone and plan (General)

1. Edit the Name (2–100 characters).
2. Set the Working day timezone. It decides when a day starts and ends for sprint dates, due dates, burndown and reports, in every project that doesn't set its own. Flow warns you first: charts already recorded keep their days.
3. Click Save.

The Address (your workspace's short name in the web address) can't be changed. Plan shows your current plan, with a Manage billing link for Owners and Admins.

The other sections each have their own part of this guide: Security · Custom fields · Workflow templates · Slack · GitHub.

GitHub works on every plan. Connecting it is for Owners and Admins. Each project then chooses which repositories it links from.

Connect GitHub

1. Click Connect GitHub. GitHub opens and asks you to install our GitHub app on your GitHub account or organisation. Only someone who administers that GitHub account or organisation can do this.
2. Choose which repositories to share and finish on GitHub. You come back to Flow with a message saying GitHub is connected.
3. The account appears in the list. Show repositories lists what it shares, and Refresh reads the list again after you change it on GitHub.

Choose a project's repositories

1. In the project, open Project settings › Repositories (Owners, Admins, and the project's Product Owner and Scrum Masters).
2. Under Add repositories, select the ones this project uses.
3. Click Save repositories.

See it on a work item

1. Open a work item. Its Development card shows branches by repository, pull requests by state with the open ones listed, and commits as a count with when the latest was made.
2. Click View all to see every pull request and branch.

Disconnect

1. Click Disconnect on the account and confirm.
2. Flow stops linking new branches, commits and pull requests from that account. Links already on work items stay.

Disconnect only unlinks Flow. To stop the app completely, uninstall it on GitHub (Manage on GitHub).

Flow can post assignments, comments, mentions, status changes on watched items, and sprint events to one Slack channel. Connecting Slack is for Owners and Admins.

Connect Slack

1. In your Slack app, create an incoming webhook for the channel you want and copy its address.
2. Paste it into Incoming webhook URL. It starts with https://hooks.slack.com/services/. Click Save.
3. Click Send test message, then check the channel.

Stop it

1. Click Disconnect and confirm. Notifications stop going to that channel, and you can paste a webhook address again at any time.

Require two-factor for everyone

1. Turn on two-factor for yourself first (below). Flow won't let you require it until you have.
2. Switch on Require two-factor for all members. Flow asks first and says how many members haven't set it up yet. Click Require it.
3. Anyone without two-factor is asked to set it up the next time they use Flow, and can't open anything else until they do.

Only the Owner can change this.

Everyone has these settings for their own account. Click your name at the foot of the sidebar and choose Your account.

Turn on two-factor

1. Next to Two-factor authentication, click Set up two-factor.
2. Open an authenticator app on your phone and scan the code (or enter the key shown under it).
3. Type the 6-digit code the app shows and click Turn on two-factor.
4. Save your recovery codes somewhere safe. If you lose your phone, each code signs you in once.

Running low on codes? Click New recovery codes and enter a current code. Your old codes stop working. You can't turn two-factor off while an organisation you belong to requires it.

Password and signing out

• Change password signs you out everywhere else.
• Forgot it? Click Forgot password? on the sign-in page to get a reset link by email.
• Sign out (in the same menu as Your account) ends your sessions on every device, not just this one.