How Do I Setup Salesforce Surveys for External Guest Users?
When looking for an effective answer to "How do I setup Salesforce surveys?", many administrators expect a simple, out-of-the-box wizard. On paper, Salesforce Surveys are the ideal mechanism for a UK business to collect customer feedback or a charity to track beneficiary outcomes.
In practice, opening surveys up to external, unauthenticated public users (Guest Access) introduces an intricate matrix of security controls, framework requirements, and email delivery rules.
If your organisation is hitting an unexpected "record not found" error or discovering that external participants cannot access your forms, use this technical configuration blueprint developed by the deployment experts at Zon Projects.
Architectural Prerequisites
Before authoring survey questions, the fundamental platform architecture must support external data ingestion. Modern Salesforce instances require strict alignment between the survey tool and your digital experience infrastructure.
┌───────────────────────────────┐
│ LWR Experience Site │
│ (Enhanced Framework Required)│
└───────────────┬───────────────┘
│
▼
┌──────────────────────────────────────────────────────────────────┐
│ Guest User Profile │
│ [Surveys: Read] [Invitations: Read] [Responses: Read/Create]│
└──────────────────────────────────────────────────────────────────┘
1. Framework Alignment
The native Survey Builder will fail to function or display correctly if pointed at an outdated Experience Cloud site. Ensure your Survey Settings point directly to an LWR (Lightning Web Runtime) Enhanced Site. Legacy Aura frameworks do not natively support the modern survey components.
2. Object-Level Guest Permissions
Because Salesforce enforces a "Secure Guest User Record Access" policy, public unauthenticated users have no data visibility by default. You must navigate directly to your specific Experience Site's Guest User Profile and apply explicit object settings:
Surveys: Read
Survey Invitations: Read
Survey Responses: Read and Create (Crucial for allowing users to submit answers)
Resolving Delivery and Branding Blocks
Once the structural permissions are open, distribution frequently encounters silent failures within sandbox and testing environments.
The Missing Branding Record
The native "Send Email" wizard within the survey canvas will refuse to load the email composer if it cannot find a core branding reference. You must ensure at least one SurveyEmailBranding record is created and populated within your environment, utilizing a verified organizational or system address as the "From" sender.
Sandbox Deliverability Settings
A common roadblock during the testing phase is a silent block on outgoing emails. When a sandbox environment is refreshed, Salesforce automatically sets email deliverability to "System Email Only". This restriction completely blocks the survey distribution engine. To test your setup successfully, you must explicitly toggle this setting back to "All Email" within Setup.
DNS Domain Verification
To protect your brand reputation and ensure high email deliverability, your outbound survey emails must stem from a verified domain.
Technical Requirement: Permanent resolution requires your IT infrastructure team to add a specific Salesforce TXT Record to your public DNS zone files. While executing sandbox testing, utilizing a verified Org-Wide email address acts as a reliable interim workaround.
Why Partner with a Trusted UK Salesforce Specialist?
Configuring external access, data mapping, and Experience Cloud security requires deep technical expertise. Growing UK SMEs and charities cannot afford to leak data or lose critical feedback loops to configuration errors.
At Zon Projects, we manage the underlying technical complexities of the Salesforce platform so you can focus on leveraging your data. We ensure your implementations are secure, compliant, and architected to deliver immediate value.

