Managing Project Settings

Managing Project Settings

Every project in AB Projects has a settings area where you tailor the workspace to how your team actually works — its identity, its task workflow, integrations, and the Microsoft Teams link. Anyone in the project can see the basics; the management and destructive actions are reserved for Owners and Admins.

Project identity

• Name & description — edit them inline from the project page (pencil → Save). The description is a short summary of what the project is for.
• Project icon — upload an image so the project is easy to recognize in your project list.
• Perma name — a short, unique URL slug for the project. Optional; if you leave it blank one is generated for you. It must be unique across AB Projects.
• Estimate time unit — choose Hours or Days. This is the unit used whenever someone enters an estimate on a task in this project.

Members and roles

• The settings area lists every joined member with their role badge (Owner, Admin, or Member).
• Adding, removing, and re-roling members is covered in Adding or Removing Members and Role-Based Access Control. Remember that membership is driven by the connected Teams channel — the roster mostly keeps itself in sync.

Task workflow (Options)

Each project defines its own task workflow. From the settings area you can open and configure:

• Task statuses — the stages a task moves through, including which status marks a task complete and the progress percentage each status represents.
• Task types — the categories of work in this project (e.g. Bug, Feature, Improvement).
• Task environments — the environments tasks apply to (e.g. Development, Staging, Production).

These lists are per project, so each team's board reflects its own process. (Task priority is a fixed scale — High, Medium, Low — and is not configured here.)

GitHub integration

Owners and Admins can connect the project to a GitHub repository so branches can be created straight from a task:

• Owner / Organization and Repository — the target repo.
• Personal Access Token — a GitHub PAT with repo scope (stored securely, shown as a password field).
• Default branch — the branch new task branches are based on (typically main).

Microsoft Teams link

• Each project is linked to exactly one Microsoft Teams channel. The settings area shows whether a channel is currently linked.
• An Owner or Admin can remove the project from the Teams channel (unlink). Unlinking does not delete the project or its tasks — it only removes the connection. To connect a different channel, unlink first, then add the AB Projects tab in the new channel.

Ownership, leaving, and deleting

• Step down from Owner — an Owner can't just demote themselves. To leave, an Owner promotes another member to Admin or Owner; the previous Owner becomes a regular Member and can then leave.
• Leave project — any Member or Admin can leave the project. They lose access, but an Owner can re-invite them later.
• Delete project (Danger Zone) — an Owner can permanently delete the project, but only when it is not linked to a Teams channel. Unlink the channel first. Deletion requires a reason and cannot be undone — all tasks and settings are removed.

Tips

• Configure task statuses, types, and environments early so the board matches how your team actually works from day one.
• Keep the project name and description current — they're what teammates see when picking a project.
• If you need to move a project to a different Teams channel, unlink first; the project and all its tasks are preserved.
• Deleting is owner-only and irreversible. If a project is just finished rather than a mistake, consider leaving it linked and inactive instead.

Kept current and properly scoped, project settings keep your workspace organized, your workflow accurate, and access exactly where it should be.