Published at: 2026-09-17
Manage custom objects
View, enable, disable, delete, and clone custom objects that you have created.
Overview
After creating custom objects, administrators need to maintain object status on an ongoing basis. Common operations include viewing the object list, enabling objects, disabling objects, deleting objects, and cloning objects.
Before you begin
[!IMPORTANT] - Role permissions: You need the relevant back-end permissions for object management. - Impact scope: Enabling or disabling an object affects whether front-end users can access it. - Risk confirmation: Deleting an object is a high-risk operation. Complete a data backup and dependency check first.
View custom objects
- Go to Setup > Object Management > Custom Object Management.
- On the Custom Object Management page, view the object name, status, creation time, and
API name. - Use the search or filter functionality to locate the target custom object.
- Open the target object to view its basic information, fields, layouts, rules, and permission settings.
Enable a custom object
After an object is enabled, front-end users can access it through the app menu, object entry, or related business entry.
- Go to Setup > Object Management > Custom Object Management.
- Locate the target object in the list.
- Open the object basic information.
- Set the object status to Enabled.
- Click Save.
- Log in to the front end with a target business role account and verify that the object entry is visible.
[!NOTE] Enabling an object does not grant all users access. Users also need object permissions, field permissions, and the corresponding menu entry.
Disable a custom object
When an object is temporarily no longer in use or requires structural adjustments, disable it first.
- Go to Setup > Object Management > Custom Object Management.
- Locate the target object in the list.
- Click Disable, or change the status to Disabled in the object basic information.
- Confirm and save.
- Log in to the front end and verify that the object entry is hidden.
[!WARNING] If the object has relationships with other objects, the system may not allow disabling. Check lookup relationship fields, master-detail relationship fields, layouts, rules, functions, and workflow references first.
Delete a custom object
Delete objects to clean up custom objects that are no longer in use.
- Confirm that the target object data has been backed up.
- Check whether the object is referenced by fields, layouts, workflows, rules, buttons, functions, or external integrations.
- Set the target object to Disabled.
- In the Custom Object Management list, click Delete in the action column for the target object.
- Verify the object name in the confirmation dialog.
- Confirm the deletion.
[!CAUTION] Deleting an object is irreversible. After deletion, data, fields, page layouts, rules, buttons, and related configurations under the object are affected. Exercise caution in production environments.
Clone a custom object
Cloning an object is useful for quickly creating a new object with a similar structure based on an existing one.
- Go to Setup > Object Management > Custom Object Management.
- Locate the object to clone in the list.
- Click Clone in the action column.
- On the clone page, enter the new object name and
API name. - Review the fields and basic configuration to clone.
- Click Save.
- Open the new object and recheck the fields, layouts, permissions, rules, and record type configuration.
[!TIP] Cloning only reduces repetitive configuration work. After cloning, recheck the object name, field names, permission scope, and page layout based on the new business scenario.
Verification
- In the back-end object list, confirm that the object status is correct.
- Use an administrator account to open the object configuration page and confirm that the object is editable.
- Log in to the front end with a target business role account.
- Verify that the object entry matches the expected enable or disable status.
- If cloning was performed, confirm that the new object fields, layout, and permissions meet expectations.
- If deletion was performed, confirm that the object no longer appears in either the front-end entry or the back-end object list.
Related topics
- Create custom objects
- Field overview
- Configure object permissions
- Object customization FAQ