Managing Project Settings

Every project has a Project settings page — identity, members, integrations, workflow options, and the Microsoft Teams link. Most of it is Owner/Admin only, and the one rule that surprises people: you can't delete a project while it's still linked to a Teams channel.

Project identity

• Name & description — click the pencil next to the name, edit, then Save.
• Icon — click the small camera button on the project icon to upload an image (Owner/Admin only). A recognizable icon pays off in the project list.
• Perma name — an optional short URL slug for the project, set in the project's edit form; if you leave it blank one is generated. It must be unique across AB Projects.
• Estimate Time Unit — also in the edit form: Hours or Days, the unit used whenever someone enters a time estimate on a task in this project.

Joined Members

The Joined Members section lists everyone on the project with their role. Owners and Admins change roles from the inline dropdown and remove members from here — but remember membership is driven by the linked Teams channel, so the roster mostly maintains itself. Details: Adding or Removing Members and Role-Based Access Control.

Teams channel notifications

When a channel is linked, AB posts task updates into it. If that gets noisy, Owners and Admins can calm it down under Integrations → Teams channel notifications — a master switch plus a checkbox per category. Everything is on by default, so nothing changes unless you opt out.

More on what the bot posts and when: Notifications and Reminders.

GitHub integration

Owners and Admins can connect a GitHub repository so branches can be created straight from a task. Under Integrations → GitHub Integration, fill in:

1. Owner / Organization and Repository — the target repo.
2. Personal Access Token — a GitHub token (a password-like key GitHub issues for API access) with repo scope, created at github.com/settings/tokens. Stored securely, displayed as a password field.
3. Default Branch — the branch new task branches are based on, typically main. Then Save.

Task workflow (Options)

Each project defines its own workflow lists, opened from the Options section: Task Status List (the stages a task moves through, including which status counts as complete and each status's progress percentage), Task Type List (e.g. Bug, Feature), and Task Environment List (e.g. Development, Production). Task priority is a fixed High/Medium/Low scale and isn't configured here. See Task Statuses and Workflows.

The Microsoft Teams link

A project links to exactly one Teams channel (see Teams Channel and Project Linking). When linked, Owners and Admins see a Microsoft Teams section with Remove from Teams channel. Unlinking removes only the connection — to move a project to a different channel, unlink here, then add the AB Projects tab in the new channel and choose the existing project.

Ownership, leaving, and deleting

• Step Down from Owner — the Owner picks a member to promote (to Admin or Owner) and confirms with Yes, promote & step down; the previous Owner becomes a regular Member. This is the only way ownership moves — see Role-Based Access Control.
• Leave Project — any Member or Admin can use Leave this project. If you're still in the linked Teams channel, the next sync re-adds you — the confirmation warns about exactly this.
• Danger Zone: Delete this project — Owner only, and only when no channel is linked. Deletion asks for a reason, requires Yes, delete permanently, and cannot be undone — all tasks and settings are removed. A finished project can simply be left in place instead.

Quick reference

Set the workflow lists early, keep the name and icon recognizable, and let the Teams link handle the rest — the settings page is mostly a place you visit once, then rarely.