---
schema_version: "1"
id: 33635215c3944de9d42b7c2859f272da5505641d8862492353fbfe899d8b9f5f
title: Preference Form Access Tokens
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/about_access_tokens.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.about_access_tokens.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 37216227673748caf25ac2a8987d3964ec0922e1e607d3a213b4f87c1e3eaacb
description: Create preference form access tokens so that users can view and edit your preference forms from an external site, static web page, or Experience Cloud site without logging in. You can create access tokens in Preference Manager or with REST API or Apex.
products:
  - Security
  - Cross Cloud
release: "264"
---
# Preference Form Access Tokens

Create preference form access tokens so that users can view and edit your preference forms from an external site, static web page, or Experience Cloud site without logging in. You can create access tokens in Preference Manager or with REST API or Apex.

### 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>Developer</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, and <strong>Unlimited</strong> Editions. Requires the Salesforce Privacy Center license.</td></tr></tbody></table>

An access token is an encrypted version of a record ID. You send a user a unique URL to your site where the preference form is hosted. The unique URL includes an access token. When the access token and record ID match, the user’s consent information is loaded into the form. For each user, the form populates with their consent information so that they can make their preference selections.

Keep these consideration in mind when creating an access token.

- Use record IDs for the Account, Contact, Individual, Lead, Person, or User objects. If you used the Basic consent template to create a preference form, the user’s consent is stored directly on a standard object (for example, on the Account object or Contact object). In this scenario, generate a token that references a record ID on the same standard object. All other consent templates require an association with an Individual record.
- If you create custom fields on the Account, Contact, Individual, Lead, Person, or User objects to store the access token strings, you can pass the token strings as parameters for email template builders.
- An access token expires after 2 years or until programmatically revoked.