# Field Member Automation

### Overview

Field Structure member automations offer a rule-based solution for efficiently managing Field Structure admins across hierarchical levels.

<figure><img src="https://1733114811-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lclpq021Ai9jH1_X4gO%2Fuploads%2FIkCWSg54VFjoovzeSqPl%2F09-12-2024-10-12-49.png?alt=media&#x26;token=6bdc58cd-c768-4314-b4a2-b7730e769c94" alt="" width="563"><figcaption></figcaption></figure>

***

### Rule Tab

To configure automation for managing Field Structure admins, click on **Automation** from the 3-dot action menu to open a pop-up menu.

<figure><img src="https://1733114811-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lclpq021Ai9jH1_X4gO%2Fuploads%2FrKQRHoIZ092TMF59W2z1%2F09-12-2024-10-18-31.png?alt=media&#x26;token=40cf06a1-e740-49f7-b9b4-4009e64bbe31" alt="" width="563"><figcaption></figcaption></figure>

The **Rule** tab allows admins to enable or disable the automation feature, configure trigger frequencies,  and set user conditions. Once enabled, the automation can be set to trigger at intervals of 24 hours, 8 hours (default), or 4 hours.&#x20;

Admins can specify up to 10 conditions using logical operators. Conditions within the same field use **OR** logic, while those across different fields use **AND** logic.&#x20;

The action for automation is static, ensuring users matching the criteria are added to the Field Structure, while those no longer meeting the criteria are removed.&#x20;

{% hint style="warning" %}
Manual additions **remain unaffected** by the automation.
{% endhint %}

Users added through automation will be clearly labeled as **Added via automation** beneath their username.&#x20;

<figure><img src="https://1733114811-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lclpq021Ai9jH1_X4gO%2Fuploads%2FfEIwTKe9s5X2Pi5j0A2k%2F09-12-2024-10-48-58.png?alt=media&#x26;token=1354c6b3-0fb3-4aee-83a5-b5a470ddbeaa" alt="" width="563"><figcaption></figcaption></figure>

These users can be removed manually or via automation if they no longer satisfy the defined criteria, while manual additions remain unaffected.&#x20;

{% hint style="success" %}
For optimal performance, we recommend limiting to a maximum of 100 active automations at a time, with up to 10 rules each. This will ensure synchronization takes no longer than 10 minutes to complete.
{% endhint %}

***

### Run Logs

The **Run Logs** tab contains comprehensive logs, detailing every automated or manual synchronization event. The logs display the date and time of the trigger, the number of users added, and the number removed, all sortable by column.&#x20;

<figure><img src="https://1733114811-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lclpq021Ai9jH1_X4gO%2Fuploads%2FzLCboYJ3e34jnEmND6U6%2F09-12-2024-10-29-11.png?alt=media&#x26;token=6c0fbc39-3297-4078-a6a1-5db227b148d5" alt="" width="563"><figcaption></figcaption></figure>

Manual sync entries also show the username of the initiator for better transparency.&#x20;

***

### **Scope**

Each Field Structure level can have its own automation rule, and these rules apply **exclusively** at the individual Field Structure level.&#x20;

Automations **do not** impact parent-child Field Structure hierarchies; i.e. users added to a parent Field Structure are not automatically added to child Field Structures.&#x20;

**Guest users** are **excluded** from automation altogether.&#x20;

Additionally, admins can initiate a manual synchronization by clicking the **Save & Run Now** button, which triggers immediate updates without altering scheduled automation runs. This ensures that both manual and automated processes coexist seamlessly.