ArbiterQ: Article Level Security
Is there ever going to be a way to restrict articles by user? Creating a new workspace seems like a daunting way to separate users for different use cases. It's not the worst, but just a bit cumbersome. Also, is there a roadmap somewhere?
andreas_ivymayhem
Dec 3, 2025A: Hi there,
The idea is that a team can work together within a workspace, it was never really planned to restrict team members from accessing specific articles. We currently also have no mechanism in place to limit the frontend search to specific member rights.
Or is your question more directed to what members can edit in the backend?
We stopped maintaining a public roadmap for all our platforms.
Verified purchaser
My use case was a little more specific: Different articles being available to different clients. It seems that creating a new workspace is the only guaranteed way to restrict article access, which is fine but not preferred. I can deal with it and still think the product is excellent thus far.
Understood that the roadmap is locked away, but is there a place to request features at least?
Yes, you can request features here: https://feedback.eniston.io
Verified purchaser
Perfect thanks. I can see the feature statuses as well. This works.