Adding custom fields to organizations

Location: Admin Center >
People > Configuration > Organization fields

Similar to adding custom
fields to tickets, you can add numerous types of custom fields to organizations to store additional
details. Any custom org fields you create apply to all organizations. You can use custom
organization fields in triggers, automations, placeholders, search, SLAs, and reporting.
Administrators and agents in custom roles with
permission can create and edit custom fields for
organizations. Custom org fields are visible to agents, but not end users.
You can also add custom fields to users and custom fields to your tickets and support request
forms.
This article contains the following topics:
Creating custom organization fields
Cloning custom organization fields


Related articles:
Using custom fields
About custom field types
Managing custom organization fields
Recipe for the customer-centric company: Collect customer insights and
act on them




Creating custom organization fields

Administrators and agents in custom roles with permission can create
any custom field type for an organization, except credit card.
The following video gives you an overview of how to create custom
fields for organizations:

Creating custom fields for organizations [1:40]

To add a custom organization field
In Admin Center, click
People in the sidebar, then select Configuration > Organization
fields.
Click Add field.
Select a field type, then enter a Display name. When naming custom
fields, don't use reserved system or feature names such as "channel." These names are
reserved by Zendesk and won't work in custom fields.

Verify that the field key is the value you want it to be. This field is
populated by the field name, but you can edit it. You can't change the field key after
the custom field is created. The field key can be used to reference the custom field
in placeholders and the API.
Avoid field keys that overlap with system fields,
such as id, name, tags, details, and
notes.

(Optional) Enter a Description for the custom field. This is visible to admins
only.
Set any other options for your field, depending on the type.

Field option (checkbox fields only, optional): Enter a tag to apply to a ticket when the checkbox is selected.


Field validation (regex fields only): Enter a regular expression to create an input mask to validate entry.


Field values (drop-down and multi-select fields):
Enter Field options to include in the list. Click the X to remove a
value. You can bulk import field values if
you have a large number to add.

Click Sort ascending or use the drag-and-drop icon
( ) to manually reorder the field
values.
To create a nested drop-down list, separate categories and values with a
double colon (::). See Organizing drop-down
lists.



Related object and Set a filter (lookup relationship fields
only) Select the type of object to relate, and optionally define filters that
restrict possible values for the field. See Adding lookup relationship
fields.



Click Save or, to create another custom field, click the drop-down icon and
select Save and add another.
New fields are active
by default and are added to all organizations.

If needed, you can reorder your custom organization fields.




Cloning custom organization fields

Administrators and agents in custom roles with permission can create new custom fields
from scratch or clone existing organization fields and modify them as needed.

To clone a custom organization field
In Admin Center, click
People in the sidebar, then select Configuration > Organization
fields.
Hover over the row of the organization field you want to clone, then click the
option menu icon ( ) and select Clone. A detailed view of the
organization field's settings is displayed.

Edit the Display name and Field key so that they are unique. The
field key is populated by the field name, but you can edit it when creating the
custom field. You can't change the field key after the custom field is created. The
field key can be used to reference the custom field in placeholders and the
API.

Set any other options for your field, depending on the type.
Click Save. New org fields are active by default and are added to all
organizations.

If needed, you can reorder your custom organization fields.





{
"@context": "https://schema.org",
"@type": "TechArticle",
"@id": "https://support.zendesk.com/hc/en-us/articles/4408842677786",
"url": "https://support.zendesk.com/hc/en-us/articles/4408842677786-Adding-custom-fields-to-organizations",
"headline": "Adding custom fields to organizations",
"description": "You can create and manage custom fields for organizations to store additional details, which apply to all organizations and can be used in triggers, automations, placeholders, search, SLAs, and reporting.",
"articleSection": "End users and organizations",
"datePublished": "2021-10-16T03:59:17+00:00",
"dateModified": "2025-09-05T23:25:25+00:00",
"inLanguage": "en-US",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://support.zendesk.com/hc/en-us/articles/4408842677786"
},
"author": {
"@type": "Organization",
"name": "Zendesk",
"@id": "https://www.zendesk.com"
},
"publisher": {
"@type": "Organization",
"name": "Zendesk",
"@id": "https://www.zendesk.com"
},
"isPartOf": {
"@type": "WebSite",
"name": "Zendesk Help",
"@id": "https://support.zendesk.com/hc/"
},
"about": {
"@type": "SoftwareApplication",
"name": "Zendesk",
"@id": "https://www.zendesk.com"
}
}
//
const fast_path_style = document.createElement('style');
fast_path_style.innerHTML = `#article-body .fastpath{font-size:.9em;background-color:#f3f3f3;border:1px solid #d3d3d3;padding:10px 10px 8px;margin-bottom:16px}#article-body .fastpath::before{content:none!important}`;
document.head.appendChild(fast_path_style);
//