Skip to content

Handover correction: a group is a valid object for SendAs / SendOnBehalf #346

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AdaWorldAPI merged 1 commit into from
Oct 10, 2026
Merged

Handover correction: a group is a valid object for SendAs / SendOnBehalf #346

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions .claude/handovers/2026-10-10-1600-hubspo-rs-to-ogar-dir-sim.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,3 +77,16 @@ permission).
That is enough for reading a shared inbox (HubSPO-rs D-MAIL-5).
- **Send-as / on behalf:** not offered until W-1 exists. HubSPO-rs will not
keep a second copy of AD's delegation lists.

## Correction (2026-10-10, after OGAR #344 V17)

- **W-1's violation list was too broad.** It named "a group as owner (a
group has no mailbox of its own)" as a violation for every right. That
holds for **FullAccess only**. Exchange grants SendAs and SendOnBehalf on
distribution groups, so a group is a valid object for those two rights.
V17 (`docs/DIRECTORY-SIMULATION-POC.md`) has it right.
- **Deny entries.** Exchange allows deny entries on FullAccess. A model that
reads grants only must not apply a grant a witness also denies: drop it,
or hold it as a violation (review on #344).
- **Transitive group trustees** depend on nested-group expansion, which is
lance-graph handover W-4.
Loading