# Roster Automations {% embed url="" %} ## Roster Trigger Actions Communities can use the [**Actions**](/cms/tutorials/administrative/actions.md) panel to send webhooks, in-game messages, and other automated tasks. These actions can run on a schedule or be triggered when roster cells change. **Example:**\ A community roster includes a **Status** column that automatically switches members between **Active** and **Inactive** based on their recent in-game activity. When a member’s playtime drops below the required threshold and their status updates to *Inactive*, a Discord webhook should be sent automatically. ***Note:** Activity time columns update automatically when new logs (join/leave game) are created. If a member hasn’t logged in recently, no logs exist to trigger a recalculation, so a 12-hour scheduled task re-processes them.*

## Edit Roster on Form Stage [Custom form stages](/cms/tutorials/forms/creating-custom-forms.md#form-stages) can also update rosters. For example, when a leave-of-absence (LOA) submission moves to the **Accepted** stage, the submitter’s **Status** field can automatically be set to **LOA**.

--- # 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://docs.sonoransoftware.com/cms/tutorials/rosters/roster-automations.md?ask= ``` 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.