Loading

Topics

Asana provides multiple layers of control to help you manage who can see, edit, and govern custom fields across your organization. This guide offers a high-level overview of our permission types, with links to deeper documentation.

  1. Custom field access levels – Control who can use and manage a custom field's configuration, including renaming, editing options, and managing access, by assigning Admin, Editor, or User roles.
  2. Field value edit restrictions – Limit who can edit values within a specific project.
  3. Private fields – Restrict visibility of a field and its values to selected people.
  4. Team sharing for custom fields  – Easily grant access to entire teams.

Custom field access levels

Access levels define who can manage the configuration of a custom field, allowing for access settings to be tailored to individual users.

  • Field admin – Full control: delete, rename, edit options, manage access.
  • Editor – Can edit dropdown options, colors, and formulas.
  • User – Can use the field in projects but not change its configuration.

This helps distribute responsibility: only give full power to those who need it.

Learn more about access levels.

Edit restriction on custom field values 

Available on Asana Enterprise and Enterprise+ tiers, as well as legacy tier Legacy Enterprise.

Edit restriction for custom field values is a project-level setting that gives project admins control over who can update values for custom fields — including Assignee and Due Date — within their project.

Admins can choose to restrict editing access to:

  • Only project admins, or
  • Project admins and project editors

This allows teams to protect sensitive or high-signal fields from accidental or unauthorized changes. 

Learn more about editing restrictions.

Private custom fields

Available on Asana Enterprise and Enterprise+ tiers, as well as legacy tier Legacy Enterprise.

Private custom fields are a field-level control that allows field owners to manage who can see and use a custom field. When a custom field is marked as private:

  • Only people who’ve been explicitly added to the field can see or use it.
  • Everyone else won’t see the field at all — even if they have access to the task or project where it’s used.

Learn more about private custom fields.

Team sharing for custom fields

Team sharing for custom fields allows you to easily grant access to a custom field to all members of a specific team. This is especially useful when your team needs to use and report on the same field across multiple projects. When a field is shared with a team, all current and future members of that team will automatically receive access to the field, based on the role you assign.

Learn more about team sharing.

Loading
Article Detail