-
Notifications
You must be signed in to change notification settings - Fork 40
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
Identify Roles and Permissions to Use in Wagtail #1120
Comments
Had a meeting with @gsmaragdis. From our discussion, it appears that there are no additional wagtail groups needed. Currently there are 2, which is editor (no publish rights) and moderator (publish rights). Everyone will be able to upload images and documents. Here's some quick notes from conversation with George: https://docs.google.com/document/d/1nqlosBSmX4DNfxJ_pY98QiB1tl6awRWPCUOnAJbICyA/edit# Also met with @jameshupp to discuss and he also agreed that this issue is now more of a formal workflow and content governance documentation for the FEC's content team. He will be working with the content team to draft this up. This documentation is extra helpful to keep current content owners aware of the formal processes and procedures as well as getting new content owners up to speed. Quick note: I have yet to speak with Press and Public records about their desire for any additional wagtail permissions. I hope to get this set up sometime next week. |
@patphongs Thanks for the great notes! With the meetings you had last week with Press and Public Records, are we ready to take next steps? |
@AmyKort I think at the very least we could start creating the permission groups. Then we can pull the trigger on actually implementing the permission groups once everyone is happy with the proposed permissions that are set. |
Great! Since we've completed our documentation of the permissions requirements of our content managers, we can close this issue. |
Reopening this issue to implement new Wagtail roles and permissions. |
In order to identify roles and permissions, we need to develop a list of page owners. Closing in favor of this ticket: #4155 |
To ensure only approved and public-ready content is posted on the website, we need to identify roles for content managers and permissions to allow managers to effectively curate the content that appears on the site.
The text was updated successfully, but these errors were encountered: