# Knowledge base Rights Management

**URL:** https://community.zammad.org/t/knowledge-base-rights-management/3858
**Category:** Completed Features
**Created:** [January 23, 2020, 2:58pm UTC](https://community.zammad.org/t/knowledge-base-rights-management/3858 "2020-01-23T14:58:28Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![anon29275129](https://community.zammad.org/letter_avatar_proxy/v4/letter/a/4bbf92/32.png) [@anon29275129](https://community.zammad.org/u/anon29275129)
#### Post date: [January 23, 2020, 2:58pm UTC](https://community.zammad.org/t/knowledge-base-rights-management/3858/1 "2020-01-23T14:58:28Z")

</div>

Hello, is there a way to publish kb article only for certain user groups? It would also be great if editors are only allowed to edit certain areas in the kb. If that does not exist, is it planned to implement something like this? Thank you

---

<div class="post-metadata">

### Author: ![MrGeneration](https://community.zammad.org/user_avatar/community.zammad.org/mrgeneration/32/9260_2.png) [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [January 25, 2020, 9:28am UTC](https://community.zammad.org/t/knowledge-base-rights-management/3858/2 "2020-01-25T09:28:44Z")

</div>

We already have thhis kind of requests - you can find them here:

- [https://community.zammad.org/t/knowledgebase-for-logged-on-users-only/3169](https://community.zammad.org/t/knowledgebase-for-logged-on-users-only/3169)
- [https://community.zammad.org/t/knowledgebase-visibility-based-on-roles-groups/2778](https://community.zammad.org/t/knowledgebase-visibility-based-on-roles-groups/2778)

* * *

We have this on our list. However, there’s no timeline for this and the scope of functionality is unknown at this moment.

If you want to scubscribe to the enhancement issue, you can find it here:

> <https://github.com/zammad/zammad/issues/2603>
>
> \<!--
> Hi there - thanks for filing an issue. Please ensure the following things …before creating an issue - thank you! 🤓
> 
> Since november 15th we handle all requests, except real bugs, at our community board.
> Full explanation: https://community.zammad.org/t/major-change-regarding-github-issues-community-board/21
> 
> Please post:
> \- Feature requests
> \- Development questions
> \- Technical questions
> 
> on the board -\> https://community.zammad.org !
> 
> 
> If you think you hit a bug, please continue:
> \- Search existing issues and the CHANGELOG.md for your issue - there might be a solution already
> \- Make sure to use the latest version of Zammad if possible
> \- Add the \`log/production.log\` file from your system. Attention: Make sure no confidential data is in it!
> \- Please write the issue in english
> \- Don't remove the template - otherwise we will close the issue without further comments
> \- Ask questions about Zammad configuration and usage at our mailinglist. See: https://zammad.org/participate
> 
> Note: We always do our best. Unfortunately, sometimes there are too many requests and we can't handle everything at once. If you want to prioritize/escalate your issue, you can do so by means of a support contract (see https://zammad.com/pricing#selfhosted).
> 
> \* The upper textblock will be removed automatically when you submit your issue \*
> \--\>
> 
> \### Infos:
> 
> \* Used Zammad version: 3.0
> \* Installation method (source, package, ..): any
> \* Operating system: any
> \* Database + version: any
> \* Elasticsearch version: any
> \* Browser + version: any
> \* Ticket-ID: #1041496, #1088929 
> 
> \*Note:\* This has been moved from our internal git ( 251 ) to Github in order to only have one enhancement issue at the time.
> 
> 
> \### Desired behavior / enhancement:
> Currently there is only the subdivision of rights between reading and editing agents.
> 
> Usecase: In an organization several departments work with Zammad. Each department has different internal requirements. The internal specifications of one department must not be available to the entire organization.
> 
> Implementation proposal: It should be possible to select the currently available roles for each category:
> 
> !\[image\](https://user-images.githubusercontent.com/6549061/59390844-b8ef7600-8d72-11e9-9bf8-38e1afe525c8.png)

---

<div class="post-metadata">

### Author: ![Tobimuc](https://community.zammad.org/letter_avatar_proxy/v4/letter/t/ecd19e/32.png) [@Tobimuc](https://community.zammad.org/u/Tobimuc)
#### Post date: [December 1, 2020, 10:49am UTC](https://community.zammad.org/t/knowledge-base-rights-management/3858/3 "2020-12-01T10:49:51Z")

</div>

Hello,

is there any new timeline to implement this Feature?

Thx  
Tobi

---

<div class="post-metadata">

### Author: ![benmo](https://community.zammad.org/user_avatar/community.zammad.org/benmo/32/3449_2.png) [@benmo](https://community.zammad.org/u/benmo)
#### Post date: [December 1, 2020, 11:53am UTC](https://community.zammad.org/t/knowledge-base-rights-management/3858/4 "2020-12-01T11:53:25Z")

</div>

They never provide ETAs or timelines. You just have to wait (or contribute).

Just like @MrGeneration said, you can subscribe to the GitHub issue if you want to stay up to date regarding this feature request: [https://github.com/zammad/zammad/issues/2603](https://github.com/zammad/zammad/issues/2603)

---

<div class="post-metadata">

### Author: ![system](https://community.zammad.org/uploads/default/original/1X/5c5afaea2d23f811dbec33cd4edb02fa29d3262f.png) [@system](https://community.zammad.org/u/system)
#### Post date: [March 15, 2021, 6:58am UTC](https://community.zammad.org/t/knowledge-base-rights-management/3858/5 "2021-03-15T06:58:33Z")

</div>

This topic was automatically closed after 416 days. New replies are no longer allowed.

---

<div class="post-metadata">

### Author: ![ckatterl](https://community.zammad.org/user_avatar/community.zammad.org/ckatterl/32/1736_2.png) [@ckatterl](https://community.zammad.org/u/ckatterl)
#### Post date: [September 25, 2019, 9:27am UTC](https://community.zammad.org/t/knowledge-base-rights-management/3858/6 "2019-09-25T09:27:33Z")

</div>

Hello,

for the Knowledgebase it would be nice to have an option to make an article visible for logged on users only. In the moment (Zammad 3.1) an article can be _really_ public or limited for editors/agents only.  
Many times, there’s a need to make content available for intra-company use only.

Hope to see this soon 🙂

BR and thanks a lot,

Christian

---

<div class="post-metadata">

### Author: ![MrGeneration](https://community.zammad.org/user_avatar/community.zammad.org/mrgeneration/32/9260_2.png) [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [September 25, 2019, 11:16am UTC](https://community.zammad.org/t/knowledge-base-rights-management/3858/7 "2019-09-25T11:16:41Z")

</div>

Heya,

this is already covered by [Knowledgebase Visibility Based on Roles / Groups](https://community.zammad.org/t/knowledgebase-visibility-based-on-roles-groups/2778)

Closing now 🙂

---

<div class="post-metadata">

### Author: ![beeing](https://community.zammad.org/user_avatar/community.zammad.org/beeing/32/3140_2.png) [@beeing](https://community.zammad.org/u/beeing)
#### Post date: [July 11, 2019, 3:19am UTC](https://community.zammad.org/t/knowledge-base-rights-management/3858/8 "2019-07-11T03:19:18Z")

</div>

In this modal, the Visibility is fixed to Internal or Public,

 ![image](https://community.zammad.org/uploads/default/original/2X/e/e7fd30c4104e59ab65194db99d6617df7fd23283.png)

It would be super-useful if the roles / group can be used in here as well.

Also, Public is meant as Customers logins or non-registered users?

A suggestion would be to separate Public and a “All Users” Role.

Thanks in advance!

---

<div class="post-metadata">

### Author: ![MrGeneration](https://community.zammad.org/user_avatar/community.zammad.org/mrgeneration/32/9260_2.png) [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [July 15, 2019, 3:49pm UTC](https://community.zammad.org/t/knowledge-base-rights-management/3858/9 "2019-07-15T15:49:18Z")

</div>

> [@beeing](#):
>
> It would be super-useful if the roles / group can be used in here as well.

I think this is covered by this enhancement issue:

> <https://github.com/zammad/zammad/issues/2603>
>
> \<!--
> Hi there - thanks for filing an issue. Please ensure the following things …before creating an issue - thank you! 🤓
> 
> Since november 15th we handle all requests, except real bugs, at our community board.
> Full explanation: https://community.zammad.org/t/major-change-regarding-github-issues-community-board/21
> 
> Please post:
> \- Feature requests
> \- Development questions
> \- Technical questions
> 
> on the board -\> https://community.zammad.org !
> 
> 
> If you think you hit a bug, please continue:
> \- Search existing issues and the CHANGELOG.md for your issue - there might be a solution already
> \- Make sure to use the latest version of Zammad if possible
> \- Add the \`log/production.log\` file from your system. Attention: Make sure no confidential data is in it!
> \- Please write the issue in english
> \- Don't remove the template - otherwise we will close the issue without further comments
> \- Ask questions about Zammad configuration and usage at our mailinglist. See: https://zammad.org/participate
> 
> Note: We always do our best. Unfortunately, sometimes there are too many requests and we can't handle everything at once. If you want to prioritize/escalate your issue, you can do so by means of a support contract (see https://zammad.com/pricing#selfhosted).
> 
> \* The upper textblock will be removed automatically when you submit your issue \*
> \--\>
> 
> \### Infos:
> 
> \* Used Zammad version: 3.0
> \* Installation method (source, package, ..): any
> \* Operating system: any
> \* Database + version: any
> \* Elasticsearch version: any
> \* Browser + version: any
> \* Ticket-ID: #1041496, #1088929 
> 
> \*Note:\* This has been moved from our internal git ( 251 ) to Github in order to only have one enhancement issue at the time.
> 
> 
> \### Desired behavior / enhancement:
> Currently there is only the subdivision of rights between reading and editing agents.
> 
> Usecase: In an organization several departments work with Zammad. Each department has different internal requirements. The internal specifications of one department must not be available to the entire organization.
> 
> Implementation proposal: It should be possible to select the currently available roles for each category:
> 
> !\[image\](https://user-images.githubusercontent.com/6549061/59390844-b8ef7600-8d72-11e9-9bf8-38e1afe525c8.png)

Personally I think it would also be possible to have several customer roles to achieve customer based dividing of categories. But I guess this will at some point get horrible in terms of overview.

> [@beeing](#):
>
> Also, Public is meant as Customers logins or non-registered users?

Public means any not authenticated or customer user, correct.  
We currently don’t make a differences between “anonymous” and a customer. (see below comment and issue)

> [@beeing](#):
>
> A suggestion would be to separate Public and a “All Users” Role.

I think this partly is covered by this enhancement issue:

> <https://github.com/zammad/zammad/issues/2613>
>
> \<!--
> Hi there - thanks for filing an issue. Please ensure the following things …before creating an issue - thank you! 🤓
> 
> Since november 15th we handle all requests, except real bugs, at our community board.
> Full explanation: https://community.zammad.org/t/major-change-regarding-github-issues-community-board/21
> 
> Please post:
> \- Feature requests
> \- Development questions
> \- Technical questions
> 
> on the board -\> https://community.zammad.org !
> 
> 
> If you think you hit a bug, please continue:
> \- Search existing issues and the CHANGELOG.md for your issue - there might be a solution already
> \- Make sure to use the latest version of Zammad if possible
> \- Add the \`log/production.log\` file from your system. Attention: Make sure no confidential data is in it!
> \- Please write the issue in english
> \- Don't remove the template - otherwise we will close the issue without further comments
> \- Ask questions about Zammad configuration and usage at our mailinglist. See: https://zammad.org/participate
> 
> Note: We always do our best. Unfortunately, sometimes there are too many requests and we can't handle everything at once. If you want to prioritize/escalate your issue, you can do so by means of a support contract (see https://zammad.com/pricing#selfhosted).
> 
> \* The upper textblock will be removed automatically when you submit your issue \*
> \--\>
> 
> \### Infos:
> 
> \* Used Zammad version: 3.0
> \* Installation method (source, package, ..): any
> \* Operating system: any
> \* Database + version: any 
> \* Elasticsearch version: any
> \* Browser + version: any
> \* Ticket-ID: 
> 
> \*Note:\* This has been moved from our internal git ( 222 ) to Github in order to only have one enhancement issue at the time.
> 
> 
> \### Desired behavior:
> 
> There should be an option that denies anonymous access to the public knowledgebase.
> You should be able to protect it by e.g. a password or user login e.g. via Office365 and local database).
> 
> Preferbly the login interface will stay in the same look and feel of the knowledgebase.

---

<div class="post-metadata">

### Author: ![beeing](https://community.zammad.org/user_avatar/community.zammad.org/beeing/32/3140_2.png) [@beeing](https://community.zammad.org/u/beeing)
#### Post date: [July 16, 2019, 12:05am UTC](https://community.zammad.org/t/knowledge-base-rights-management/3858/10 "2019-07-16T00:05:43Z")

</div>

Great, thanks for the reply @MrGeneration

Looking forward to test and feedback the implementation.

---

<div class="post-metadata">

### Author: ![ryanjeff](https://community.zammad.org/user_avatar/community.zammad.org/ryanjeff/32/2119_2.png) [@ryanjeff](https://community.zammad.org/u/ryanjeff)
#### Post date: [January 30, 2020, 3:44pm UTC](https://community.zammad.org/t/knowledge-base-rights-management/3858/11 "2020-01-30T15:44:30Z")

</div>

Hi,

I tried to find the possibility to add the visibility in knowledge based for specific Organization is there a way that we can do that, not sure if this is already implemented.

Please do let me know. because inside our zammad support system we have different client and inside different client we have different business process that must not be in public or share to other organization.

Please let me know.

Thank you in advance.

---

<div class="post-metadata">

### Author: ![fleverest](https://community.zammad.org/user_avatar/community.zammad.org/fleverest/32/2204_2.png) [@fleverest](https://community.zammad.org/u/fleverest)
#### Post date: [January 31, 2020, 5:29am UTC](https://community.zammad.org/t/knowledge-base-rights-management/3858/12 "2020-01-31T05:29:36Z")

</div>

Or even role-based visibility for internal categories would be very useful

---

<div class="post-metadata">

### Author: ![MrGeneration](https://community.zammad.org/user_avatar/community.zammad.org/mrgeneration/32/9260_2.png) [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [February 3, 2020, 12:35pm UTC](https://community.zammad.org/t/knowledge-base-rights-management/3858/13 "2020-02-03T12:35:23Z")

</div>

Just for your information, we already have this on our list:

> <https://github.com/zammad/zammad/issues/2603>
>
> \<!--
> Hi there - thanks for filing an issue. Please ensure the following things …before creating an issue - thank you! 🤓
> 
> Since november 15th we handle all requests, except real bugs, at our community board.
> Full explanation: https://community.zammad.org/t/major-change-regarding-github-issues-community-board/21
> 
> Please post:
> \- Feature requests
> \- Development questions
> \- Technical questions
> 
> on the board -\> https://community.zammad.org !
> 
> 
> If you think you hit a bug, please continue:
> \- Search existing issues and the CHANGELOG.md for your issue - there might be a solution already
> \- Make sure to use the latest version of Zammad if possible
> \- Add the \`log/production.log\` file from your system. Attention: Make sure no confidential data is in it!
> \- Please write the issue in english
> \- Don't remove the template - otherwise we will close the issue without further comments
> \- Ask questions about Zammad configuration and usage at our mailinglist. See: https://zammad.org/participate
> 
> Note: We always do our best. Unfortunately, sometimes there are too many requests and we can't handle everything at once. If you want to prioritize/escalate your issue, you can do so by means of a support contract (see https://zammad.com/pricing#selfhosted).
> 
> \* The upper textblock will be removed automatically when you submit your issue \*
> \--\>
> 
> \### Infos:
> 
> \* Used Zammad version: 3.0
> \* Installation method (source, package, ..): any
> \* Operating system: any
> \* Database + version: any
> \* Elasticsearch version: any
> \* Browser + version: any
> \* Ticket-ID: #1041496, #1088929 
> 
> \*Note:\* This has been moved from our internal git ( 251 ) to Github in order to only have one enhancement issue at the time.
> 
> 
> \### Desired behavior / enhancement:
> Currently there is only the subdivision of rights between reading and editing agents.
> 
> Usecase: In an organization several departments work with Zammad. Each department has different internal requirements. The internal specifications of one department must not be available to the entire organization.
> 
> Implementation proposal: It should be possible to select the currently available roles for each category:
> 
> !\[image\](https://user-images.githubusercontent.com/6549061/59390844-b8ef7600-8d72-11e9-9bf8-38e1afe525c8.png)

ETA is unknown.

---

<div class="post-metadata">

### Author: ![herzkerl](https://community.zammad.org/user_avatar/community.zammad.org/herzkerl/32/8167_2.png) [@herzkerl](https://community.zammad.org/u/herzkerl)
#### Post date: [March 3, 2020, 7:26am UTC](https://community.zammad.org/t/knowledge-base-rights-management/3858/14 "2020-03-03T07:26:51Z")

</div>

I’d also love visibility based on organisation—so we could easily have customised articles for some customers. Of course we could also create roles for that purpose, but it’d be nicer this way 🙂

---

<div class="post-metadata">

### Author: ![sinichi19](https://community.zammad.org/user_avatar/community.zammad.org/sinichi19/32/2197_2.png) [@sinichi19](https://community.zammad.org/u/sinichi19)
#### Post date: [March 11, 2020, 8:10am UTC](https://community.zammad.org/t/knowledge-base-rights-management/3858/15 "2020-03-11T08:10:23Z")

</div>

Visibility for registered customer only we wait before we use the Knowledge base our KB is still on draft because of some details cant publish in public.

thank you

---

<div class="post-metadata">

### Author: ![iancrown](https://community.zammad.org/letter_avatar_proxy/v4/letter/i/e9a140/32.png) [@iancrown](https://community.zammad.org/u/iancrown)
#### Post date: [May 17, 2020, 9:53am UTC](https://community.zammad.org/t/knowledge-base-rights-management/3858/16 "2020-05-17T09:53:18Z")

</div>

We also need this feature. We have customers in different countries and want to make only relevant information available to them.  
Thanks

---

<div class="post-metadata">

### Author: ![McMuffin](https://community.zammad.org/letter_avatar_proxy/v4/letter/m/9de053/32.png) [@McMuffin](https://community.zammad.org/u/McMuffin)
#### Post date: [December 8, 2020, 9:06am UTC](https://community.zammad.org/t/knowledge-base-rights-management/3858/17 "2020-12-08T09:06:07Z")

</div>

It would be great if you could also set the visibility for different editor groups.

We have editors that shouldn’t be able to see or edit certain entries.

For example if an editor from the finance department does not need to see the entries for the IT department. It would help that no accidentally edits or removes something that they shouldn’t have edit rights to.

---

<div class="post-metadata">

### Author: ![Mr\_P](https://community.zammad.org/user_avatar/community.zammad.org/mr_p/32/1765_2.png) [@Mr\_P](https://community.zammad.org/u/Mr_P)
#### Post date: [September 11, 2019, 12:06pm UTC](https://community.zammad.org/t/knowledge-base-rights-management/3858/18 "2019-09-11T12:06:38Z")

</div>

Is it possible to add “Admins” to the visibility of knowledge base entries?

![grafik](https://community.zammad.org/uploads/default/original/2X/5/5f2d4ce75bfae6ebafb7e43433058061f46535fb.png)

I added some instructions to the knowledge base, how to configure some zammad settings…  
Its not uninteresting for editors or agents, but for admins.

Greetings, Daniel.

---

<div class="post-metadata">

### Author: ![MrGeneration](https://community.zammad.org/user_avatar/community.zammad.org/mrgeneration/32/9260_2.png) [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [September 11, 2019, 1:03pm UTC](https://community.zammad.org/t/knowledge-base-rights-management/3858/19 "2019-09-11T13:03:16Z")

</div>

In my opinion this is already covered by this request:  
[https://community.zammad.org/t/knowledgebase-visibility-based-on-roles-groups/2778](https://community.zammad.org/t/knowledgebase-visibility-based-on-roles-groups/2778)

---

<div class="post-metadata">

### Author: ![Mr\_P](https://community.zammad.org/user_avatar/community.zammad.org/mr_p/32/1765_2.png) [@Mr\_P](https://community.zammad.org/u/Mr_P)
#### Post date: [September 11, 2019, 2:46pm UTC](https://community.zammad.org/t/knowledge-base-rights-management/3858/20 "2019-09-11T14:46:17Z")

</div>

True story… Thx and push. 😊

[Next page](https://community.zammad.org/t/knowledge-base-rights-management/3858.md?page=2)