Hi,
I think you can use the
OrganizationUnit
without a problem.
OrganizationUnit
is a tree structure.You can use the first-level node as the company and the sub-level nodes as branches.
I appreciate you taking the time to consider my question.
However, your answer essentially restates my question!
While you suggest that OrganizationUnit
could work, I was hoping for a more definitive answer regarding whether they fully satisfy the requirements I outlined.
My question wasn't simply whether OrganizationUnit
could be used as a hierarchical structure; it was whether it provides the necessary functionality for granular access control at the Company/Branch level or not.
To clarify, my goal is to assign a role to a user within the context of a specific Company and Branch. NOTE that I am not looking to assign roles directly to Companies or Branches themselves(like what is done in ABP where the role or user itself is linked to an OrganizationUnit
). The ability to control access to entities like AccountingDocument
based on the user's role within a specific Branch is crucial.
Could you please confirm whether the OrganizationUnit
feature provides this level of fine-grained access control, or if a custom solution would be necessary?