Gearset

If your source and target are both on the API v50 (Winter '21) and 

you are deploying a profile that contains this in the source ​<code>&lt;tabVisibilities&gt;</code> ​<code>&lt;tab&gt;standard-DelegatedAccount&lt;/tab&gt;</code> ​<code>&lt;visibility&gt;DefaultOff&lt;/visibility&gt;</code> ​<code>&lt;/tabVisibilities&gt;</code>

- If your source and target are both on the API v50 (Winter '21) and 
- you are deploying a profile that contains this in the source ​<code>&lt;tabVisibilities&gt;</code> ​<code>&lt;tab&gt;standard-DelegatedAccount&lt;/tab&gt;</code> ​<code>&lt;visibility&gt;DefaultOff&lt;/visibility&gt;</code> ​<code>&lt;/tabVisibilities&gt;</code>

<code>You can't edit tab settings for DelegatedAccount, as it's not a valid tab.</code>

This is happening because Salesforce API does not support<code> DelegatedAccount</code> in tabs. Please report this to Salesforce support.

If you are deploying from org to org, you can workaround this error by removing the <code>DelegatedAccount</code> custom object from your metadata filter. This will prevent the profile from<a href="https://docs.gearset.com/en/articles/2509281-using-gearset-to-deploy-profiles"> retrieving the tab visibilities</a> for this custom tab, and therefore not deploy this section.

If you are deploying from Git (where <a href="https://docs.gearset.com/en/articles/3845806-in-git-with-org-comparisons-why-are-the-results-different-from-org-to-org-comparisons">all components</a> of a profile are retrieved) you can work around this and still deploy the Profile by:

Downloading the deployment package, from the <code>Download package</code> button on the deployment summary page before the deployment. (See <a href="https://docs.gearset.com/en/articles/3313889-how-to-replicate-deployment-errors-with-other-tools">here</a> for more instructions)

Edit the<code> .profile</code> file (using software that can view the XML such as Notepad, TextEdit or VSC) to delete the four lines that reference <code>standard-DelegatedAccount</code>.

Create a new comparison with<code> Local files</code> as the modified <code>.profile</code> file (with the valid <code>package.xml</code>) and deploy.

1. Downloading the deployment package, from the <code>Download package</code> button on the deployment summary page before the deployment. (See <a href="https://docs.gearset.com/en/articles/3313889-how-to-replicate-deployment-errors-with-other-tools">here</a> for more instructions)
2. Edit the<code> .profile</code> file (using software that can view the XML such as Notepad, TextEdit or VSC) to delete the four lines that reference <code>standard-DelegatedAccount</code>.
3. Create a new comparison with<code> Local files</code> as the modified <code>.profile</code> file (with the valid <code>package.xml</code>) and deploy.

Hopefully this workaround will help you deploy your profile while this Salesforce metadata API bug is being investigated.