Limits for contacts associated with business accounts.
Contacts are the people associated with business accounts that are tracked in Salesforce. Each contact includes various kinds of information, such as phone numbers, addresses, titles, and roles in a deal.
Sharing and Access Limitations for Contacts
- Contact sharing isn’t available for organizations that have territory management or person accounts.
- You can’t restrict access to contacts beyond your organization’s default access levels.
- You need at least read access to the contacts and leads that you invite to an event. You need at least “Add Events” on a resource to invite it to an event.
- A contact that isn’t linked to an account is always private, regardless of your organization’s sharing model. Only the owner of the contact and administrators can view it. Sharing rules and workflow rules don’t apply to private contacts. If your organization uses divisions, private contacts always belong to the global division.
- If a recipient doesn’t have access to the account, you can’t share the contact unless you also have permission to share the account.
- If your organization-wide default for contacts is set to Controlled by Parent, the Contact Access options aren’t available when you share related records such as accounts. Instead, all access to contacts is determined by the user’s access to the contact’s account.
- If your organization-wide default for contacts is Controlled by Parent and your organization-wide default for accounts is Private, you can’t view contacts for accounts that you don’t own, even if you have the View All permission on the account object. However, if you own a contact on an account, you can view other contacts on the same account. (Access to a parent account gives you access to the associated child records.)
Limitations for Merging Contacts
- You can’t modify the Merge My Contacts page layout.
- When you’re searching for contacts to merge, you can’t add filters to the search criteria.
- Merged contacts don’t retain related Chatter feeds.
Limitations for Importing Contacts from Mobile Device Contact Lists
- When importing contacts from an Android or iOS device using Salesforce1 into a Salesforce org that has State and Country picklist fields enabled, the State field isn’t populated.
- If you have multiple mobile phone fields in your mobile device’s contact, and the Phone field in Salesforce is empty:
- The first mobile phone field maps to the Phone field in Salesforce.
- The second mobile phone field maps to the Mobile field in Salesforce.
- When you select emails from the mobile device, Salesforce1 typically pulls the second email address location. If labels are created on the device, the integration tries to map from the local work email address to the standard contact email address in Salesforce.
Contact History Limitations
- Modifications to the related lists for a contact aren’t tracked in the contact history.
Limitations for Enabling and Managing the Customer Portal for Contacts and Person Accounts
- Delegated administrators can’t assign the High Volume Customer Portal license to contacts.
- When you create a customer user from the API, the Chatter Answers User permission isn’t selected for that user.
- When person account users try to self-register for a customer portal, they receive an email notification that instructs them to contact the portal admin. See Enable Customer Portal Login and Settings.
- You can’t merge person accounts that are enabled to use a customer portal.
- You can’t delete a person account that’s enabled to use a customer portal.
- You can transfer contacts that are enabled for a partner portal only to accounts that are also enabled for a partner portal.
Limitations for Changing Accounts on Contacts That Are Enabled for Self-Service
- On the Self-Service portal, contacts that are Self-Service users can view cases only if they’re associated with their current account.
- Self-Service users can’t view opportunities.
Limitations for Deleting Self-Service for Contacts and Person Accounts
- You can’t delete an active Self-Service user. You can only deactivate the user’s access to the Self-Service portal.
- You can’t delete a contact or person account that’s associated with an active Self-Service user. Instead, deactivate the user’s access to the Self-Service portal, and then delete the contact or person account.