---
title: "Behaviors"
description: "Discover how to use content policies, rules, conditions, and actions for efficient content management and custom behavior integration. (Gitana 4.0)"
product: "Gitana"
version: "4.0"
url: "/documentation/gitana/4.0/engine/behaviors/overview"
---

# Behaviors

Content editors work with simple forms to create content that conforms to your defined content models. When that content is created, updated or deleted, it automatically triggers policies (or events) which you use to bind in custom behaviors.

The pieces fit together like this:

- [Policies](/documentation/gitana/4.0/engine/behaviors/policies.md) are the events, such as creating a content item or associating it into the content graph, that you hook your custom logic into. Policy handlers include scripts and rules.
- [Rules](/documentation/gitana/4.0/engine/behaviors/rules.md) are content nodes that describe the [Conditions](/documentation/gitana/4.0/engine/behaviors/conditions.md) to evaluate and the [Actions](/documentation/gitana/4.0/engine/behaviors/actions.md) to trigger. Once they're set up, rules run automatically as content is created, updated and deleted within your branch.
- [Conditions](/documentation/gitana/4.0/engine/behaviors/conditions.md) let a rule evaluate its content and its environment before deciding whether to execute its actions.
- [Actions](/documentation/gitana/4.0/engine/behaviors/actions.md) are units of work that perform content operations on your behalf.

**Start here:** [Rules](/documentation/gitana/4.0/engine/behaviors/rules.md).

The following types of behaviours are available:

- [Actions](/documentation/gitana/4.0/engine/behaviors/actions.md)
- [Conditions](/documentation/gitana/4.0/engine/behaviors/conditions.md)
- [Policies](/documentation/gitana/4.0/engine/behaviors/policies.md)
- [Rules](/documentation/gitana/4.0/engine/behaviors/rules.md)