Status. Proposed design only. Nothing in this vault is DG client approval. No application, service or test has been executed; every scenario is Not executed. Fees and dates are open.
T03 · Company-admin visibility is disclosed and scoped
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software |
| Layer / kind | API · E2E |
| Priority | P0 |
| Gates | A03, A04, A09 |
| Build step | Step-02-Identity-Membership-Roles |
| Decisions | Q02, Q08 |
Given
Separate A-B and A-C private engagements; A/B company admins, assigned/unassigned colleagues, C and removed members exercise each access context.
When
Open each company record and its messages/actions under every listed role and access context.
Then / oracle
Company admins have disclosed access to their own company engagements; other users need assignment/entitlement. A-B and A-C remain separate. Before publication and first private send, explain authorised company/admin access, that viewed or delivered information cannot be recalled, and: Acceptance opens a discussion. It is not a confidentiality agreement.
Evidence required
Disclosure at publication/first private send; positive A/B access and negative C/body-canary assertions.
Decision dependency (verbatim)
Q02/Q08: assignment granularity and disclosure/metadata policy. Agent agreement is not DG approval.
Source: TDD rev 1.3 (PDF); machine-readable in 10-Sources/tdd-bundle/. Back to Scenario-Index · Traceability-Matrix · integration dependencies in Dependency-and-Regression-Table.