---
schema_version: "1"
id: e73f94c7dc2a151dc88660cb24f1bda9be5b544cf2ca33ef6be230ab1df4bed0
title: Considerations and Limitations for Quick Pages (Beta)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/quick_pages_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.quick_pages_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: f1b1c6ee856e052303257b961e27a78780646f59fcc3eb84381772a0f0d50a41
description: During the beta, keep these considerations and limitations in mind.
products:
  - Salesforce Platform
release: "264"
---
# Considerations and Limitations for Quick Pages (Beta)

During the beta, keep these considerations and limitations in mind.

- Salesforce isn’t charging for AI usage in Quick Pages during the beta. When the feature becomes generally available, AI usage in Quick Pages becomes metered.
- For best performance, keep your prompts brief and specific. Long prompts time out after two minutes.
- Quick Pages are read only. You can’t create, update, or delete a record from a Quick Page. To update the information on the page, update the data in the relevant object or field in your org, then refresh the Quick Page.
- After you save a Quick Page, you can’t change the page’s name.
- When you view a shared Quick Page, you see only the data that you have access to, so different page viewers can see more or less information than the page creator can.
- An admin can see or share a Quick Page created by another user, but can’t edit or delete the page.
- You can’t use Connect REST API or Apex classes inside a Quick Page to get data from Salesforce.
- A Quick Page can’t:
    - Connect to Data 360
    - Access assets from Salesforce CMS or Salesforce Files
    - Use APIs to query data that’s external to Salesforce
    - Move between orgs via data export
    - Be included in a package