> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fusioncore.us/llms.txt
> Use this file to discover all available pages before exploring further.
# Set Up Person Accounts
> Enable and configure Person Accounts step by step so they work across fusionCore checkout, refunds, purchase tracking, credit, and order creation.
A **Person Account** is a single Salesforce record that combines an **Account** (an organization) and a **Contact** (a person) for one individual. fusionCore supports Person Accounts, but they need configuration before they work correctly across fusionCore's financial and transactional processes.
This runbook is for **system administrators and implementers** who are setting up an org. It is a one-time setup sequence: work through each section in order, because later steps depend on earlier ones. When you finish, Person Accounts behave correctly across these fusionCore flows:
* **Checkout** — placing orders through an Experience Cloud portal
* **Refunds** — returning payments to an individual
* **Purchase tracking** — recording what an individual has bought
* **Credit application** — applying an individual's credit or wallet balance
* **Order and opportunity creation** — generating orders and opportunities for an individual
The configuration makes sure the individual's contact details are recognized across fusionCore's standard and custom objects, and that the related fields are visible and usable on the right page layouts.
Enabling Person Accounts is **permanent and cannot be undone**. Once the feature is on, you cannot remove it from your org. Plan the setup before you enable Person Accounts in any environment.
Internal users and portal users may need different access. Portal-facing access usually relies on separate profiles and permission sets (for example, **fusionCore - Portal Guest User** and **fusionCore - Checkout**). Keep this distinction in mind as you work through the steps below.
## Before You Start
* You need an administrator login with permission to change setup (typically the **System Administrator** profile).
* Know which **page layout** your org uses for Accounts. In a fusionCore org the Account layout is usually **FC Account Layout**.
* Know which profiles need access to Person Accounts (for example **System Administrator**, **Standard User**, or a QA tester profile).
* Know which users need to see fusionCore business data on Person Accounts, so you can assign permission sets later.
* Have access to the **Membership** app and the **Accounts** tab for the final list-view step.
## Configure the Person Account Record Type
Before you enable Person Accounts, create a business **Account** record type. This gives organization-style Accounts their own record type, which keeps them separate from the Person Account record type that Salesforce adds automatically when the feature is enabled.
From **Setup**, type `Object Manager` in the **Quick Find** box and open **Object Manager**, then click **Account**.
Click **Record Types** in the left sidebar, then click **New**.
Complete the form:
* **Existing Record Type**: select **Master** (if it is not already chosen).
* **Record Type Label**: enter a name that fits your organization's naming convention, such as **Business Account** or **Organization Account**.
* **Record Type Name**: this auto-fills from the label.
* **Description**: optional, for example *Record type used for organization Accounts*.
* **Active**: make sure this checkbox is checked.
In the profile list, check **Make Available** for every profile that should use this record type. Then assign the page layout these profiles will see, which in a fusionCore org is usually **FC Account Layout**.
Click **Next**. On the page layout assignment screen, confirm the page layout (for example **FC Account Layout**), then click **Save**.
With the business record type in place, you can enable the Person Accounts feature.
## Enable Person Accounts
Before you can create Person Accounts, turn the feature on in **Setup**.
Enabling Person Accounts is **permanent and cannot be undone**. Once the feature is on, you cannot remove it from your org. Confirm you intend to use Person Accounts before you continue.
At least one profile must have a record type assigned for the **Account** object before you can enable the feature. The readiness check in the steps below confirms this for you.
From **Setup**, type `Person` in the **Quick Find** box, then click **Person Accounts**.
Click **Check Readiness**. Salesforce runs a system check to confirm your org meets the requirements (such as record type availability and permissions).
Click **View Org Impacts** to review how enabling Person Accounts will change your org. Read this list carefully, because the change is permanent.
Check the acknowledgment box labeled *"I understand that enabling this feature results in permanent changes to my Salesforce org."*, then click **Continue**.
On the confirmation popup, click **Enable Person Accounts**. When prompted, click **Enable**.
Your Salesforce org now supports Person Accounts.
## Assign Person Accounts to Profiles
After you enable Person Accounts, make the **Person Account** record type available on the **Account** object for each profile whose users need to create or work with Person Accounts. Until you do this, those users cannot select Person Account when they create an Account.
From **Setup**, type `Profiles` in the **Quick Find** box, click **Profiles**, then select the profile you want to update (for example **System Administrator**).
On the profile page, scroll to the **Record Type Settings** section, find **Accounts**, and click **Edit** next to it.
Move **Person Account** into the **Selected Record Types** list so the profile can use it. Then, under **Default Record Type**, set the default as needed for this profile (for example, set the **Person Account** default to **Person Account**).
Click **Save** to apply the changes.
Repeat these steps for any additional profile whose users need Person Accounts, such as **Standard User** or a QA tester profile.
## Update Layouts for Person Accounts
After you enable Person Accounts, update the Person Account layout so the fusionCore fields and actions you need are visible. This step has two parts:
* **Part A** adds fusionCore fields and actions to the **Person Account** page layout.
* **Part B** creates a **compact layout** for Person Accounts and sets it as the default.
### Part A: Update the Person Account Page Layout
Go to **Setup**, then click **Object Manager**.
In the **Quick Find** box, type `Person Account`, then click **Person Account**.
Click **Page Layouts** in the left menu, then click **Person Account Layout**.
In the layout editor, drag the following fields from the field palette onto the layout, positioning them wherever suits your business process:
* **Total Available Individual Credit**
* **Email**
* **Title**
The buttons users can click at the top of a record live in the **Mobile and Lightning Actions** section of the layout. Click that section, then click **Override the predefined actions** so you can choose exactly which actions appear instead of the org defaults. Drag the following actions into the **Salesforce Mobile and Lightning Experience Actions** section, then rearrange them into the order you want:
* **Create Order**
* **Enable Customer User**
* **Log in as Experience User**
Click **Save** to finalize your changes.
### Part B: Create and Assign a Compact Layout
Creating a **compact layout** for Person Accounts keeps the most useful fields in view at the top of the record.
In the **Person Account** object in **Object Manager**, click **Compact Layouts**, then click **New**.
Set **Label** to `Person Account Compact Layout`, then under **Fields to display** add:
* **Account Name**
* **Email**
* **Title**
* **Phone**
* **Billing Address**
Click **Save**.
A new compact layout has no effect until you set it as the primary layout for the object. In **Compact Layouts**, click **Compact Layout Assignment**, then click **Edit Assignment**. From the **Primary Compact Layout** dropdown, select **Person Account Compact Layout**, then click **Save**.
## Assign Person Account Fields to Object Page Layouts
Several fusionCore objects — such as **Credit** and **Order** — can belong to either an organization or an individual, so they need a field that shows the right customer name in either case. fusionCore ships two formula fields that handle this for you:
* `FS_Customer__c` — shows the customer's name as a clickable link.
* `FS_Customer_Name__c` — shows the customer's name as plain text.
Each field checks the record's **Customer Type**. For an organization it shows the **Account** name; for an individual it shows the related **Contact** name. The older, non-`FS_` versions of these fields were not designed for Person Accounts and do not resolve the individual's name correctly. On the page layouts below, add the `FS_` field and remove the older version it replaces.
Go to **Setup**, then in **Quick Find** type `Object Manager` and open it.
For each object in the table below, open the object, click **Page Layouts**, and open the layout you use.
Drag the listed field onto the layout where you want it to appear.
Remove the older, non-`FS_` version of the same field from the layout, then click **Save**.
Add these fields to the matching object layouts:
| Object | Field to add | What it shows |
| ------------------------- | ------------------------------------------ | -------------------------------------------------------------------------------- |
| **Credit** | `FS_Customer__c` | Customer name as a link (Account for organizations, Contact for individuals) |
| **Purchase Activity** | `FS_Customer__c` | Customer name as a link (Account for organizations, Contact for individuals) |
| **Opportunity Line Item** | `FS_Customer_Name__c` | Customer name as plain text (Account for organizations, Contact for individuals) |
| **Order** | `FS_Customer__c` | Customer name as a link (Account for organizations, Contact for individuals) |
| **Order Item** | `FS_Customer__c` and `FS_Customer_Name__c` | Customer name as a link and as plain text |
On each layout, also remove the older non-`FS_` version of the customer field. Those fields predate Person Account support and do not resolve the individual's name for Person Accounts.
## Assign Permission Sets for Person Account Access
fusionCore ships two permission sets that grant access to the fusionCore business-data fields used by Person Accounts:
* `FS Person Account - Manage Business Data` (API name `FS_Person_Account_Manage_Business_Data`)
* `FS Person Account - View Business Data` (API name `FS_Person_Account_View_Business_Data`)
Both permission sets grant access to the fusionCore business-data fields (`FS_Customer__c` and `FS_Customer_Name__c`) on the **Credit**, **Purchase Activity**, **Opportunity Line Item**, **Order**, and **Order Item** records. With this access, those fields resolve correctly for Person Accounts. Assign the permission set (or sets) to any user who needs to see fusionCore business data on Person Accounts.
The two labels suggest different intents, but in the current release both permission sets grant the same field access. Assign whichever one matches how you organize access in your org.
Click the gear icon at the top right and select **Setup**. In the **Quick Find** box, type **Permission Sets**, then click **Permission Sets**.
Click the permission set you want to assign: `FS Person Account - Manage Business Data` or `FS Person Account - View Business Data`.
Click **Manage Assignments**.
Click **Add Assignments**, then select the users who need this access.
Click **Assign** to grant the access.
## Configure a List View for Person Accounts
By default the **Accounts** tab mixes organizations and individuals, so this final step creates a list view that shows only Person Accounts, with the most useful fields visible.
### Open the Accounts Tab
Click the **App Launcher**, then open the **Membership** app.
Click the **Accounts** tab. The list view dropdown in the top left shows your current view, such as **Recently Viewed**.
### Create the List View
Click **List View Controls** (the gear icon) on the right of the list, then select **New**.
Set **List Name** to `Person Accounts`. The **List API Name** fills in automatically.
Under **Who sees this list view**, select **All users can see this list view** (or a narrower option if you prefer).
Click **Save**.
### Choose the Fields to Display
Click **List View Controls** again, then select **Fields to Display**.
From **Available Fields**, add the fields that are useful for Person Account users, such as:
* **Account Name**
* **Email**
* **Phone**
* **Billing City**
* **Billing State/Province**
* **Customer Type**
Click **Save**.
### Filter to Show Only Person Accounts
Click the **Filter** icon (the funnel at the top right).
Set **Filter by Owner** to **All accounts**.
Click **Add Filter** and set:
* **Field**: **Is Person Account**
* **Operator**: **equals**
* **Value**: **True**
Click **Done**, then **Save**.
You now have a **Person Accounts** list view that shows only Person Accounts with the most relevant fields.
## Limitations and Common Pitfalls
Keep these in mind as you set up and work with Person Accounts.
Enabling Person Accounts is permanent and cannot be undone. Plan before you turn the feature on.
* **Enable the feature only after the record type exists.** At least one profile must have a record type assigned for the **Account** object, or the readiness check will fail. Configure the business Account record type first.
* **Person Account users cannot select the record type until you assign it to their profile.** If users cannot create Person Accounts, confirm the **Person Account** record type is in the **Selected Record Types** list on their profile.
* **The customer name can show blank or wrong if the layouts are not updated.** fusionCore uses `FS_Customer__c` and `FS_Customer_Name__c` to resolve the individual on Order, Credit, Purchase Activity, Opportunity Line Item, and Order Item records. If those fields have not been added in place of the older non-`FS_` fields, the customer name can appear blank or incorrect for Person Accounts.
* **Fields can still appear empty even after layouts are updated.** A user needs one of the fusionCore permission sets to see the business-data fields. Assign `FS Person Account - Manage Business Data` or `FS Person Account - View Business Data` to users who need that access.
## Related Features
What Person Accounts are and how fusionCore uses them. Start here for background before you configure your org.
How an individual's address flows through fusionCore once Person Accounts are set up.