SQL & PL/SQL

If you change anything that is shared, you push it to the subscribers in your development APEX Builder. In your case: when you change the authorization scheme in the master app, push it to the subscribing apps in dev, export all apps (or app components) and import these in the other environments (test and production).
So there is no need to go into APEX Builder in test and production to push these subscriptions. These environments shouldn't have builder access anyway.

Inol,
Thank you for replying.
This approach is what I initially described to them (the client). They responded with not wanting to have to deploy all the applications (10 in total) when a change was made to an Authorization Scheme. So I was wondering if there was another approach that could be added to their automated deployment process, like a command line or similar, that could be used?
Thanks,
Joe

Inol,
Thank you for confirming there's no other process than to go into the Scheme and Publish the updates.
I'll let them know. Honestly, I also asked how often they would make changes and they said not very often. So they had a concern that "remembering" that the updated Scheme would need to be published. I suggested we can put a comment in the Comments section on all the Schemes created to "remind" them what the process is. Now if they don't see or read it...well.
Thanks,
Joe