---
updatedAt: 2026-07-23T16:06:27.000Z
agentTools:
projectIndex: https://docs.sev.co/llms.txt
---
# Template Language for Action Center
# Template Language
Template language allows you to automatically add attribute values for each of your selected **assets** or **queries** without having to manually enter them. For example, if you are submitting tickets for six Device assets, you can incorporate the tag `{{device.hostname}}` in your description so that the `hostname` of each Device is included in its respective ticket.
Let's breakdown the structure of a template tag to gain a better understanding of it
## Brackets and Separators
There are two important syntax rules to keep in mind when constructing a template tag:
* All template tags must begin and end with two brackets (`{{}}`).
* Separators (`.`) must be used to differentiate between the different data components that make up a template tag.
## Namespaces
Namespaces tell the Aurora ASM platform the **data type** associated with your template tag. There are currently three namespace options:
* `device` – allows you to include **Device attributes** in your template tag
* `user` – allows you to include **User attributes** in your template tag
* `query` – allows you to include information about the query you've run in your template tag
## Attributes
Attributes are unified **asset attributes** in Aurora ASM with values that you would like your template tag to generate.
* Attributes always follow a **namespace** in the template tag format. For example: If `Device` is your namespace and `hostname` is your attribute, your template tag will be `{{device.hostname}}`.
* Please note that additional syntax is needed to display attribute values from specific sources. We will review this in the following section
***
# Applying a Template Tag
As you begin typing, the Aurora ASM platform will automatically populate syntax for each portion of your **template tag**.
After you enter your first set of brackets (`{{`) you will be prompted to choose between the `device` or `user` (depending on which Live Inventory page you are on) and `query` **namespace**.
Once you have selected a namespace, you will be provided with a list of possible **unified** and **source asset attributes** to finish populating your tag. Here are some tips for constructing a tag:
* Make sure to include a **separator** (`.`) after your namespace. Otherwise the list will not populate
* While the `query` attribute list is fairly short, you will want to type out the name of the **attribute** you would like to include in your tag to filter down the list.
* For **source asset attributes**, type the `source_assets.` followed by the **Source Name** that your attribute falls under (i.e. `{{device.source_assets.crowdstrike}}`).
* Tera built-in filters can be used to create more complex templates
* Complex **attributes** such as **tags** must be passed via the **pipe operator** (`|`) to `json_encode` in order to be rendered properly (e.g. `{{ device.tags | json_encode }}`. If you see `[[object]]` rendered in your template output, then the attribute cannot be rendered as is and must be passed to `json_encode`.
***
# Query Template Tags
Unlike template tags for **assets**, which provide information about the assets in your queries, template tags for **queries** report information about the query itself. Because Aurora ASM incidents create a separate ticket for each asset selected from a query, the value of a template tag for an asset will change depending on the asset corresponding to a ticket. Conversely, template tags values for queries will remain the same across all tickets created from an incident, as it is reporting on the query as a whole.
There are two query template tags that can be applied to an incident:
* `{{query.total}}` – populates the total number of **assets** in your query
* `{{query.web_link}}` – provides a link to the query you ran. Logged-in users with the link will be able to view the query from the **Live Inventory** page