Hi @ryancyq
Thanks for your reply and explanation, but I am not sure that I agree with your point of view.
Please have a look here Common Use Cases
For the described use case to make sense, you sould only assign the user to one level in the OU tree - at least in my application that makes sense, and I agree that it may differ depending on your use case.
And no - a ROLE is not what solves my usecase - please again refere to the link and use case above.
But however I sorted out what I need to do in the UI code to obtain the behaviour that I was asking for:
In the script _OrganizationTree.js I just needed to uncomment the line in the eventhandler section: selectNodeAndAllParents(...);
Thanks for all the input.
Reopend by mistake.
@ismcagdas
Thanks for your clearification - and hints it's very helpfull. And I am aware about most of what you try to explain.
But this was not the question - sorry to say. My question was aiming at the point where you create a user and assign him to the OU. If you here has a multilevel OU structure (as in my example posted) and you assign the user to the bottom level - ASP.NET Zero will per default "assign" him to all levels above also. And I do question the functionality at this point, as this seems for me to be wrong when we look at OU's! So my question was: Is there a way that the user may only be included in the OU I select - and nothing else?
By the way, if you enter the OU admin you may this way add a user to a specefic OU only.. so that is my current workaround - but that is not the best way of manageing this.
I am sorry that we have to take this "de tour" on this question - but please try to read my initial post once more and focus only on what I am asking for here - the assignments of a user to an OU nothing more nothing else - thanks in advance.
The role dos have Tenants but should not see the Editions or be able to change it on the tenant.
The exception occures when the page loads - so I don't even try to visit the Editions page!
In other words, I have a role that can see Tenants, but should not see the Editions.
That combination should at least not end up in an Exception!
Sure,
My objective is that a user that belongs to "Company B" can ONLY see entities that is marked with that OU id. A user that is in the "Norway" can see all entities from "Company A, B and C"
And as a animation:
HI @ismcagdas,
you misread my explanation, as my goal for that role is precisely that I don´t want to see the Editions at all!
And this creates an exception!
Hi,
ASP:NET ZERO version 6.4.0.0 - on Core and using MVC. Working on the HOST.
I am adding a new role where there is no permission to see the Editions entity. After that, a usere is created and included in this new role only.
When I try to log in as the new user I get this exception:
When I add "Editions" to the role permissions, it works perfect. But I don't want the "Editions" for this role, and don't think I should get an exception on that.
Be also aware that I made no changes to persmissions at all - they are as they come out of the "box". Just in case that should have anything to do with the cause to the problem.
How to solve this issue?
Thanks in advance.
Sorry,
6.4.01 (Latest) CORE, MVC
Hello,
I am trying to use OU (Organisational Units) to control the results from an entity lists. (Ex. "See only Tennants assigned to your OU" )
Here I realize, that when I want need to add a user to an OU (by clicking the checkbox), ALL OU checkboxes on the levels above to OU that I want to assig, is also beeing checked automatically... And if I uncheck those above, all OU's below i also unchecked.
I don't think the current default behaviour is the "best chooice" in this case for the OU's. I would for this usecase prefere, that only the one OU I do select is beeing checked.
Is there a way that I can get this configured to reach my goal?
Thanks in advance.
Hi @aaron
Thanks - that made the trick - now all seems to be working.
