How to organise space permissions and restrictions for a Knowledge Base?

[Anja Summa]

We are working on a company-internal Knowledge Base and have been struggling with Confluence's permissions/restrictions.

What do we want to achieve?

We want to have the following setup of permissions:

1. "everyone" (within the company network) can view

2. certain people can comment when logged in

3. there is a certain area where certain people can create/edit articles (or delete their own)

What worked?

The first two steps (with the help of Windows Active Directory).

What doesn't work?

Step 3 - we don't want many people to be able to create or edit articles in the Knowledge Base. We want to make sure that the articles have a certain quality and only contain compliant solutions and so on. Thus, we need some kind of monitoring.

The idea was to grant write/edit access to those applicable for the full space and then restrict their access to most pages. We wanted to use page restrictions inheritance for that. However, we just found out that inheritance is not applicable to edit restrictions, just to viewing.

So what we COULD do is put an additional restriction on each and every article in the Knowledge Base. But that is tedious and easily forgotten when creating a new article.

Is there anything else we could do? Are there any best practices? Any mechanism that was created for that purpose?