This article applies to the following Content Automation permission levels:
| ❌ Contributor | ❌ Author | ❌ Designer | ✅ Admin |
Key terms
Content Automation Tag: Content Automation Tags are labels you create to meaningfully group teams so that you can efficiently manage the content they have access to.
Team: A selection of users belonging to a certain department, location or sub-brand.
What are Content Automation Tags?
Content Automation Tags are labels you create to organize your teams in meaningful groups so that you can efficiently manage the content they have access to.
Tags are a flexible tool, so you can bring your own organizational structure into Content Automation. For example, you might use Content Automation Tags to represent regions, departments, services, or any other categorization you see fit.
How to add a Content Automation Tag to a team
- You can start grouping teams by creating/adding Content Automation Tags under Team Settings. There are no limits to the number of Content Automation Tags you can have on a team.
- To add a Content Automation Tag, begin searching for the name in the Add tags field. To create a new tag, simply type in the tag name and select Create option.
- After you’ve added Content Automation Tags to your team, you can filter the list of teams by tags. Click the Filter dropdown menu, and choose the name of the Content Automation tag you want to filter by. You can filter by teams with no tag by selecting the Untagged option at the bottom of the dropdown menu.
Content segmentation with Content Automation Tags
Content Automation Tags currently work with Project Kits and Template Variations, with more features on the way.
In the Project Kit or Template Variations permission settings, you can select a tag to add all teams with that tag to the resource.
Whenever you add or remove the tag from a team, the resource permissions will automatically update. This allows you to automate permission settings when onboarding new teams.
You can also use Content Automation Tags to quickly move content from a group of testing teams to a trial group, to a broader network release, simply by switching the Content Automation Tags.