On Jun 26, 2014 3:56 PM, "Wenli Ji" <[email protected]> wrote: > > Hello, > > It's will be very helpful if anyone could give me some hints... > > We have a special requirement that we want our customers to access out bloodhound website to create tickets/wikis, but they should be invisible from each other. > > For example, users belong to customer A cannot never view/modify tickets/wikis of customer B. > > Is there a way to configure bloodhound to satisfy the requirement, or we have to develop it ourselves? > > Thanks > Wenli
The permission policy attached to #777 should accomplish the aim for tickets, or at least serve as a starting point: https://issues.apache.org/bloodhound/ticket/777 For the wiki, you'll either want to implement a permission policy, or you can use TracFineGrainedPermissions if the resource name or naming pattern is known. http://trac.edgewall.org/wiki/TracFineGrainedPermissions
