---
schema_version: "1"
id: eb73193bd89e818649d24249ec0634f2eced2388ace3784f638d9d047a0b7ed3
title: Considerations for Document Ranges
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/quip_document_range_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.quip_document_range_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 7b722b037141c4ffc24544087e9079703412b2dd711d164d75f7c925ea3f8c16
description: As you set up document ranges in your templates, keep in mind these considerations.
products:
  - Quip
  - Cross Cloud
release: "264"
---
# Considerations for Document Ranges

As you set up document ranges in your templates, keep in mind these considerations.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Lightning Experience</strong></td></tr></tbody></table>

## Template Format

You can see your document ranges only in templates. You can add automation to documents based on a document range, but you can’t click **Show Document Range** in a document to see the defined sections.

Document ranges aren’t supported in spreadsheets or slides.

## Document Range Identification

Document ranges are defined only by headers. Paragraphs, checklists, and other formats don’t define the start or end of a document range.

If a header used for automation is edited, the automation can’t find the document range. To avoid broken automation, lock edits to headers you want to use for document ranges.

@Mentions, data mentions, and mail merge syntax don’t work well with document range automation. For the best experience, use static headers to define your document ranges.

If a document or template has multiple headers of the same name, automation endpoints use the first instance of that header.

If a document or template has multiple columns, showing a document range from a column highlights the document width. Automation based on the document range header still works as expected.