damoe
June 30, 2020, 9:08am
21
Currently, knowledge base articles can be unpublished, internal only or “public”. Public means it’s visible to anybody on the internet.
What we would like to have is an additional setting “users”: Only signed in customers (and of course agents) can see the knowledgebase articles.
1 Like
This has been discussed a few times, including:
https://community.zammad.org/t/knowledgebase-visibility-based-on-roles-groups/2778/
Also, there’s already a feature request on Github:
opened 10:33PM - 12 Jun 19 UTC
closed 11:15AM - 24 Feb 22 UTC
enhancement
knowledge base
<!--
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)
Please note that Zammad doesn’t provide public roadmaps. It’s done when it’s done.
Personally, I also hope that it won’t get done rater sooner than later
damoe
June 30, 2020, 9:56am
23
Thanks for linking this - I didn’t spot it on a brief search.
1 Like
Is there any status reports on the feature request you linked to? The FR just says to discuss it in the forums and every discussion in the forum links back to github without anyone actually mentioning where things are with implementing the request
The state is specification required
as the label says.
We in general do not provide any ETAs.
If you absolutely can’t wait for that function, you always have the possibility to sponsor a specific function if you want to.