Project Labels
Project Labels let you build a shared taxonomy that organizes every project on the platform. As an administrator, you define the taxonomy once by uploading a CSV file. From then on, whoever creates or edits a project chooses a value at each level of that taxonomy, so projects stay consistently categorized across organizations.
Find this setting at System Configuration > Others > Project Labels.
What Project Labels are used for
Project Labels give you a single, controlled vocabulary for classifying projects. Instead of letting each team invent its own naming, you publish a hierarchy that everyone selects from.
Once labels are configured, they appear in three places:
- Create and edit project: Users pick a value at each level of the hierarchy. If labels are configured, a selection at every level is required.
- Projects list: A Project Tags column shows the label path for each project, so you can scan how projects are categorized.
- Usage reporting: The selected labels are attached to workspace and active-user metrics, so you can group usage data by your business taxonomy.
The hierarchy can be up to five levels deep. Each level becomes a separate dropdown when a user creates or edits a project.
How the CSV file is structured
You define the taxonomy by uploading a CSV file. The platform reads the file as a tree: each row describes one full path from the top level down, and repeated values are merged automatically.
| Part of the file | Requirement | Purpose |
|---|---|---|
| First row (header) | Required | Each cell names a level of the hierarchy. These names become the dropdown labels users see when they create a project. |
| Remaining rows | At least one required | Each row lists one value per level, from left (top level) to right. |
| Columns | 1 to 5 used | Each column is one level of the hierarchy. The platform reads more than five columns but only the first five appear in the project form. |
| Empty cells | Optional | A row can stop at any column. Empty cells are skipped. |
Keep these rules in mind:
- Use a standard UTF-8, comma-separated CSV file.
- List every combination you want to allow. The platform removes duplicate values at the same level automatically, so you don’t need to worry about repeating a parent value across rows.
- Uploading a new file replaces the entire taxonomy. It doesn’t merge with a previous upload.
Column reference
| Column | Level | Example header | Data type |
|---|---|---|---|
| 1 | Top level | Business Unit | Text |
| 2 | Second level | Product Line | Text |
| 3 | Third level | Team | Text |
| 4 | Fourth level | Sub-team | Text |
| 5 | Fifth level | Component | Text |
Example CSV
Say you want to classify every project by business unit, then by product line, then by team. You’d create a file like this:
Business Unit,Product Line,Team
Finance,Payments,Checkout
Finance,Payments,Fraud
Finance,Billing,Invoicing
Healthcare,Patient Portal,Web
Healthcare,Patient Portal,Mobile
Healthcare,Claims,Processing
<!--NeedCopy-->
This file produces the following hierarchy:
-
Finance
- Payments > Checkout, Fraud
- Billing > Invoicing
-
Healthcare
- Patient Portal > Web, Mobile
- Claims > Processing
Notice that Finance and Payments each appear on several rows. The platform merges these repeated values automatically, so you don’t create duplicates — you simply list every full path you want to allow.
What the user sees
After you upload the file, the three header names become three dropdowns on the Create Project form: Business Unit, Product Line, and Team. The dropdowns cascade, so each choice narrows the next.
For example, a user creating a project might:
- Choose Business Unit > Finance. The Product Line dropdown now offers only Payments and Billing.
- Choose Product Line > Payments. The Team dropdown now offers only Checkout and Fraud.
- Choose Team > Fraud.
The project is now labeled Finance > Payments > Fraud. That path appears in the Project Tags column on the projects list and travels with the project’s usage data, so you can report on all Finance projects — or just the Fraud team’s — at any time.
Upload your Project Labels
- Go to System Configuration > Others > Project Labels.
- Select the file field and choose your CSV file.
- Select Upload.
The new taxonomy takes effect immediately and replaces any labels uploaded before. Existing projects keep their current labels until someone edits the project and chooses new values.