Rules are managed assets that share some behaviors with content. Like content, they can be push-published to other environments and their permissions inherit from their parent site or page. Unlike content, they are never visible to front-end users — when a rule is enabled, it runs silently in the background to shape the visitor experience.

When normal content is published to your server, it becomes available for viewing by different front-end users. The content contributors who edit and publish normal content are usually different from the front-end users that view the content.

However, when a rule is turned ON ("published") to your server, the rule becomes active, but the rule itself is still only visible to back-end users. The rule is transparent to front-end users, running and managing their user experience in the background without their knowledge.

Because of these differences, permissions on rules are handled slightly differently than permissions on other content:

• To View rules on any site, a user must have View (Read) rights for rules on the site.
  • A user without View rights for rules on a site will not be able to view a rule, condition or condition group, or action on the site.
• To Add, Edit, or Delete rules on a site, a user must have Publish rights for rules on the site.
  • A user without Publish rights for rules on a site will not be able to save or modify rules, conditions or condition groups, or actions on that site.