-
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
Contributor Form Access Membership Selector #1038
Comments
does this include the member select forms (used when creating a user with MemberId fields and the email action)? if so this might take longer, since they have a few bugs + don't actually let you select role |
Ah, good call. Yes, it probably should. Feel free to bump it as appropriate. |
sorry for the late comments but I'm also not sure about this req
for the pub level, this makes sense to me: it's the set of forms that match the pub's pubtype. but at the stage or community level, should this just be a list of every form? and since that could potentially be a long list, should we use one of our multivalue combobox components instead of checkboxes? |
Yes. That's much better. Sorry, this is what happens when I "design" |
Motivation
Requirements
Acceptance Criteria
Mockups (if available)
Actual text to use in description:
Pub Level
Select the forms via which this member can edit and view this Pub. If no form is selected, they will only be able to view the Pub, and will only see fields added to the default Pub form for this type.
Stage Level
Select the forms via which this member can edit and view Pubs in this stage. If no form is selected, they will only be able to view Pubs in this stage, and will only see fields added to the default Pub form for a each Pub type.
Community Level
Selecting forms will give the member the ability to create Pubs in the community using the selected forms. If no forms are added, the contributor will not be able to create any Pubs, and will only be able to see Pubs they have access to either directly or at the stage level.
The text was updated successfully, but these errors were encountered: