Confidentiality and Enterprise Agreements
AB Projects keeps work confidential through Microsoft Teams channel scoping and Microsoft identity — not through per-task privacy controls. This article explains how confidentiality actually works today, what isn't a product feature, and how NDAs and private commercial terms are handled.
How confidentiality works today
- Channel-scoped access. A project is linked one-to-one with a Teams channel, and membership follows that channel. People who aren't in the channel aren't members and don't see the project's tasks — so confidentiality is controlled by who is in the Teams channel (see Becoming a Project Member in AB Projects).
- Microsoft identity. Access is via Microsoft SSO / Microsoft Entra ID, so your organization's authentication, MFA, and conditional-access policies apply (see SSO and Microsoft Login).
- Audit trail. Every task change is recorded with who/when/old→new and a required reason, and posted to the linked Teams channel — a durable, timestamped history for accountability (see Adaptive Cards and Task Previews).
- Separate projects for separate audiences. To keep a workstream confidential from the wider team, use a dedicated Teams channel/project with only the people who should see it.
What isn't a product feature
To set expectations clearly, AB Projects does not currently offer:
- Per-task "Private" visibility — there is no task-level privacy flag; tasks are visible to the project's members. Confidentiality is at the project/channel level, not per task.
- In-product NDA workflows — there's no NDA acknowledgment, signing, or NDA-status audit report inside AB Projects.
- Document watermarking or access expiration — these are not available.
- Admin controls for "who can create private tasks" or export approval — these don't exist (there is also no built-in export; see Exporting and Accessing Project Data).
NDAs, private deals, and Enterprise terms
- NDAs, data-processing terms, data-residency, and private commercial arrangements are handled as part of an Enterprise agreement — commercially, not as an in-app workflow (see Managing Subscriptions & Billing).
- If you have confidentiality, compliance, or contractual requirements, contact your account representative or our support team to discuss what can be put in place for your organization.
For sensitive work today, scope it to a dedicated Teams channel with only the right people — and talk to us about Enterprise terms for anything contractual.