Thanks for adding some food for thought Oscar.
There are more ways that lead to Rome [1] but with the given scenario I
still would model it as part of the domain, rely on database queries for
performance and maybe use app tenancy as a safeguard. Just a matter of
taste I guess.
[1]
Hi David and Jeroen,
Current Isis Security add-on has an interface, "WithApplicationTenancy”, that
can also be used to apply custom domain/business logic to resolve the
Application Tenancy to assign to a given entity.
By means of the tenancy path returned, you can determine the permissions
Hi David,
Currently in isis-module-security a user can have multiple roles (general
admin, financial admin, etc) and a single application tenancy (your
regatta) which is not a perfect match for your requirements. Personally I
would model an tuple entity like RegattaRole to specify the user,
Hello,
I have been playing with ISIS some more and have a question concerning
multiple tenancies for a single user.
The application I am working on is a rowing regatta management system.
I would like users to have scoped roles so that
user A can be:
- a general admin for regatta A
- a financial
Thanks Dan. It worked. Using a mixin is much better for my approach.
Thanks a lot.
On 2/23/2016 12:15 PM, Dan Haywood wrote:
Hi Vishma,
It you can't change the original class - because it was written for some
other purpose - then perhaps it might be better to wrap it in a view model
of your
