What a “blank app” actually means in Salesforce
When you log in as a Platform User and see:
“Well, this is awkward. This app doesn’t have any navigation items, or you can’t access them.”
Salesforce is saying:
“I looked at the app’s nav items, checked your object + tab permissions, and you’re not allowed to see any of them.”
No error.
No warning.
Just… emptiness.That’s intentional.
Why this happens specifically with Platform Users
Platform licenses are object-restricted by design.
They:
- ❌ Don’t support Cases
- ❌ Don’t support many standard CRM objects
- ✅ Do support custom objects (within limits)
So if your app navigation includes things like:
- Cases
- Accounts
- Contacts
- Reports
- Dashboards
…and the user’s license/profile/permission set doesn’t allow access?
👉 Salesforce removes every single item from the nav bar
👉 Leaving the app “empty”
The Fix
Whenever a user sees a blank app, check in this exact order:
✅ 1. Does the User’s License support the object?
Ask first, always.
- Platform license?
- ❌ Cases
- ❌ Opportunities
- ❌ Leads
- ✅ Custom objects (like
Service Task__c)
If the license doesn’t support it — stop.
No permission set can fix that.
✅ 2. Is there a TAB for the object?
Objects don’t appear magically.
You must have:
- A Custom Object Tab
- Tab visibility set to:
- Default On (via profile or permission set)
You did this here — that was a key unlock.
✅ 3. Does the USER have object access?
Check via:
- Profile or
- Permission Set
Minimum required:
- Read access to the object
No object access = no nav item.
✅4. Is the object added to the APP navigation?
This is the step most people miss.
In App Manager → Edit App → Navigation Items:
- Add your custom object (Service Tasks)
- Save and refresh
If it’s not in the app, Salesforce can’t show it.
✅ 5. Is the Lightning Record Page activated?
For custom objects:
- Record page must be:
- Activated
- Assigned as Org Default or
- Assigned by App/Profile (if applicable)
Otherwise users can see the tab but hit weird dead ends.
How this ties to the Custom Permission solution
Once users could:
- See the app
- See the object
- Open records
I then layered Custom Permissions on top to control:
- Which Lightning record page they see
- What data is visible
- Which users get the “Field Operative” experience
So the blank app problem wasn’t separate — it was Step 0.
⭐ STAR
Situation
Platform Users logged into Salesforce but were presented with a blank app and no navigation items.
Task
Diagnose whether the issue was permissions, profiles, licensing, or app configuration — and restore access without breaking license constraints.
Action
Audited the user license, verified supported objects, created a custom object tab, added it to the app navigation, and ensured object access via permission sets.
Result
Platform Users gained access to a clean, role-appropriate app experience while remaining fully license-compliant.
A blank app in Salesforce is not a bug — it’s a signal that the user has no accessible navigation items under their current license and permissions.