Skip to main content
Solved

What kind of tags can we create for projects?

  • October 23, 2026
  • 1 reply
  • 8 views

We want to create tags for project to indicate if gigs are managed or unmanaged, given we’ll be using managed gigs for an AI change network. Do we have freedom to name the tags what we want? Additionally, are the tags just used as filters, or can we add controls behind them, so only people in certain user groups can see them? Any information about project tags would be appreciated!

Best answer by dkreiger

Hi ​@beth.steffens, Yes, you can choose your own project tag terminology. The documented feature supports classification and filtering, but I couldn’t verify tag-based visibility controls for specific user groups.

Naming and using project tags

Eightfold supports custom field-based project tagging:

  • An organization admin defines a custom dropdown label and a predefined set of values.
  • Project managers select one of those values when creating a project.
  • Employees can filter the Project Marketplace by those values.
  • The selected value can also appear in the project details.

For your use case, I’d recommend a field called “Gig management model” with “Managed” and “Unmanaged” as the options. That’s a suggested naming convention—not a required Eightfold naming scheme. This is an admin-defined dropdown rather than free-form tags that each project creator invents.
 

Can tags control who sees a gig?

Don’t treat the tag itself as an access restriction. The tagging documentation describes discovery, filtering, and display; it does not document attaching user-group permissions to a tag. An earlier product request also explicitly distinguishes filtering from enforcement: a filter can still allow someone to search outside their area and apply.

There is a separate Career Hub framework for restricting access to the Projects capability based on employee attributes, but that is different from showing only particular tagged gigs to particular groups.

For the AI change network, I’d therefore separate the requirements:

  1. Classification: use Managed/Unmanaged tagging.
  2. Restricted visibility: ask your Eightfold Support/Solution Expert team to validate whether selected gigs—or the tag field/options themselves—can be limited to your intended user groups in your environment.

Where it’s configured

The documented starting point is Admin Console → Talent Management → ProjectMarketplace – Manage Project Creation Templates. Enabling the dropdown in project creation, adding its marketplace filter, and displaying it in project details are separate configuration steps. The project-tagging setup guide walks through each.

View original

1 reply

dkreiger
Community Manager
  • Community Manager
  • Answer
  • October 26, 2026

Hi ​@beth.steffens, Yes, you can choose your own project tag terminology. The documented feature supports classification and filtering, but I couldn’t verify tag-based visibility controls for specific user groups.

Naming and using project tags

Eightfold supports custom field-based project tagging:

  • An organization admin defines a custom dropdown label and a predefined set of values.
  • Project managers select one of those values when creating a project.
  • Employees can filter the Project Marketplace by those values.
  • The selected value can also appear in the project details.

For your use case, I’d recommend a field called “Gig management model” with “Managed” and “Unmanaged” as the options. That’s a suggested naming convention—not a required Eightfold naming scheme. This is an admin-defined dropdown rather than free-form tags that each project creator invents.
 

Can tags control who sees a gig?

Don’t treat the tag itself as an access restriction. The tagging documentation describes discovery, filtering, and display; it does not document attaching user-group permissions to a tag. An earlier product request also explicitly distinguishes filtering from enforcement: a filter can still allow someone to search outside their area and apply.

There is a separate Career Hub framework for restricting access to the Projects capability based on employee attributes, but that is different from showing only particular tagged gigs to particular groups.

For the AI change network, I’d therefore separate the requirements:

  1. Classification: use Managed/Unmanaged tagging.
  2. Restricted visibility: ask your Eightfold Support/Solution Expert team to validate whether selected gigs—or the tag field/options themselves—can be limited to your intended user groups in your environment.

Where it’s configured

The documented starting point is Admin Console → Talent Management → ProjectMarketplace – Manage Project Creation Templates. Enabling the dropdown in project creation, adding its marketplace filter, and displaying it in project details are separate configuration steps. The project-tagging setup guide walks through each.