The document approval workflow is currently configured at the level of each document. This is extremely powerful but can cause some
Experience would tell, however, that approval of documents is typically assigned to a very limited number of people:
This suggests that the approval of documents - even though it ultimately centers around an individual - is more about the function, the team, and the process.
For this reason it would make sense to create a new master data entity called "Approval Workflow". This would effectively be a model. (And furthermore, all models like "Ratings", "Tests", "Risk Assessment Models", "Decision Trees", etc. could all be hosted in a Master Data module called "Models". Why call it models - you can define a model as something that takes inputs from the user and transforms it into other information or performs some function)
The benefits of this would be immense as the users would only have to control the approval workflow in one place and it would be applied across all documents. This would make the reassignment of approvals very quick in case people leave, or change jobs, etc.