DNN engagement acceptance case
Keep portal scope in every access decision.
Review the page and module together. Matching role names on another portal do not grant access here.
12Target portal · North
40 / 70Page / module identity
r4Current access contract
Named acceptance identities
| Test identity | Portal membership | Role scope | Initial decision |
|---|---|---|---|
| North dealerN-08 | North · 12 | Members + Dealers | Allowed |
| North memberN-19 | North · 12 | Members | Module blocked |
| South dealerS-04 | South · 18 | Members + Dealers | Portal blocked |
One explicit change request
Page 40 permits Members. Module 70 permits Dealers. Add Members to the module candidate, run all three identities and retain the approval for the exact revision.
Page 40 / module 70 · North portal 12
Test the candidate before approval.
The exercise uses explicit allow lists and portal membership. Review inherited rules, denies and privileged accounts separately in the installed DNN site.
Candidate module rule
- Page allow list
- Members
- Module base rule
- Dealers
- Candidate revision
- r4
Expected access contract
North dealer: allowed.
North member: allowed after the change.
South dealer: blocked from North.
| Identity | Candidate result |
|---|---|
| Run evaluation to inspect the decisions. | |
No current evaluation.
Retained acceptance evidence
Keep the approved permission matrix.
The receipt identifies the accepted portal, revision and access outcomes. A later candidate edit cannot change the retained decision.
No approved matrix yet
Evaluate the expected three-identity contract and approve as Portal owner.
Receipt not created.