+1

Pretty crazy that this isn't how the extension is already set up. This would also make it much easier for clients who use Cloudflare as their registrar directly.

Why this isn't the way its already handled is beyond me. If this were enabled it would really make life easier for clients that use Cloudflare as their registrar directly rather then them having to manually make every record.

pls.

Cloudflare allows you to create a custom token to allow DNS editing only for a specific domain.

So, each domain would have its own token and would only be able to edit itself and would not be able to edit the DNS of other domains.

This way it could be used for web hosting business, without the customer having to log into Cloudflare, as in fact only the administrator has to manage the Cloudflare account.

The customer will only be able to manage his DNS from the Plesk panel.

some clients manage their cloudflare accounts independently, thus there should be a way to sync several cloudflare accounts from different clients with the cloudflare DNS extension

This would be great for hosting providers and end users of Plesk. It would need to allow the Plesk subscriber to link their own Cloudflare account or create a new one and then use that to host their sites and sync records. It ideally should also have a way to enable and disable the proxy and clear cache in Plesk.

many customer want to use their domain and connect with cloudfare, if only visible to admin only, customer don't have that benefit,

Cloudflare offers an array of features, many of which are accessible to users with free accounts. Currently, the Plesk "DNS Integration for Cloudflare" extension allows server administrators to view only the domains associated with the admin account. To display all customer domains within the extension, administrators must modify the panel.ini file. However, there's a catch: If a server administrator adds a customer's domain via this method, it's registered under the administrator's Cloudflare account, not the customer's. This setup prevents the customer from accessing and modifying domain settings directly in Cloudflare. Consequently, any adjustments to the plethora of Cloudflare options would necessitate intervention from the server administrator. This configuration limits the utility of the extension for web hosting businesses aiming to offer direct Cloudflare access to their customers.