# Adding Advanced Activity Rules

## **Overview**

{% hint style="warning" %}
**Caution:** This setup reflects <code class="expression">space.vars.Kizen\_company\_name</code>'s default configuration. Your administrator may have customized your layout, so columns or navigation may appear differently. Trial accounts may have limited features.
{% endhint %}

This walkthrough shows you how to add Advanced <code class="expression">space.vars.activity</code> Rules using the Kizen UI. You’ll learn how to define rule conditions, apply logic, and specify which <code class="expression">space.vars.activity</code> fields are shown when those conditions are met, so <code class="expression">space.vars.activities</code> behave consistently during logging and submission.

Advanced <code class="expression">space.vars.activity</code> Rules are configured at the <code class="expression">space.vars.activity</code> Type level and take effect immediately once saved.

## **Before You Begin**

Before adding Advanced <code class="expression">space.vars.activity</code> Rules, make sure the following are in place:

* You have Admin access to Activities
* The <code class="expression">space.vars.activity</code> Type includes:
  * One or more field types to use as rule conditions
  * The <code class="expression">space.vars.activity</code> fields you want to show when conditions are met
* You understand that:
  * Each field can be controlled by only one rule
  * Rules explicitly define which fields are shown
  * Required fields are ignored if they are hidden by a rule

Having the <code class="expression">space.vars.activity</code> fields configured first ensures they appear as selectable options when defining rules in the Advanced Rules tab. See [Activity Fields](/docs/concepts/activities/activities-data-model.md#activity-fields) for more information.

***

{% stepper %}
{% step %}

### Navigate to Advanced Rules

1. Go to **Platform > Activities**
2. Choose an <code class="expression">space.vars.activity</code>
3. Click on the Advanced Rules Tab

<div data-with-frame="true"><figure><img src="/files/G60vMkevJ7OosuXDB7gc" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### Create a Rule

* Click **+Add Activity Rule**
* Select a field from the **When the following conditions are met** dropdown

{% hint style="info" %}
**Note:** You can add multiple condition fields by selecting the **+Add Condition** button. When multiple conditions are present, the rule specifies whether any or all of them must be met.
{% endhint %}

<div data-with-frame="true"><figure><img src="/files/N26g6JTvqdxsGgKvjIjq" alt="" width="563"><figcaption></figcaption></figure></div>

* Select an Operator (If required). ANY allows you to define the condition by OR. ALL allows you to define the condition by AND.
* Select a field from the **Show the following field(s)** dropdown.
  {% endstep %}

{% step %}

### Save and Test

* Save the <code class="expression">space.vars.activity</code> configuration, then log or schedule a test <code class="expression">space.vars.activity</code> to verify
* When you verify, check the following:
  * Field visibility changes correctly
  * Required fields behave as expected
  * Submission succeeds in all valid scenarios
    {% endstep %}
    {% endstepper %}

***

## Design Guidance and Best Practices

* Keep your rules simple and predictable
* Avoid chaining rules that are hard to reason about
* Use Dropdown fields for clear branching logic
* Test rules with different permission levels
* Avoid making read-only fields required

***

## What's Next

Next, continue to [Activities APIs & Webhooks](/docs/concepts/activities/activities-api-and-webhooks.md), which provides an overview of all API endpoints and webhook events available for <code class="expression">space.vars.activities</code>. This section helps you understand:

* Which <code class="expression">space.vars.activity</code> operations are available via API
* How Scheduled and Logged <code class="expression">space.vars.activities</code> are exposed programmatically
* Which <code class="expression">space.vars.activity</code> lifecycle events emit webhook notifications

Reviewing the APIs and Webhooks overview prepares you to work with individual endpoints and event types in the sections that follow.

<details>

<summary>Related Topics</summary>

* [Activities](/docs/concepts/activities.md)
* [Activities Core Concepts](/docs/concepts/activities/activities-core-concepts.md)
* [Activities Data Model](/docs/concepts/activities/activities-data-model.md)
* [Activity Permissions](/docs/concepts/activities/activity-permissions.md)
* [Advanced Activity Rules](/docs/concepts/activities/advanced-activity-rules.md)
* [Activities API & Webhooks](/docs/concepts/activities/activities-api-and-webhooks.md)

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developer.kizen.com/docs/concepts/activities/advanced-activity-rules/adding-advanced-activity-rules.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.