New User Role
A
Amber Mollusk
There should be a User Role that allows a user/customer to utilize the knowledge base but not access the internal documentation side. Then the User Role will also be counted in the Analytics of the system. This role could also allow groups of customers to be created so the knowledge base will be customized to their org. For example, Customer 1 will be allowed to utilize the knowledge base, but only view information that they have access to.
E
Experienced Stoat
We will also benefit of this, as we use the knowledge base for customers
R
Ripe Unicorn
I wonder if creating a Helpjuice user group for just your customers would help you assign access for certain articles to just them. We use this feature to differentiate between articles intended for specific departments, teams, job roles, etc.
E
Experienced Stoat
Ripe Unicorn: We are doing this as workaround, but is very cumbersome. As you still have to assign the article to 'Internal' then 'internal viewer' and also having to manually create a group per each of your customers. It is confusing that the articles are set as internal but they are actually use by 'external'.
Photo Viewer
View photos in a modal
R
Ripe Unicorn
Experienced Stoat: First and foremost, I do not recognize the screenshot you provided, so it may be possible our accounts have different setups and the following recommendations don't apply to your team.
Generally speaking, we set up our private Helpjuice "categories" by assigning all of the potential user groups that would need to access any of the articles created within it. I then teach our "Draft Writers" to navigate to the "primary category" (in the Dashboard) they would like the article to live before clicking on the "New Article +" button. By default, this process only allows the pre-assigned group(s) to have access to the article without having to manually assign them every time a new article is created.
I created a mockup example (attached below) of what that process may look like. I hope this helps!
NOTE: This process means that any "internal" article would be accessible to ALL users, including everyone in the "Customers" group. So a similar process would need to be applied for staff. (Private "Staff" Category that a "Staff" group is all assigned to)
Photo Viewer
View photos in a modal
E
Experienced Stoat
Ripe Unicorn: thanks for your help!, having pre-defined user groups when creating a new article would actually help us. As we can assign them by default to only client groups (external).
Currently all the documentation is set as private, then we setup a customer as user, create a group with the company name and assign the user to this group with 'internal viewer' access.
It is a bit manual, long and not ideal but it is the best workaround we could come up with.
By the way, the screenshot comes changing the access to multiple categories.
Photo Viewer
View photos in a modal