Enable Person Accounts | Prerequisites for Enabling Person Accounts | Salesforce Exam Prep

Prerequisites for Enabling Person Accounts

Question

The Cloud Kicks (CK) IT team wants to enable Person Accounts in its Salesforce org.

Which three prerequisites must be met before the consultant can enable Person Accounts? (Choose three.)

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E.

ACD

To enable Person Accounts in a Salesforce org, the following three prerequisites must be met:

A. At least one Record Type should be created for Accounts: Enabling Person Accounts requires creating a new Record Type specifically for Person Accounts. This Record Type allows you to differentiate between Person Accounts and regular Business Accounts. By creating this Record Type, you can customize the page layouts, fields, and business processes specific to Person Accounts.

D. User Profiles with Read access to Accounts must also have Read access to Contacts: To enable Person Accounts, the User Profiles that have Read access to Accounts should also be granted Read access to Contacts. This ensures that users who can view Account records can also view associated Contact records, as Person Accounts blur the distinction between Accounts and Contacts.

C. The organization-wide default sharing is set so either Contact is Controlled by Parent or both Account and Contact are Private: The organization-wide default sharing settings for Contacts should be set to either "Controlled by Parent" or both Account and Contact should be set to "Private." This is because Person Accounts merge the concepts of Accounts and Contacts, and they share the same fields and access controls. By setting the Contact sharing to either "Controlled by Parent" or "Private," you ensure that the sharing rules and access controls for Person Accounts function correctly.

It's worth noting that the other options, B and E, are incorrect:

B. The organization-wide default for both Accounts and Contacts should be set to Public Read/Write: Setting the organization-wide default sharing for both Accounts and Contacts to Public Read/Write is not a prerequisite for enabling Person Accounts. In fact, Person Accounts require a different sharing model, where the access to Account and Contact records is controlled based on the organization-wide default settings mentioned in prerequisite C.

E. The CK customer portal must be disabled to allow Person Account self-registration in the future: Disabling the CK customer portal is not a prerequisite for enabling Person Accounts. Person Accounts allow for self-registration by individuals, but the availability of self-registration is not dependent on the status of the customer portal.

In summary, before enabling Person Accounts, you need to create a Record Type for Accounts, ensure that User Profiles with Read access to Accounts also have Read access to Contacts, and set the organization-wide default sharing to either "Contact is Controlled by Parent" or both "Account and Contact are Private."