Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce a distinction between the 'read' and 'update' permissions #806

Closed
avernet opened this issue Feb 6, 2013 · 0 comments
Closed

Comments

@avernet
Copy link
Collaborator

avernet commented Feb 6, 2013

Since 4.0, Form Builder supports CRUD permissions, but read and update have been "packaged" together. This will enable users to set those separately. Changes:

  • don't allow giving the update without the read permission
  • require the update permission to access the edit page
  • require the read permission to access the view page
  • if users have the read but not the update permission, the summary page sends them to the view page instead of the edit page
  • if users have the read but not the update permission, the view page doesn't show the button to go to the edit page
@ghost ghost assigned avernet Feb 6, 2013
avernet added a commit that referenced this issue Apr 5, 2013
- introduce classes to make it easier to locate elements
- implement a "reasonable" use case with two roles, clerk and admin
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant