Absolutely crucial, I've been checking 3 times a day for the past 6 months because at any moment my FastAPI server meets his end and my customers have no way to login to their work tool.

Apache doesn't work for this so it has to be nginx. Because I'm a sudo user, I've been overwriting the automatically generated nginx config file for that domain. Coordinating with the server admin on this has been a near impossible task. Half 1 this Sunday night I was resurrecting the server again... meanwhile I'll keep looking for a way to get plesk to accept my settings without deleting it randomly.

We have use cases where a server owner wants to grant a developer "unrestricted" access to do anything (e.g. including modification of nginx directives) for a single domain, but they do not want to give them access to modify things for other domains (so "additional admin" user is not appropriate).

A way to grant greater power to a standard user, or a way to restrict an "additional administrator" to only work with specified domains/subscriptions would be useful (the latter would also overcome the problem where access to a server-level extension is required for the developer's work).

This option should at least be available in standard for resellers, and optionally for customers.

Current requirement to involve Admin is very clunky. This seems a fundamental need

I would appreciate that option!

I'm baffled why a simple thing like this has not been implemented. For EVERY domain I create as a reseller, I've got to contact the hosting provider to sort nginx directives. Please relieve customers and server admins. At least make this available for reseller accounts.

I can't see any reason why Nginx should not have the same rights as Apache regarding application of rewrite rules. The risk is there for Apache with the .htaccess - why should nginx not the same rights and the feature to define rewrite rules at least?
I understand, the ability to add directives might not be enabled per default to mitigate miss configurations and support efforts. However, it should be easy to make this an optional feature which could be enabled for dedicated customers on demand, might be with at disclamer 'at your own risk' etc.

It's not important, it's fundamental, crucial...

I cant belive I migrate to Plesk 18 and Nginx fields are hidden now under Apache setiings! This is for me very bad new version policy. + hotlinking bug... seems it is not tested enough

Currently, the customer is unable to manage "Additional nginx directives" as described here https://support.plesk.com/hc/en-us/articles/115000065889
However, at the same time, he can disable Apache by disabling "Proxy mode".
So, it would be nice if the customer will have the ability to manage nginx settings for his domain on his own without contacting Plesk admin
Also, I can see the existing request which was declined https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/34285378--additional-apache-nginx-directives-avaliable-f

wtf you need more informations for? Read title and Description.
Thats exactly what i think is totally needed.....

Currently only admin can manage these directives, that leads to additional work for me as an administrator. I want to be able customer to manage additional Apache/Nginx directives by themselves, for example configure rewrite rules.

"Additional Apache directives" should be made available as an option for customers. For example I want my customers to be able to use custom directives.