Forwarded to devs Backup Permissions in Service Plan are not working as expected

[Xio]

TITLE:

Backup Permissions in Service Plan are not working as expected​

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:

CentOS 7
Plesk 17.8.11 Update #9​

PROBLEM DESCRIPTION:

With the following permissions set (see below) on a Service Plan I would expect users, that are using it, would be able to make a full (website content and databases etc) backup only on their own FTP server. However I would also expect they are able to create a backup of the configuration settings like DNS and Mail on the server storage. This does not seem to work because when users are trying to do this they get an error asking them to configure a remote backup side. Is this a bug or am I interpreting these options wrong?

Service Plan permission settings:
Backup and restoration of subscription data using the server storage: Disabled
Backup and restoration of subscription data using an FTP storage: Enabled
Backup and restoration of account data using the server storage: Enabled
Backup and restoration of account data using an FTP storage: Enabled​

STEPS TO REPRODUCE:

Configure Service Plan with the following Backup and restoration settings:

Backup and restoration of subscription data using the server storage: Disabled
Backup and restoration of subscription data using an FTP storage: Enabled
Backup and restoration of account data using the server storage: Enabled
Backup and restoration of account data using an FTP storage: Enabled​

ACTUAL RESULT:

It disables the option to make a backup (small size) without website, mail or database content on server storage​

EXPECTED RESULT:

I expect it would give the user the option to create small backups by themselves but they are not allowed to backup the full website, mail and database content​

ANY ADDITIONAL INFORMATION:

​

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:

Confirm bug​

 

[IgorG]

From developer:

Ability to back up account data means backup of customer's own settings with all his subscriptions data. Currently, we have no separate permissions to distinct content of backups.