> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rootly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Team Variables

> Reference guide for team variables available in Liquid templates including team metrics, member data, on-call assignments, and integration mappings in Rootly.

Team variables expose team-level data — names and slugs, incident and action item counts, configuration flags, user lists, and objects like services, schedules, and functionalities — for use in Liquid templates. You can use them anywhere Rootly supports [Liquid templating](/liquid/liquid), such as workflow task option blocks, to make your automations aware of team context.

Like [incident variables](/liquid/incident-variables), team variables are plain Liquid expressions, so you can chain [filters](/liquid/filters) onto them to transform values, look items up in arrays, or format output. The `team.users` array is particularly useful for reverse lookups — for example, resolving a user's Slack ID from their email address (see the example below).

## Variables

<Note>
  Use the [Liquid Markup explorer](https://rootly.com/account/help/liquid-explorer "Liquid Markup explorer") to navigate through all team variables.
</Note>

Rootly uses the [Liquid](https://shopify.github.io/liquid/ "Liquid") template language. The available variables are:

```ruby Ruby theme={null}
# Basic team info
{{ team.id }} # returns string
{{ team.name }} # returns string
{{ team.slug }} # returns string
{{ team.time_zone }} # returns string
{{ team.generated_incident_title }} # returns string

# Incident counts
{{ team.incidents_count }} # returns integer
{{ team.incidents_test_count }} # returns integer
{{ team.incidents_normal_count }} # returns integer
{{ team.incidents_scheduled_count }} # returns integer
{{ team.incidents_backfilled_count }} # returns integer

# Action item counts
{{ team.action_items_count }} # returns integer
{{ team.action_items_follow_up_count }} # returns integer
{{ team.action_items_task_count }} # returns integer
{{ team.action_items_open_count }} # returns integer
{{ team.action_items_in_progress_count }} # returns integer
{{ team.action_items_cancelled_count }} # returns integer
{{ team.action_items_completed_count }} # returns integer

# Configuration flags
{{ team.config_ai_enabled }} # returns boolean
{{ team.config_ai_summarization_enabled }} # returns boolean
{{ team.config_ai_similarities_enabled }} # returns boolean
{{ team.config_sub_status_enabled }} # returns boolean

# User arrays
{{ team.users }} # returns array
{{ team.jira_users }} # returns array
{{ team.pagerduty_users }} # returns array

# Objects (keyed by slug)
{{ team.form_fields }} # returns object
{{ team.post_mortem_templates }} # returns object (keyed by slug)
{{ team.schedules }} # returns object (keyed by slug)
{{ team.services }} # returns object (keyed by slug)
{{ team.functionalities }} # returns object (keyed by slug)
{{ team.groups }} # returns object (keyed by slug)
```

## Examples

### User reverse lookup by email

```ruby Ruby theme={null}
{{ team.users | find: 'email', 'john@doe.com' | get: 'name' }}
{{ team.users | find: 'email', 'john@doe.com' | get: 'slack_id' }}
```

## Related resources

* [Task Output Variables](/liquid/task-output-variables)
* [Incident Variables](/liquid/incident-variables)
* [Action Item Variables](/liquid/action-item-variables)
* [Alert Variables](/liquid/alert-variables)