Handle different scenarios when user doesn't have access to page/feature
Open
Nobody has claimed this yet.
needs detail
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
As part of reviewing the permission schema, we need to ensure that features that are not accessible to a role are handled in one of the following ways:
- Can view the features/page, but everything is disabled
- Can view that the page exists, but cannot access (disabled menu link with tooltip, if accessed via URL no access page)
- Can't view the page, menu item or feature at all (404 if accessed directly)
Note:
These are the scenarios that I've worked with in the past, however they may not all apply within OpenFn but should be considered in terms of the permissions
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reviewing the permission schema and identifying the affected features and pages. Compare each case with the three access scenarios in the issue, then confirm which behavior applies within OpenFn; done means the applicable handling is agreed for inaccessible roles.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100