Right now, only a single API Token is allowed in "DNS Integration for Cloudflare®" extension.

However, consider this scenario:
1) A customer uses their Cloudflare account under which they manage at least one domain.
2) You're hosting their website under this/these domain(s) in Plesk.
3) You want to configure their domain to auto sync/export using the "DNS Integration for Cloudflare®" extension.

Cloudflare won't allow you under any API token issued by your account to manage other users' Zones (in this case the customer's) - even if they have invited you as an Administrator member through Cloudflare.

My suggestion is to be able to override the API token that is going to be used for a domain - either on a domain level or a subscription one (or both).

Hope you find it useful! Certainly I would.

PS:
Setting the token on a customer-level does not seem as a good idea since if a customer has multiple subscriptions, they might be allocated to each and every one of their customers (e.g. if they're an agency).

This should be mandatory function and it is very bad, that you can not add different Cloudflare APIs. We use Plesk Servers with several customers on it and are not able to use this extension cause of this. Very sad.
To the developers: Is it that much of an effort to implement this?

This feature is critical for us. Moving cloudflare management to user level is very important, would minimize the support load.

I'd love to see this feature.
I'm a Cloudflare partner and I'd like to be able to connect/have my customer connect their Cloudflare account with their subscription.

+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.