Feed

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! 

Hi Community,

We're a nonprofit implementing Agentforce Nonprofit with Program and Benefit Management enabled, and we're looking for advice on our data model for storing ride information from an external ride provider.

Our Use Case

We offer secure rides as a client benefit. Ride data is sourced from external ride provider’s system and pushed into Salesforce via API. A key requirement is that we do not store any PII in Salesforce — client identity is managed through tokenized Person Accounts (e.g., "Client 00123") with an External ID that maps back to the source system.

Our Proposed Data Model

We plan to use the native Agentforce Nonprofit Program and Benefit Management hierarchy:

Program → Benefit (Type: Service) → Program Enrollment (Token-based Person Account) → Benefit Assignment → Benefit Disbursement (each individual ride)

Each ride from an external ride provider would be stored as a Benefit Disbursement record, upserted via API using an External Ride ID field. We'd add custom fields to the BenefitDisbursement object (surfaced via the Benefit Disbursement Field Set) to capture ride-specific data from the external ride provider, including:

- Pickup and Drop-off DateTime (UTC), City, State, and Zip Code

- Distance (miles) and Duration (minutes)

- Ride Cost, Transaction Amount, Transaction DateTime, and Transaction Type

- Ride Type, Fare Type

- Scheduled Ride ID and Flex Ride ID

We are not storing street addresses — only city, state (using State/Country picklists), and zip code to keep the data PII-safe.

Our Questions

1. Is BenefitDisbursement the right object to store individual ride events from an external system, or would you recommend a different approach?
2. Are there any limitations of the BenefitDisbursement object we should be aware of when storing high-volume records from an external integration?
3. Has anyone used the Benefit Disbursement Field Set to surface ride- or service-specific custom fields, and are there any gotchas?
4. Any considerations we should keep in mind for reporting on ride utilization (rides used vs. rides allocated) using this model?

Any advice or experience with similar implementations would be greatly appreciated!

Thank you!