Content
View differences
Updated by Parimal Satyal about 1 year ago
**As** a OpenProject sales manager
**I want to** be able to offer this feature in the Corporate plan
**so that** that it creates more desire of corporate clients to book this plan which in turn will finance all the other open source community work that we do.
**Acceptance criteria**
* When there is not Enterprise token, or the token does not allow this feature:
* We still show the permissions in the role administration and leave them editable.
* We don't show the toggle/checkbox to make a new internal comment a restricted comment.
* We show a banner at the project setting for enabling the feature.
**Technical notes**
* The feature needs to be explicitly enabled by the Enterprise token. So people will need to upgrade their token to have access to the feature.
**Permissions and Visibility considerations**
* _To whom is this feature visible?_
* _When is it not visible?_
**Out of scope**
* \-
**I want to** be able to offer this feature in the Corporate plan
**so that** that it creates more desire of corporate clients to book this plan which in turn will finance all the other open source community work that we do.
**Acceptance criteria**
* When there is not Enterprise token, or the token does not allow this feature:
* We still show the permissions in the role administration and leave them editable.
* We don't show the toggle/checkbox to make a new internal comment
* We show a banner at the project setting for enabling the feature.
**Technical notes**
* The feature needs to be explicitly enabled by the Enterprise token. So people will need to upgrade their token to have access to the feature.
**Permissions and Visibility considerations**
* _To whom is this feature visible?_
* _When is it not visible?_
**Out of scope**
* \-