All articles

Troubleshoot Custom Field Visibility

Overview

Custom fields in Wrike help teams store and manage information specific to your work across tasks, projects, and folders. The ability to view custom fields depends on the sharing settings controlled on two levels:

  • Item level (tasks, folders, projects)

  • Custom field level

If a custom field is not visible to you, adjusting the sharing settings and access to the parent location of the field can help.

Important

Before troubleshooting, try accessing your Wrike account in a different browser or in a new incognito window. If everything works as expected in these environments, it may indicate that clearing your cache and cookies could resolve the issue. You can find instructions on clearing cache and cookies here.

Situation

A custom field exists in your account and is visible to colleagues, but you can't see it. Follow the instructions below to determine the cause and gain visibility.

Restricted by parent item inheritance

Custom fields added to a parent item (folder, project, or space) will be inherited on the subitem levels as well. If the parent level is not shared with you, the custom field will also be hidden from you on the subitem level. To get the required custom field to show on the item you can:

Restricted by custom field sharing settings

The custom field may be hidden due to its sharing settings. To gain access to the custom field, ask your account admin or space admin (for space-level fields) to share this field with you. They can grant you "See" access, or "Edit” access if you need to update the values. Account admins, can review and adjust the field's sharing settings from the account-level custom field panel. 

Contact Support

If the steps described in this article didn't help solve the issue, please contact our Support team for assistance.

When sending a support request, please include the following information:

  • Troubleshooting steps you took.
  • Screenshot or video recording illustrating the issue. 
  • Permalink to the affected folder/project/space.
  • Emails of user(s) experiencing the trouble, as well as the email addresses of account members who are not affected.
Top

Related articles