I think that if a service is @Hidden, then it won't appear as an icon.
So one option might be to code something in the new hidden() method just
implemented might also work the same way (eg using
container.getUser().hasRole("...") ).
Another possibility is that the Authorization service could veto. The
details will vary by impl, but I think the FileAuthorization service will
consult the "allow" file and veto visibility if no matching role is present?
Dan
On 8 December 2011 13:27, Kevin Meyer - KMZ <[email protected]> wrote:
> On 8 Dec 2011 at 13:16, Dan Haywood wrote:
>
> > Do you mean that the services/repositories (icons in the UI) available
> are
> > per role, or something else?
>
> Exactly this.
>
> Only those who have "Treasurer" role should see "Invoicing" service,
> for example.
>
>
>
