# Tagging Best Practices

{% hint style="info" %}
Tags can be added or removed at the organization level by admins or owners, at any time.
{% endhint %}

A well-defined, consistent, and logical tag schema will help your team manage their pipelines more efficiently. The following best-practices will help you get started:

#### 1. Use tags for themes, not statuses

Tags should be used to help describe the topic or theme of the feedback content. Avoid the use of tags to track status, priority, sentiment, customer, product, Engagement, etc. as these parameters are already included in the feedback metadata.

#### 2. Keep tags simple, and broadly useful

Tags are shared across your organizations in Confur. This means that your organization tags likely need to be broadly useful to several different products. To that end, avoid over-defining your tags. For example, your organization may have multiple products that support some level or reporting. In this case a simple tag like "reports" is better than relying on multiple similar tags (eg. "acme cloud reports" + "acme lite reports" + "acme premier reports"). Instead, rely on other metadata, such as product profiles in this case, to further define your organization's feedback items.

#### 3. Avoid tag bloat

Yes, it is possible to have too many tags! If you are creating tags for every feature of every product in your organization, no matter how specific, you are well on the way to tag bloat. Tag bloat leads to semantic overlap, and can naturally reduce the efficacy of Auto-Tag (too many options to describe the same thing). This can lead to inconsistent tagging across your organization. 

#### 4. Start simple and refine over time

As you are setting up your workspace, start with a simple list of tags, and refine as needed as your feedback collection ramps up. The following tags generally offer a good place to start:

* user interface
* user experience
* performance
* bug
* reliability
* feature request
* security