-
Notifications
You must be signed in to change notification settings - Fork 6
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
Update contributor role permissions to include form view/edit layer #1037
Comments
should this be "Can add other contributors to the pub"? if not, does it mean all pubs with the pub type(s) of the form(s)?
create/add shouldn't be a problem. seeing related pubs is still tricky, since it makes calculating whether a user has view access a potentially quite expensive query. right now we're just handling that by embedding the related pubs into a the pub details page, to depth 2. if that's not sufficient anymore, we could allow configuration of the depth/whether to embed related pubs at all at the form_element level as part of the new view configuration
when a contributor creates a pub, should we give them some kind of membership to it? maybe that's a new setting on the submit buttons or the form itself? |
Yup, good catch, thanks! Updated.
Updated. We only need to replicate the functionality on view/edit pages, not via overall permissions, because when someone creates a new related pub, we'll add a membership to it for them, as you suggested. This creates an edge case if there are multiple contributors to a pub who each add related pubs, but we think that's okay, and certainly for now, if they can still edit those via the "from" pub view/update page.
Yes... Will add another ticket for this. |
does "are controlled by" mean "have the same pub type as"? |
Motivation
So admins can restrict contributors to viewing/editing pubs using specific forms -- implicitly, this means they can also only see/edit pubs of the types of forms they have access to.
Requirements
Acceptance Criteria
The text was updated successfully, but these errors were encountered: