# Managing Project Week project descriptions

**URL:** <https://discourse.slicer.org/t/managing-project-week-project-descriptions/39666>\
**Category:** Project Week\
**Created:** [June 6, 2017, 6:12pm UTC](https://discourse.slicer.org/t/managing-project-week-project-descriptions/39666 "2017-06-06T18:12:49Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ihnorton](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ihnorton/32/9_2.png) [@ihnorton](https://discourse.slicer.org/u/ihnorton)\
**Post date:** [June 7, 2017, 4:47pm UTC](https://discourse.slicer.org/t/managing-project-week-project-descriptions/39666/3 "2017-06-07T16:47:30Z")

</div>

> [@About the Project Week category](https://discourse.slicer.org/t/about-the-project-week-category/415/1):
>
> we did NOT have a clear pathway to manage edit rights on existing “pages” (or post)

FWIW, the way to do this currently is to:

- restrict “See” permission for the category to the ProjectWeek group
- make all posts into Wiki posts
- give every group member “minimum wiki edit” trust (TL1)
- then everyone in the group could edit all posts.

When the Discourse platform updates to the next release (I don’t know ETA) then it will be possible to have Wiki posts visible outside the group, but only editable by members of group with “Create” permission on the category:

> <https://github.com/discourse/discourse/commit/addc85cd08bbdab5e8cae8b5d041caa94791c67a>

---

_[View the full topic](https://discourse.slicer.org/t/managing-project-week-project-descriptions/39666)._