Knowledgebase Page restrictions by Company

[Damon Gaylor]

We work work about 10 customers currently and provide software solutions for their business.  We currently document the customizations and general user documents (tips) in confluence pages.  However this documentation varies by client based on their unique needs.  e.g. 'How to add a user' may vary by customer.

It looks like we can only have one knowledgebase per Service Desk project.  Can we use standard Confluence permissions to restrict KB pages based on the logged in user?

Should we create separate Service Desk Projects for each Customer given the small number of clients?  If so, is there a way to view queues from multiple projects like the Scrum Boards today in Jira?

[Victor Mutambuki · Accepted solution]

Damon,

You can only have only 1 knowledge base per project.

You can't restrict knowledge based on logged in user.

In your situation, you'd need to create separate service desk projects with accompanying knowledge bases.

More info

Victor

[Damon Gaylor]

Thank you Victor.  It also looks like can't create a Queue that pulls issues from multiple service projects.  (project in ("Customer A","Customer B")) is a valid jquery, but doesn't pull results in a Queue.  I have not been able to find if there is a config option to solve this)

Ideally, our Customer Support would only have to have one queue open to see requests from multiple service type projects.