Seeing an article is not permission to edit it.
Article A-80 · Harbour notice · Initial Staff viewing level · Action core.edit. Inspect inherited group rules before receiving a Joomla programming change.
Profile decision matrix
| Profile | Effective groups | Can view | Can edit |
|---|
Initial case: Editors + Contractors can see Staff content, yet the Contractor category denial blocks core.edit.
Four levels, one action
- Global configurationEditors group 8: core.edit Allowed
- Articles componentAll fixture groups inherit
- Harbour categoryContractors group 9: Denied initially
- Article A-80Editors: Allowed initially
Fixture group tree: Public 1 → Registered 2 → Editors 8 or Contractors 9. Group numbers are synthetic configuration choices.
Who can view, who can edit?
Expected receiving outcome
Check the expected outcome against the current controls.
This exercise checks view-level membership and core.edit for ordinary fixture users. Super User, edit-own, publication state, menu access and extension-specific actions belong in separate project cases.
Permission trace
An explicit denial from any effective group in the asset ancestry wins. With no denial, at least one allowance is needed. A viewing level does not grant core.edit.
Keep both groups. Change the article permission to Inherited: the category denial still blocks editing. Change the category denial to Inherited: the global Editors allowance can take effect.
Owner receiving record
Check an expected outcome before receiving it.
No record received.
What the record contains
- Configuration editionProfile, effective groups and rule values
- Two explicit outcomesCan view and can edit, each with its reason
- Receiving responsibilitySite owner acknowledgement and frozen evidence
Changing a control requires a fresh check. It preserves an already received record so the earlier result remains inspectable. Downloaded records contain only the synthetic values shown here.