Key Considerations for Enabling Person Accounts in Your Org

D

When evaluating Person Accounts in Salesforce, there are several important considerations to keep in mind. Let's go through each answer choice and explain whether it is true or false:

A. The Person Account object must have at least two record types.

• This statement is false. Person Accounts do not require multiple record types. In fact, Person Accounts have a predefined record type called "Person Account" that is automatically created when Person Accounts are enabled. This record type cannot be deleted or deactivated.

B. Enabling Person Accounts requires a Public Read/Write sharing model.

• This statement is true. Enabling Person Accounts does require a Public Read/Write sharing model. By default, the Account object in Salesforce follows a Private sharing model, which means that only the owner and users above the owner in the role hierarchy can access the account records. However, Person Accounts require a different sharing model where records are accessible to a broader set of users. Enabling Person Accounts will automatically switch the sharing model for the Account object to Public Read/Write.

C. Person Account records only count toward Account storage.

• This statement is false. Person Account records count towards both Account storage and Contact storage. In Salesforce, a Person Account is a hybrid record that combines elements of both the Account and Contact objects. It behaves as a single record, but it actually consumes storage space for both an Account and a Contact. So when evaluating storage limits and usage, both Account and Contact storage should be considered when Person Accounts are enabled.

D. Enabling the Person Accounts feature is irreversible.

• This statement is true. Enabling the Person Accounts feature in Salesforce is irreversible. Once Person Accounts are enabled in your org, it cannot be disabled or turned off. It's important to consider this fact before making the decision to enable Person Accounts, as it has a long-lasting impact on the data model and functionality of your org.

In summary, when evaluating Person Accounts, the consultant should consider the following points:

• Enabling Person Accounts requires a Public Read/Write sharing model.
• Person Account records count towards both Account storage and Contact storage.
• Enabling the Person Accounts feature is irreversible.

These considerations will help the consultant assess the impact and feasibility of enabling Person Accounts in Cloud Kicks' org and make an informed recommendation to the sales director and team.