In workflows, most of the time a status like "approved" is available. However, at the moment everybody can set this status, so it pretty useless.
If only certain users (e.g. with a certain role) could set the status to approved it suddenly gets value and it can be used to manage procedures etc. on it.
When you say "leveraging an internal process to confirm that only certain people within your organization is allowed to change a status to "approved."", can you explain how that would work?
As you know, we offer the ability to fully customize workflows so that the terminology can match your internal processes. We also have a variety of user types with different levels of permissions (product owner, contributor, reviewer and viewer), including the ability to make changes within the account.
At this time, we do not have additional plans to add or extend the roles and permissions of the user types. We would suggest either using the current available user types or leveraging an internal process to confirm that only certain people within your organization is allowed to change a status to "approved."