Issue Summary

When we publish a classification level, an Org Admin can set a global default level or a project default level or even update the level via the More Actions on a work item.

However, we cannot limit the editing of this field by non-Admins. And, as it is meant to be used to mark things as Confidential, etc, we should be able to restrict users (non-admins) from being able to change that.

Steps to Reproduce

1. Create a Data Classification > Set a classification to a Jira Work Item or Confluence page.
2. Have the owner of the above classified Item change the classification level while not being an admin of the space/Project.

Expected Results

When desirable, we should be able to restrict the Data Classification level field changes to specific groups/users. 

Limiting the Classification Level field to certain groups via a project permission scheme option or even a global toggle under the Data Classification management panel (In Admin hub).

Actual Results

The end user can still change the level of the classification.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available