Body: I’m stuck on the Trailhead challenge “Handle Field Access with a Permission Set” (Recruiting app). The checker reports it can’t find a permission set that grants read/edit on all Job Application fields except Position and Candidate (read-only). I’d appreciate guidance on what I’m missing.
Requirements I’m following:
Create a permission set:
Label: Manage Job Applications
API Name: Manage_Job_Applications
License: None
Job Application object permissions: Read, Edit (no Create/Delete/View All/Modify All)
Field-level security on Job Application: all fields readable and editable, except Position and Candidate (read-only)
What I configured:
Permission Set
Label/API/License match the spec: Label “Manage Job Applications”, API Name “Manage_Job_Applications”, License “None”.
Object Settings > Job Application:
Object Permissions: Read and Edit only; Create/Delete/View All/Modify All are unchecked.
Field Permissions:
I enabled Read and Edit for all fields, then unchecked Edit only for Position and Candidate, keeping Read checked.
I re-verified that every other field has Edit=ON, and Position/Candidate have Edit=OFF.
Job Application object definition
Label: Job Application; Plural: Job Applications
API Name: Job_Application
Record Name: Job Application Name (Auto Number; Display Format: JA-{0000})
Optional features: Allow Reports=On, Track Field History=On; Allow Activities/Allow in Chatter Groups/Enable Licensing=Off
Classification: Allow Sharing=On; Allow Bulk API Access=On; Allow Streaming API Access=On
Deployment Status: Deployed=On
Search Status: Allow Search=Off (can turn On if required)
Org Language/Locale: Language=English; Locale=United States
Fields on Job Application
Position (API: Position__c): Lookup (or Master-Detail) to the Position object.
Candidate (API: Candidate__c): Lookup to the Candidate object.
Both are English labels/API names. I did not create similarly named extra fields (e.g., Position_Lookup__c).
Profiles/Assignments
Error message (excerpt): “Couldn’t find the ‘Manage Job Applications’ permission set that grants read and edit access to all Job Application fields except Position and Candidate.”
Troubleshooting already done:
Switched org Language/Locale to English/United States, waited a few minutes, and re-ran the check.
Reconfirmed Job Application > Field Permissions: Position/Candidate are Read=On, Edit=Off; all others Read/Edit=On.
Reconfirmed object permissions are exactly Read+Edit only.
Verified Position/Candidate field data types and lookup targets.
Ensured there are no duplicate or similarly named fields.
Verified object labels and API names conform to the spec.
Open questions:
Does the checker require an actual user assignment of the permission set?
Are there any other commonly missed toggles (e.g., View All/Modify All flipped on elsewhere, permission set group interactions, metadata propagation delays)?
What I can provide:
Screenshot of the permission set (Manage Job Applications) > Object Settings > Job Application > Field Permissions showing Position/Candidate Edit=Off and all others Edit=On.
Job Application Fields & Relationships list (with Position__c/Candidate__c types and lookup targets).
Org Language/Locale settings.
User permission summaries if needed.
Goal: Identify the minimum changes needed for the checker to pass (e.g., turning on Allow Search, changing Record Name to Text, assigning the permission set), so I can re-run the challenge successfully.
Thanks in advance for your help and any insights!
#Trailhead Challenges
The wording can not find a permission set that grants... is the clue — the grader looks the set up by API name first, then checks the field pattern. Two things trip most people here:
1. The API name must be exactly Manage_Job_Applications (underscores, not spaces). If it is even slightly different the grader cannot find it and reports exactly that message. Open the permission set and confirm the API Name reads Manage_Job_Applications.
2. Position and Candidate must be Read-only, meaning Read checked and Edit unchecked — not hidden. If you unchecked Read as well they count as not readable and the all-fields-readable check fails. Verify both show Read on, Edit off.
Also worth a quick pass:
- Every other Job Application field needs BOTH Read and Edit checked. Scroll the entire field list — a single field left without Edit fails it. (Any formula field can only be Read, and that is expected.)
- Object permissions: Read and Edit only, which you have — no Create, Delete, View All, or Modify All.
Nine times out of ten on this one it is the API name, or Position/Candidate being hidden instead of read-only. Fix that and recheck.
if this helps, please mark it as the Best Answer so it helps the next person — thanks 🙂
