Zum Hauptinhalt gehen

AD Group Security

Kommentare

6 Kommentare

  • Ryan Kelley
    Try something like the image below. I have to deal with this all the time.

     

    User-added image
    0
  • Ryan Kelley
    Actually, this really pertains to workflows... maybe it'll get you on the right track though?? However, I feel like with permissions on layers specifically, I have had to make separate viewers to avoid the conflict you are referring to.
    0
  • Ryan Cooney
    Here's how we apply permissions:
    • Deny permissions trump allow permissions at the same level.
    • Allow permissions trump deny permissions that are inherited.
    Your use case is possible when you are able to deny access to an ancestor object for group B and then allow access to a descendant object for group A.

     

    --Ryan
    0
  • Permanently deleted user
    So the following should work?

     

    Image 1 is for Group B which is denying general users access to the well sticks layer

     

     Group B. General User Access

     

    Image 2 is for Group A, granting select users (who are all also users of group B) access to the well sticks

     

     

    Group A.  Select User Access

     

    Both groups are also granted Site access, it's not implied. 
    0
  • Permanently deleted user
    Scott, if you're still having issues then I can give you an answer to help get almost any kind of permission combinations but if you have what you want then I'll leave it be as it's a handfull to type out.
    0
  • Permanently deleted user
    We got it working Matthew.  It was just taking much longer thane expected for changes made in the AD groups to trickle through the system.  Thanks though.
    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.