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

Identify Roles and Permissions to Use in Wagtail #1120

Closed
AmyKort opened this issue Jul 3, 2017 · 7 comments
Closed

Identify Roles and Permissions to Use in Wagtail #1120

AmyKort opened this issue Jul 3, 2017 · 7 comments
Assignees

Comments

@AmyKort
Copy link

AmyKort commented Jul 3, 2017

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.

@AmyKort AmyKort added this to the Sprint 3.1 milestone Jul 3, 2017
@AmyKort
Copy link
Author

AmyKort commented Jul 5, 2017

@gsmaragdis

@patphongs
Copy link
Member

patphongs commented Jul 14, 2017

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.

@AmyKort AmyKort modified the milestones: Sprint 3.2, Sprint 3.1 Jul 18, 2017
@AmyKort
Copy link
Author

AmyKort commented Jul 24, 2017

@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?

@patphongs
Copy link
Member

@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.

@AmyKort
Copy link
Author

AmyKort commented Jul 27, 2017

Great! Since we've completed our documentation of the permissions requirements of our content managers, we can close this issue.

@patphongs
Copy link
Member

Reopening this issue to implement new Wagtail roles and permissions.

@patphongs
Copy link
Member

In order to identify roles and permissions, we need to develop a list of page owners. Closing in favor of this ticket: #4155

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants