Send members to their own record after sign-in closes #665 #685
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
high priority
invalid
L
low priority
M
medium priority
needs refinement
optional
question
S
security
technical improvement
UX Improvement
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
local-it/mitgliederverwaltung!685
Loading…
Reference in a new issue
No description provided.
Delete branch "issue/mitgliederverwaltung-665"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
closes #665
Description of the implemented changes
The changes were:
Members (own_data) landed on the overview after signing in, were refused it and ended up on their account page with an error. They now start on their own member record, and their pages show the areas of that record (my data, my fees, sign-in & security) in a frame without links to pages they cannot open. Board, treasurer and admin start on the overview as before.
What has been changed?
Definition of Done
Code Quality
Accessibility
Testing
Additional Notes
CheckPagePermission.home_path/1is the one place that decides where a user starts: "/" for actors who may open it, otherwise the own member record when it is linked and may be opened, otherwise the own account page. Sign-in, the plug and the LiveView hook use it; a request for "/" by a member leads home without the access-denied message. Staff keep their account page as the target of a denied page.MvWeb.SelfServicedecides whether a page gets the self-service frame (the actor may not open/members) and which areas the actor has (each filtered through the page permission). Pages ask it instead of checking roles (DESIGN_GUIDELINES §15.4).Release: 1.6.0 (wave 1).
Proposed news entry (for the release file once #683 is merged):