AB Projects keeps confidential work confidential the same way Microsoft Teams does: by who is in the channel. There are no per-task privacy switches — if something must stay hidden from the wider team, it needs its own channel and project.
How confidentiality works today
Channel-scoped access
A project is linked one-to-one with a Teams channel, and membership follows that channel. People outside the channel aren't members and don't see the project at all — see Adding or Removing Members.
Microsoft identity
Access requires Microsoft sign-in (SSO via Microsoft Entra ID), so your organization's MFA and conditional-access policies apply — see SSO and Microsoft Login.
Audit trail
Every task change is recorded — who, when, old → new, with a reason — and posted to the linked Teams channel, giving you a durable, timestamped history for accountability.
Separate audiences, separate projects
Each AB product also keeps its own data store — AB Sales and AB Support can't read AB Projects records. Within AB Projects, separation is per channel/project.
Keep a workstream confidential, step by step
- Create a dedicated channel in Teams with only the people who should see the work (a private channel works well for this).
- Add the AB Projects tab to that channel — in the channel, click + (Add a tab) and choose AB Projects to link a project to it.
- Let membership sync. The project roster follows the channel automatically — whoever is in the channel becomes a member, and no one else does (see Adding or Removing Members).
What isn't a product feature
To set expectations clearly, these do not exist in AB Projects today:
| Often asked for | Status | What to do instead |
|---|---|---|
| Per-task “Private” visibility | Not available | Scope by project: use a dedicated channel (see Who Can See What?) |
| In-product NDA signing or acknowledgment | Not available | Handle NDAs contractually (below) |
| Document watermarking, access expiration | Not available | Use your Microsoft 365 information-protection tooling |
| Export approval / admin export controls | Not available | There is no built-in export at all — see Exporting Reports and Project Data |
NDAs, private deals, and Enterprise terms
NDAs (non-disclosure agreements), data-processing terms, data-residency commitments, and private commercial arrangements are handled commercially, as part of an Enterprise agreement — not as an in-app workflow. Plan and billing basics are covered in Managing Subscriptions and Billing; for anything contractual, contact our support team to discuss what can be put in place for your organization.
For sensitive work today: give it a dedicated channel with only the right people, and talk to us about Enterprise terms for anything that needs to be on paper.