📝 Use this when a user still can’t access a feature after their role was updated.
✅ Step 1: Confirm Session Refresh
Why: Role-based permissions often require the user to start a new session to take effect. If the user hasn't logged out and back in, cached session data may still be active.
✅ Step 2: Check Feature Access for Role
Why: Not all roles automatically include access to every feature. It's common for features like dashboards or modules to be restricted even within elevated roles unless manually added.
✅ Step 3: Check Tab/Object Visibility
Why: The user’s role may have object-level access but still be restricted from viewing certain tabs, fields, or record types, especially in platforms like Salesforce or nCino.
✅ Step 4: Browser Cache & Incognito Test
Why: Browser caching can cause UI elements or permissions to appear out-of-date, even after role changes. Incognito mode bypasses this cache and helps isolate the issue.
✅ Step 5: Escalate if Issue Persists
Why: If all steps have been confirmed and the user still cannot access the feature, there may be a backend permission or sync issue that requires admin-level investigation.
Comments
0 comments
Please sign in to leave a comment.