Using Team Attributes
Using Team Attributes
Team attributes let you store additional metadata on a team that can be used across the platform for workflow routing, display logic, approvals, and access control.
Common examples include:
Manager
– for approvals or escalationEscalation Contact
– for routing urgent requestsRegion
– to scope visibility or assignment logicSupport Level
– for tiered SLAs or dashboards
These attributes are available in workflows, forms, and even portals to dynamically drive behavior based on the team involved.
Setting Team Attributes
To add or edit team attributes:
- Navigate to Configuration > Teams
- Click on a team
- Scroll to the Attributes section
From here, you'll see a dropdown to select an existing attribute definition and assign a value.
Creating New Attribute Definitions
From the Attributes dropdown:
- Scroll to the bottom and select "Add New Attribute Definition"
- Enter the name, an optional description, and whether the attribute allows multiple values
- Once saved, it will immediately be available to assign
This makes it easy to expand your attribute strategy without interrupting your flow or switching context.
How Are Team Attributes Used?
Once assigned, team attributes can be referenced in:
Workflows
values('Escalation Contact')
Route tasks or notifications dynamically based on team-level data.
Forms
- Pre-filled fields based on the selected team
- Show or hide fields depending on a team's attribute value
Security Definitions
values('Region') === 'US-East'
Limit access based on a team's scope or location.
Best Practices
- Use clear and consistent attribute names (e.g.,
managerEmail
,supportLevel
) - Avoid redundant or overlapping attributes across teams and users
- Regularly audit attributes to ensure they're being used effectively in workflows and logic
Updated 24 days ago