Allow Course Editors to save ORA and Teams settings in Pages & Resources
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python, typescript
- Domain
- authorization
Research direction
The issue names PageSettingButton.jsx and the ORA and Teams settings modals, and links a related route guard issue at openedx/openedx-authz#286. Read the existing permission checks in the modal and backend paths, then decide whether these settings require advanced-settings permission or also allow Course Editors. Done means all four apps have consistent UI and backend permissions, a Course Editor cannot be offered a failing save, and tests cover the behavior.
Written by the indexing model from the issue text.
Description
Description
Some settings are split between Advanced Settings and Pages & Resources. The ORA and Teams settings modals in Pages & Resources only validate the advanced_settings permission, so a Course Editor cannot save them even though they can open Pages & Resources.
Current Behavior
A Course Editor changes ORA or Teams settings in Pages & Resources and saving fails. The frontend already disables the gear button for Progress and Wiki:
// PageSettingButton.jsx:54
const isGearDisabled = (id === 'progress' || id === 'wiki') && !canManageAdvancedSettings;
That does not cover the deep link to the modal (see the related route-guard issue).
Expected Behavior
For ORA, Teams, Progress and Wiki, the UI and the backend agree on which permission is required, and an Editor is never offered a save that is guaranteed to fail.
Steps to reproduce
- Log in as a Course Editor.
- Open Pages & Resources and open the Teams (or ORA) settings.
- Change a setting and save.
- Observe that the save fails.
Acceptance Criteria
- A decision is made on which permission governs ORA, Teams, Progress and Wiki settings (advanced settings only, or both).
- If advanced-settings-only: the controls are disabled in the modal itself, not only in the gear button, so deep links are covered.
- If both are accepted: the backend allows either permission for these four apps.
- A Course Editor either saves successfully or sees the controls disabled, never a failing save.
- Tests are added or updated.
Proposed Solution
Pick one of:
- Disable the controls directly in the modals for the four apps.
- Accept both permissions on the backend for the four apps.
Related Issues
Related to openedx/openedx-authz#286 (route guard finding).
- Dominant language
- Python
- Stars
- 0
- Forks
- 10
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 21
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openedx/openedx-authz
-
willow
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openedx/openedx-authz#597 ·
Maintainers usually reply within 1 day
-
willow
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
openedx/openedx-authz#579 ·
Maintainers usually reply within 1 day
-
willow
Difficulty 4/5 1-2 days Newbie friendliness 48/100
openedx/openedx-authz#600 ·
Maintainers usually reply within 1 day
-
willow
Difficulty 3/5 1-2 days Newbie friendliness 74/100
openedx/openedx-authz#599 ·
Maintainers usually reply within 1 day
-
willow
Difficulty 3/5 1-2 days Newbie friendliness 66/100
openedx/openedx-authz#598 ·
Maintainers usually reply within 1 day
All issues in openedx/openedx-authz
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
area:docs documentation effort:M ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
mczielinski/ob-analytics#423 ·
Maintainers usually reply within 1 day
-
infra
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 3 days
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
vllm-project/vllm-ascend#21033 ·
Maintainers usually reply within 1 day