How should I structure advanced distribution rules?

💻 Environment/Context

  • External groups
  • Distribution Rules
  • Access
  • Set-up 

 

In order for you to edit external group rules, the External Groups > Can view and External Groups > Can edit permissions must be enabled on your account.

If you're unable to follow any of the steps below, kindly reach out to your admin or refer to the Account Type Permissions Overview article for more information.

 

 

 

❓ Issue/Question

  • How do I set up my external group rules?
  • How does advanced rule structuring work?
  • How do I create my external group rules?

 

👌 Resolution/Answer

  • The recommended approach is to use:
    • A top-level AND group
    • An OR group that contains all allowed content packages
    • Global exclusions applied at the top level
       
  • This structure keeps access rules organized and avoids duplicating conditions across multiple branches.
  • Using a top-level AND allows global requirements and exclusions to be managed in a single location.
  • Using an OR group as an allow-list makes it easy to grant access to multiple content packages without creating separate rule trees. As access requirements grow, new content packages can be added without modifying existing rules.
     
  • Standard Set-up →  An asset is visible if it matches one of the allowed groups AND does not match any excluded condition.  
    • In the following example, the goal is to give access to Spain photos and Brazil videos, while excluding any content tagged Internal.
      • Give access to "Spain photos" and "Brazil videos", but never share anything tagged internal. 
        Top-level AND with an OR allow-list (two AND bundles) and one global exclusion at the top level. An asset is visible if it matches at least one allowed package (Spain + photo, OR Brazil + video) AND it is not tagged internal.

 

  • If I wanted to scale the structure and add more content access rules:
    • Add another AND bundle inside the OR group
      • Example: France + Highlights
    • To add global restrictions → Add another != condition at the top-level AND
      • Example: Tag != embargo

 

  • Using NOT for grouped exclusions → Use a NOT block when you need to exclude a specific combination of conditions rather than a single value.
    • For example, allow all Spain content while excluding Internal content and media tagged with both Photo and Best Moments. 
      • This can be expressed as: 
        Top-level AND
        Tag = Spain
        NOT (internal)
        OR (Photo AND Best Moments)
        • NOT is preferred when exclusions involve combinations, as it keeps logic clearer and easier to extend.

           
  • When possible, follow the same pattern for every rule set:
    • Use a top-level AND.
    • Place allowed content packages inside an OR group.
    • Apply exclusions at the top level.
    • Add new access packages by creating additional AND bundles inside the OR group.

 

  • Following this structure makes advanced distribution rules easier to understand, scale, and troubleshoot over time.

 

🔖 Notes