Your Archive region—not your Salesforce org's Hyperforce status—determines whether Archive uses an authenticated user or the Platform Integration User (PIU), and which setup, security, and import and export options you see.
Your Salesforce org's Hyperforce status and your Archive region's Hyperforce status are independent, because Archive runs as a separate service with its own region. Your org can be on Hyperforce while your Archive onboards to a non-Hyperforce region, depending on your geographic location. Your org can also be on a non-Hyperforce region while your Archive is on Hyperforce.
Your Archive Region
Whether Archive prompts you for an authenticated user depends on your Archive region, the data region where your archived data is stored, not on your Salesforce org.
The Archive Settings page shows you which region you're in.
- If Archive prompts you for an authenticated user's username and password, your Archive region is a non-Hyperforce archive region.
- If Archive doesn't prompt you, your Archive region is a Hyperforce archive region.
To find your Archive region, in the Archive app go to . If your Archive is in a Hyperforce region, the Region field shows Hyperforce. It doesn't name the specific region. If your Archive is in a non-Hyperforce region, the field shows the specific region name.
Authenticated Users in Non-Hyperforce Regions
On a non-Hyperforce archive region, Archive connects to your Salesforce org through an authenticated user. During setup, you enter that user's username and password. For the license and permissions this user needs, see Authenticated User Permission Requirements for Archive.
Your Archive region is set when your Archive service is provisioned, based on when your Archive contract starts. Your Archive region doesn't change just because your Salesforce org moves to Hyperforce.
Platform Integration User on Hyperforce
On Hyperforce, Archive connects through the Platform Integration User (PIU)—a Salesforce-managed internal user built into every org. Because Archive operates within the Salesforce domain, there's no manual authentication process. While you cannot create or delete the PIU, admins can manage certain permissions assigned to it. For details, see Salesforce Help: Platform Integration User.
Hyperforce Archive Region Availability
Archive on Hyperforce is available in these regions.
- Tokyo
- Osaka
- Mumbai
- Hyderabad
Orgs on these regions that were provisioned on or after July 2026 onboard to the matching Hyperforce archive region. Orgs provisioned before that date can be on a non-Hyperforce archive region.
To check your Salesforce org's Hyperforce status, ask your Salesforce admin.
What Changes in Setup on Hyperforce
On a Hyperforce archive region, the setup interface hides the authenticated-user settings because an authenticated user isn't used. This list shows what changes.
- Authenticated-user settings and section are removed. An authenticated user applies only to non-Hyperforce archive regions.
- Field-Level Security (FLS) isn't applicable. Hyperforce security controls make separate Field-Level Security settings redundant.
- Shield Platform Encryption integration is available. See Shield Platform Encryption on Hyperforce.
Shield Platform Encryption on Hyperforce
Shield Platform Encryption integration is available only in a Hyperforce archive region. It requires a Salesforce Shield or Shield Platform Encryption add-on license. Activation and key management happen in Shield Platform Encryption, not in Archive Settings. Archive Settings shows only the key status. See Configure Archive Settings and Salesforce Help: Strengthen Your Data's Security with Shield Platform Encryption.
Changes to Import and Export on Hyperforce
On a Hyperforce archive region, these import and export options change.
- Amazon S3 integration for import and export isn't available for Hyperforce archive regions.
- The Export option for CSV files on the home page is no longer available. Export CSV files from search instead.