* Begin of the insertionShow the [banner video](https://community.openproject.org/work_packages/67185) if the enterprise token is not activated.

* Show the enterprise icon in the project attribute creation action menu if the enterprise token is not activated.

* End of the insertion The token should be Begin of the insertionvalidatedEnd of the insertion Begin of the deletion consideredEnd of the deletion when

* Begin of the insertionCreatingEnd of the insertion Begin of the deletion creatingEnd of the deletion calculated values

* Begin of the insertionEditingEnd of the insertion Begin of the deletion readingEnd of the deletion calculated values Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * Begin of the insertionWith an expired token, you can still

* Display calculated values inEnd of the insertion Begin of the deletion withinEnd of the deletion the Begin of the insertionAPI,End of the insertion Begin of the deletion API


As opposed toEnd of the deletion the Begin of the insertionproject overview andEnd of the insertion Begin of the deletion feature flag, were we limitEnd of the deletion the Begin of the insertionproject list.

* DeleteEnd of the insertion Begin of the deletion validity check to the _creation_ step, not having an enterprise token should instead also limit _using_ calculated values. This will create some edge cases whereEnd of the deletion a Begin of the deletion user has already createdEnd of the deletion calculated Begin of the insertionvalue.

* Also,End of the insertion Begin of the deletion values withEnd of the deletion a Begin of the deletion valid enterprise token - but the token later expires. UsingEnd of the deletion calculated Begin of the insertionvalue will stillEnd of the insertion Begin of the deletion values (reading, editing, etc.) shouldEnd of the deletion be Begin of the insertionupdated/recalculated when a referenced custom field is updated.End of the insertion Begin of the deletion restricted.End of the deletion