---
schema_version: "1"
id: 0db1693a7eabae8fb28b1f7d975931228335e56b2f26b171d2b2f70cd6889d0d
title: Best Practices and Considerations for Page-Level Access in Experience Builder
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/networks_page_level_best_practices.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.networks_page_level_best_practices.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 7baa702877c9fb85456721583ab6ba36e800bd6f1cbccc1e41de48aeae7c2d50
description: Experience Builder is a powerful tool for keeping your Experience Builder site secure. Keep these best practices and considerations in mind when working with access levels.
products:
  - Security
  - Salesforce Platform
release: "264"
---
# Best Practices and Considerations for Page-Level Access in Experience Builder

Experience Builder is a powerful tool for keeping your Experience Builder site secure. Keep these best practices and considerations in mind when working with access levels.

- Don’t create object pages for objects that aren’t exposed to external users. If you have object pages that aren’t being used, delete them.
- Use specific object pages when possible. These pages make public URLs more discoverable to your users.
- If you set up object pages for authenticated users, test the pages to ensure that guest users can’t see them.