🏢
Company
: Uber Technologies Inc.
📍
Context
Uber is running its global Salesforce org for Sales, Support, and Driver Onboarding. Due to rapid expansion and poor security practices, sensitive data is being overexposed across departments. There are growing concerns from leadership about GDPR violations, internal data leaks, and incorrect data access.
An internal audit has flagged major security issues, and you’ve been brought in as the Salesforce Admin to clean it up.
⚠️
Business Problems
:
Organizational-Level Security: Employees in India are accessing the system outside approved business hours. Sales reps are using weak passwords and logging in from unapproved devices. Contractors in Africa are accessing parts of the system meant for full-time staff.
The Support team can view and edit Sales Opportunities. New Onboarding Agents can create new Lead records but shouldn’t be allowed to delete them. Operations users are complaining they can’t see the Vehicle object even though it’s part of their job.
Driver license numbers and payout bank account fields are visible to interns. Marketing users are unable to view the “Lead Source” field on Leads. Finance fields like “Projected Revenue” are editable by junior Sales Reps.
All Case records are visible to everyone in Customer Support globally. Drivers onboarded in Kenya can see driver records in the UK via their portal. Regional Managers want access to all records from their teams only, not others.
✅Your Task
You’ve been given full access to fix the entire security model. For each problem listed above:
- 👀 Identify the level of security involved (Org/Object/Field/Record).
- 🧠 Explain what tools or configurations you’d use to solve the problem.
- 🛠 Mention any setup you’d create – roles, profiles, permission sets, sharing rules, login hours, etc.
- 🔐 Show how you would balance security with user productivity.
💪Bonus Challenge
Uber wants to track and restrict who changes security settings going forward.
👉 How would you implement this in Salesforce?