Given you want to verify each applied license for a particular project, you may want to use the "enforce whitelisting" feature. Enabling this option, the system will require each new license to be added on the whitelist. Every license that is not on the whitelist will be marked as violation. See here for a detailed description on how to switch on and off.
To change violation status, the license needs to be put on the whitelist. Using the context function in the license view, the license may be put on the corresponding list. (see how to white- and blacklist) All users with access to the project may execute this task.
But this does not immediately lift the violation status. When you look at the whitelist, you will see the license added to the list but marked with the status "approval pending". The push to the whitelist does initiate a task for the corresponding compliance manager to verify the suitability. As soon as he approves the license, the status label will change to whitelisted (ok).
PLEASE NOTE: Approvals may be performed on all three levels: corporate, project or module. Be cautious with approvals on higher levels. Especially circumstances like distribution, modification or architectural position are defined on module level only.
It might make sense to reject an approval on project level but approve the same request on a module level.