Access Lists on custom location paths

Hello,

While implementing Proxy Manager and migrating from Apache Reversed Proxy (which are all configuration files built and referred to in sites files) I came across the following configuration I use and miss in Nginx Proxy Manager;

Most of the websites are public, while others have the need to use basic HTTP Auth or an access list. This is already possible on a domain and works like a charm.
Now there are some websites which are public, but some subdirectories or subfiles on a website should be protected by auth or acl. Simple example: Wordpress websites should be public, but the wp-admin and/or wp-login.php sub url should be restricted by IP. In Apache I named a separate location and defined the allowed IP ACL.
In proxy manager this is not yet possible, since I can't define a proxy host (e.g. example.com/wp-admin), I can only define domain names (e.g. domain.com (without something after the /)). I can define custom locations for various paths but it is not possible to define a ACL for the specific path.
I am not a programmer, but I would very much like to have the option to be able to select a ACL list on a custom location (subdirectory).

Does anyone have any input?
Thanks

Regards,
Thomas

No files or tests are named. Start by tracing the custom-location and ACL configuration flows in the project, then determine how a custom path can select an access list. Done means a user can assign an ACL to a custom location and the generated Nginx configuration enforces it for that path.