Have you started to learn about Salesforce, made your way through Trailhead and now look at this Superbadge?

Have you just managed all the other Superbadges which are now required before you tackle this one?

But do not quite know where and how to start?

Following Jeffrey Alhadeff YouTube Video about the Superbadge, I have drawn out UserStories and talk about some of the challenges! Sorry, you won’t find solutions here though!

What the Salesforce Security Superbadge is about

According to Trailhead, GenZ Capital security has to meet the OldGuard requirements and you as the Salesforce Admin are the go-to person!

Here is the Organisational Chart for GenZ:

Pay attention to the Organisational Chart, it is important for the setup of the GenZ Capital Users.

The Challenge as table:

	ORG wide	Executive	Inside Sales	Field Sales	Project Manager**
Login	PW reset every 90 days PW 8 characters include alpha and numeric characters	mobile access on demand no hour restriction	access via IP 0.0.0.0 between 8:00am and 6:00pm no mobile access	mobile access on demand no hour restriction	mobile access on demand name security property “Project Managers”
Accounts	access for anyone (if profile allows it)	View all	View, create, edit all (no delete)	read, edit all*
Opportunity	access to their own & manager	View all	View, create, edit all (no delete)*	read, create, and edit their own (but not delete)	view all if Type = “Existing Customer & Upgrade” and Stage = “Closed Won”
list view/folders		create / not create or manage for others	create, manage for them and others	create / not create, manage for others
reports/dashboards		create R&D, not folders	create, create & manage folders	create / but not create or manage folders

*do not use View all, Modify All

**do not use Profile to set record level permission, do not use Role for sharing records

GenZ Capital User Stories

I have started the habit of writing User Stories for the Superbadges and in general, for the Dev Orgs, I am creating. It helps to get into the right mindset and keep track of the tasks and keep an eye on the Acceptance criteria, especially if you set up your own Salesforce Dev Org. I will write more about User Stories [later here]