Salesforce Administration
Allied Kicks
ALLIED KICKS:
SALESFORCE ADMIN
PROJECT
RECORD ACCESS, LOGIN SECURITY, AND SALES TEAM SETUP
P R E S E N T E D
B Y
B E N J A M I N
O P A L E Y E
01
Allied Kicks
INTRODUCTION
Context: Allied Kicks prioritizes
data security & visibility.
Objective: Onboard The Closer
Crew sales team with correct
security and permissions
while improving data access.
Learn More
02
Allied Kicks
PROFILES & PERMISSION SETS DEMONSTRATION
Closer Crew Profile (Sales Team)
Defines baseline access.
Sales team cannot delete records, this protects data
integrity.
Ola Louis & Tanya Stone – Permission Sets & Groups
→
Permission Set: Grants Ola Louis extra access
delete outdated records, build reports, create
dashboards
Permission Set Group: Bundles permissions for Tanya Stone, with the option to mute specific
rights (e.g., remove delete while keeping reporting)
Provides flexibility without changing the base profile
03
Allied Kicks
LOGIN SECURITY
CONTROLS
Requirement: Closer Crew only login
9–5, Mon–Fri, from HQ, no MFA
inside HQ.
Solution:
Login Hours (9–5 weekdays).
Login IP Ranges (HQ IPs).
Network Access (HQ trusted).
Learn More
04
Allied Kicks
01
→
Login Hours screenshot
Allowed hours for
Closer Crew
IP Ranges screenshot
Restricted to HQ
→
02
Network Access screenshot
Trusted network, no MFA
→ Caption:
05
Allied Kicks
MULTI-CURRENCY SETUP
Sales team handles EMEA
customers, so
transactions must support
multiple currencies.
Solution:
Enabled MultiCurrency in
Salesforce.
Added relevant
currencies: EUR, GBP,
ZAR, etc.
Opportunity records
now track currency
per deal.
06
Allied Kicks
SECURING OPPORTUNITIES & CASES
Problem:
All users could see
every Opportunity
and Case in the org.
Data exposure risk
and lack of
confidentiality.
Solution:
Set OrganizationWide Defaults (OWD)
for Opportunities &
Cases to Private.
Used Role Hierarchy
so managers can still
view subordinates’
records.
07
Allied Kicks
SHARING CLOSED OPPORTUNITIES
WITH ACCOUNTS RECEIVABLE
Problem:
Accounts Receivable
team couldn’t access
Closed Opportunities.
Blocked them from
processing invoices
for customers.
Solution:
Created a Sharing
Rule to grant Accounts
Receivable read-only
access to Closed
Opportunities.
Ensured only this
team has access,
without exposing
sensitive sales data to
others.
08
Allied Kicks
COLLABORATION WITH OPPORTUNITY TEAMS &
SECURING SENSITIVE FIELDS
Problem:
Some Sales Reps needed support from other
teams to process Accounts & Opportunities.
But all users could see the Amount field on
Opportunities, which is sensitive data.
Solution:
Enabled Opportunity Teams: record owners
can share specific Opportunities with additional
team members for collaboration.
Applied Field-Level Security: restricted the
Amount field so only Closer Crew team
members can view it.
09
Allied Kicks
Flexible record-level collaboration without opening up all data.
Sensitive fields protected, visible only to the right team.
Opportunity Teams = collaboration. Field-Level Security = protection.
10
Allied Kicks
FIXING TASK VISIBILITY
Problem:
All Sales Reps could see
every task on a record, even
when it wasn’t assigned to
them.
Created confusion and risk
of unnecessary access.
Solution:
In Sharing Settings, set
Activities = Private.
Ensures reps only see their
own tasks.
Role Hierarchy still allows
managers to view their
subordinates’ tasks.
11
Allied Kicks
THANK
YOU
12