You can define custom fields with Gtmhub that go with teams and users. By default, Gtmhub will store info from the built-in fields. However, you can easily add more fields to suit your needs.

Check out this general guide for Custom Fields.

Ideas for team and user custom fields

Team custom field

Let’s say you want to specify where each team is located. You can create a custom field for teams with this information:

Name: office
Programmatic name of the field. This field has several requirements: must be unique, must be lowercase, can be letters only, has to be between 4 and 12 characters

UI Label: Office
This is the name of the field that will be displayed in the user interface. There're no requirements here

Description: Location
A hint to users on how to use this field

UI Selector: Drop-down menu
Type of the field depends on the type of information you want to store in this field

Target type: Team

Required: Unchecked
If this is checked, every user must fill in the value of this field when creating an team. To make the field optional, leave this unchecked

When a team is created or edited, you can specify where the team is based.

Pro-tip: Now that you have an Office custom field, you can use it in your Insightboards as a filter to gain more granular understanding of your organization’s OKRs progress.

User custom field

Let’s say you want everyone to know who your OKRs champions are in your organization. You can create a custom field for employees with this information:

Name: okr_champion
Programmatic name of the field. This field has several requirements: must be unique, must be lowercase, can be letters only, has to be between 4 and 12 characters

UI Label: OKR Champion
This is the name of the field that will be displayed in the user interface. There're no requirements here

Description: OKR Champion
A hint to users on how to use this field

UI Selector: Checkbox
Type of the field depends on the type of information you want to store in this field

Target type: User

Required: Unchecked
If this is checked, every user must fill in the value of this field when creating an team. To make the field optional, leave this unchecked

When a user is created or edited, you can mark whether or not the individual is an OKR champion.

You can create a simple Insight that lists all the OKR champions in your organization which people can reference if they need help.

And you can point everyone to this information easily by linking to this Insight in an Announcement.

Did this answer your question?