CRM configuration
Change fields, layouts, permissions and territories in CRM setup.
20 project-authored proposals · taxonomy v1.1 · 0 new benchmark runs. Verifiers and partial-credit rules below are designs, not executed results.
- Typical applications
- Salesforce Setup · HubSpot settings
- Class GUI-need label
G2· GUI-essential
Task proposals · 20
Expand to inspect the complete original wording and proposed checks. Original proposal text remains English in both interfaces.
R05.06.01.03-T01 Add a formula field visible only to marketing users
Original instruction
Salesforce developer org, Setup. On Opportunity create formula field 'Days to Close' (Number, 0 decimals) = CloseDate - TODAY(). Field-level security: visible (read-only) only to profile 'Marketing User'; hidden for all others. Add it to the 'Marketing Opportunity Layout' only.
- Platforms
web· Any OS (web)- Applications
- Salesforce Setup
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP08· App/system state- Conditions
licensed· Licensed pro app- Proposed difficulty
- 2 / 5
Proposed verifier
Grader retrieves metadata as admin: field formula, type, scale; FieldPermissions only for Marketing User (read); layout membership exactly one. API Enabled removed from the agent profile, so Metadata/Tooling API and sf CLI access are denied; Setup Audit Trail must show the change via Setup UI.
Proposed partial credit
40% field and formula; 40% FLS exact; 20% layout placement
R05.06.01.03-T02 Create a dropdown company property and show it in the record sidebar
Original instruction
HubSpot test portal, Settings > Properties. Create company property 'Contract Tier' (internal name contract_tier) in group 'Company information', type dropdown with options Bronze, Silver, Gold, Platinum (in that order), then add it to the company record's 'About this company' sidebar card as the third property.
- Platforms
web· Any OS (web)- Applications
- HubSpot settings
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & formsdrag· Drag & drop- Work product
WP08· App/system state- Conditions
- None declared
- Proposed difficulty
- 2 / 5
Proposed verifier
Property definition (admin API read): name, group, type enumeration, option order; sidebar card configuration lists it in position 3. No private-app or developer token issued; the account audit log must show the change from settings UI.
Proposed partial credit
50% property and options; 20% option order; 30% sidebar position
R05.06.01.03-T03 Determine whether a permission set lets users delete accounts
Original instruction
Salesforce developer org. User 'r.park' has profile 'Standard User' plus permission set 'Account Access' and permission set group 'Sales Ops'. Determine whether she can delete Account records (consider object permissions across profile, sets and muting permission sets). Write 'yes' or 'no' and the granting/muting component to output/answer.txt.
- Platforms
web· Any OS (web)- Applications
- Salesforce Setup
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicknav· Pan/zoom/scroll- Work product
WP12· Answer/decision- Conditions
licensed· Licensed pro app- Proposed difficulty
- 1 / 5
Proposed verifier
Answer equals key (a muting permission set in the group removes Delete, so the naive 'yes' is wrong); component named correctly. API Enabled is removed from the agent profile, so SOQL/Tooling queries are denied and permissions must be inspected in Setup.
Proposed partial credit
60% correct yes/no; 40% correct component cited
R05.06.01.03-T04 Add conditional components to an opportunity Lightning record page
Original instruction
Salesforce developer org, Lightning App Builder. Edit 'Opportunity Record Page': add a tab 'Deal Desk' containing the related list 'Competitors' and a Rich Text note; set component visibility so the tab shows only when Stage = Negotiation/Review and the user has custom permission 'Deal_Desk'. Activate as org default for desktop.
- Platforms
web· Any OS (web)- Applications
- Salesforce Lightning App Builder
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
drag· Drag & dropclick· Point & clicktype· Text & forms- Work product
WP08· App/system state- Conditions
licensed· Licensed pro app- Proposed difficulty
- 3 / 5
Proposed verifier
FlexiPage metadata: tab with the 2 components, visibility rule with both criteria (AND), activation assignment org default desktop. Grader renders the page as 2 users and checks tab presence. API Enabled removed from the agent profile, so Metadata/Tooling API and sf CLI access are denied; Setup Audit Trail must show the change via Setup UI.
Proposed partial credit
30% components placed; 40% visibility rule; 30% activation
R05.06.01.03-T05 Restructure a page layout with sections and required fields
Original instruction
Salesforce developer org. Clone 'Account Layout' to 'Partner Account Layout'; create sections 'Partner Profile' (2 columns) and 'Compliance' (1 column); drag in the 8 fields listed in input/partner_fields.txt in the given order; make 'Partner Tier' and 'NDA Signed' required; assign the layout to record type 'Partner' for all profiles.
- Platforms
web· Any OS (web)- Applications
- Salesforce Setup
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
drag· Drag & dropclick· Point & click- Work product
WP08· App/system state- Conditions
licensed· Licensed pro app- Proposed difficulty
- 3 / 5
Proposed verifier
Layout metadata: sections, column counts, field order, required behaviors equal key; layout assignments for record type Partner across profiles. API Enabled removed from the agent profile, so Metadata/Tooling API and sf CLI access are denied; Setup Audit Trail must show the change via Setup UI.
Proposed partial credit
40% sections and field order; 20% required fields; 40% layout assignments
R05.06.01.03-T06 Block closed-won opportunities without a signed contract
Original instruction
Salesforce developer org. Create validation rule 'Require_Signed_Contract' on Opportunity: error when Stage is Closed Won and Contract_Signed__c is false, except for record type 'Renewal' with Amount < 10,000. Error message 'Attach signed contract before Closed Won' on field Contract_Signed__c. Activate.
- Platforms
web· Any OS (web)- Applications
- Salesforce Setup
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP08· App/system state- Conditions
licensed· Licensed pro app- Proposed difficulty
- 3 / 5
Proposed verifier
Grader runs 4 DML test cases as admin (blocked, allowed exception, allowed signed, other stage) and checks outcomes and message location; rule active. API Enabled removed from the agent profile, so Metadata/Tooling API and sf CLI access are denied; Setup Audit Trail must show the change via Setup UI. Control pair: T13.
Proposed partial credit
60% test-case outcomes; 20% error message and field; 20% active
R05.06.01.03-T07 Grant sales-ops edit access with a permission set group and field security
Original instruction
Salesforce developer org. Create permission set 'Commission Admin' (edit on custom object Commission__c, read/edit FLS on Rate__c and Override__c, read-only on Paid__c), add it with existing set 'Report Builder' to a new permission set group 'Sales Ops Admins', and assign the group to the 4 users in input/users.txt.
- Platforms
web· Any OS (web)- Applications
- Salesforce Setup
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP08· App/system state- Conditions
licensed· Licensed pro apprisk· Irreversible/risky- Proposed difficulty
- 3 / 5
Proposed verifier
ObjectPermissions and FieldPermissions equal spec; group composition exact; PermissionSetAssignment for exactly 4 users. API Enabled removed from the agent profile, so Metadata/Tooling API and sf CLI access are denied; Setup Audit Trail must show the change via Setup UI.
Proposed partial credit
40% object and field permissions; 30% group composition; 30% assignments
R05.06.01.03-T08 Configure a new deal pipeline with stage probabilities and required properties
Original instruction
HubSpot test portal. Create deal pipeline 'Partner Deals' with stages Registered (10%), Qualified (25%), Joint Pitch (50%), Commit (80%), Closed Won, Closed Lost; require properties 'Partner company' at Qualified and 'Close date' plus 'Amount' at Commit; restrict moving backward from Commit.
- Platforms
web· Any OS (web)- Applications
- HubSpot settings
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & formsdrag· Drag & drop- Work product
WP08· App/system state- Conditions
- None declared
- Proposed difficulty
- 3 / 5
Proposed verifier
Pipeline definition: stage names, order, probabilities, closed flags; conditional stage properties per stage; backward-move restriction set. No private-app or developer token issued; the account audit log must show the change from settings UI.
Proposed partial credit
40% stages and probabilities; 40% required properties; 20% restriction
R05.06.01.03-T09 Add a choice column, form placement and a business rule in Dynamics 365
Original instruction
Power Apps maker portal for a Dynamics 365 Sales trial environment. In the Account table add choice column 'Risk Rating' (Low/Medium/High), place it on the main form in section 'Summary' below 'Industry', and create a business rule that locks 'Credit Limit' when Status Reason = Inactive. Publish all customizations.
- Platforms
web· Any OS (web)- Applications
- Dynamics 365 · Power Apps
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clickdrag· Drag & droptype· Text & forms- Work product
WP08· App/system state- Conditions
licensed· Licensed pro app- Proposed difficulty
- 3 / 5
Proposed verifier
Solution export (admin): column and options; FormXml position; business rule logic; published. Grader opens an inactive account form and checks field lock. No app registration or pac CLI auth is issued, Conditional Access admits the agent only via the sandbox browser, and solution import is denied; changes must appear as maker-portal edits in solution history.
Proposed partial credit
30% column; 30% form placement; 30% business rule behavior; 10% published
R05.06.01.03-T10 Make opportunities private and share enterprise deals by criteria
Original instruction
Salesforce developer org (sandbox data). Set Opportunity org-wide default to Private (internal), keep grant-access-using-hierarchies, then create a criteria-based sharing rule giving public group 'Exec Viewers' read-only access to opportunities where Segment__c = Enterprise. Do not change other objects' defaults.
- Platforms
web· Any OS (web)- Applications
- Salesforce Setup
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP08· App/system state- Conditions
licensed· Licensed pro apprisk· Irreversible/risky- Proposed difficulty
- 3 / 5
Proposed verifier
Org-wide default for Opportunity = Private; sharing rule criteria, group and access level exact; other OWDs unchanged; grader checks record visibility as 2 test users. API Enabled removed from the agent profile, so Metadata/Tooling API and sf CLI access are denied; Setup Audit Trail must show the change via Setup UI.
Proposed partial credit
30% OWD; 40% sharing rule; 30% visibility tests and no collateral changes
R05.06.01.03-T11 Create a team with restricted permissions and assign users in HubSpot
Original instruction
HubSpot test portal, Users & Teams. Create team 'EMEA Sales' with the 5 users in input/emea_users.txt; give them a permission set 'EMEA Rep' that can view and edit only deals owned by them or their team, cannot export, and cannot delete contacts. Do not change any other user's permissions.
- Platforms
web· Any OS (web)- Applications
- HubSpot settings
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP08· App/system state- Conditions
risk· Irreversible/risky- Proposed difficulty
- 3 / 5
Proposed verifier
Team membership exact; permission set definition matches; 5 users assigned; other users' permissions unchanged (diff). No private-app or developer token issued; the account audit log must show the change from settings UI.
Proposed partial credit
30% team; 50% permission settings; 20% no collateral changes
R05.06.01.03-T12 Customize forms and add an automated action with Odoo Studio
Original instruction
Odoo 17 Enterprise with Studio. On CRM opportunities add a selection field 'Deal Source' (Partner, Inbound, Outbound, Event) and a related field showing the customer's country; place both on the form after Expected Revenue and in the list view; add an automated action: when Deal Source = Partner, add follower 'Partner Manager' user.
- Platforms
web· Any OS (web)- Applications
- Odoo Studio
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clickdrag· Drag & droptype· Text & forms- Work product
WP08· App/system state- Conditions
- None declared
- Proposed difficulty
- 4 / 5
Proposed verifier
ir_model_fields x_studio_* with types; view arch positions; base_automation record with trigger/domain/action; grader creates a Partner deal and checks follower. XML-RPC is blocked for the agent and module import is disabled; customizations must be Studio-generated (studio_customization ir_model_data).
Proposed partial credit
30% fields; 30% view placement; 40% automation behavior
R05.06.01.03-T13 Deploy the same validation rule as metadata (control pair of T06)
Original instruction
Control pair of T06. Separate developer org with an API-enabled user (sf CLI authenticated). Write the ValidationRule metadata for the same logic and message and deploy it active.
- Platforms
lin· Linuxmac· macOSwin· Windows- Applications
- Salesforce CLI · VS Code
- Interfaces
term· Terminalapi· API/SDK- GUI need · task setting
CL· CLI-sufficient- GUI need · ordinary access
AP· API-sufficient- Interaction primitives
code· Code & commands- Work product
WP06· Code/engineering- Conditions
licensed· Licensed pro app- Proposed difficulty
- 3 / 5
Proposed verifier
Same 4 DML test cases as T06; compared to T06 to measure the GUI penalty.
Proposed partial credit
60% test outcomes; 20% message/field; 20% active
R05.06.01.03-T14 Build and activate a territory model with assignment rules
Original instruction
Salesforce developer org with Enterprise Territory Management enabled. Create model 'FY27', territory type 'Geo', territories West, Central, East under a 'North America' parent, account assignment rules on Billing State (from input/territory_states.csv), run the rules, assign territory users, and activate the model.
- Platforms
web· Any OS (web)- Applications
- Salesforce Setup
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP08· App/system state- Conditions
licensed· Licensed pro apprisk· Irreversible/risky- Proposed difficulty
- 4 / 5
Proposed verifier
Territory2Model active; hierarchy and rules exact; ObjectTerritory2Association for accounts equals key; UserTerritory2Association per spec. API Enabled removed from the agent profile, so Metadata/Tooling API and sf CLI access are denied; Setup Audit Trail must show the change via Setup UI.
Proposed partial credit
25% hierarchy; 35% rules; 25% account assignments; 15% activation and users
R05.06.01.03-T15 Add a record type with its own picklist values and sales process
Original instruction
Salesforce developer org. Create Opportunity sales process 'Partner Sales' with stages Registered, Qualified, Joint Pitch, Closed Won, Closed Lost; record type 'Partner Deal' using it, with Lead Source values limited to Partner Referral and Event, default Partner Referral; enable it for profiles Partner Manager and System Administrator only.
- Platforms
web· Any OS (web)- Applications
- Salesforce Setup
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP08· App/system state- Conditions
licensed· Licensed pro app- Proposed difficulty
- 4 / 5
Proposed verifier
BusinessProcess values; RecordType picklist value sets and default; profile record-type visibility exact. API Enabled removed from the agent profile, so Metadata/Tooling API and sf CLI access are denied; Setup Audit Trail must show the change via Setup UI.
Proposed partial credit
30% sales process; 40% record-type picklists; 30% profile visibility
R05.06.01.03-T16 Migrate an account page to Dynamic Forms with visibility rules
Original instruction
Salesforce developer org. Upgrade 'Account Record Page' to Dynamic Forms: create field sections 'Basics', 'Financials', 'Partner'; Financials visible only when AnnualRevenue > 0 and the user has profile 'Finance'; Partner section visible only for record type Partner; remove the legacy Record Detail component. Activate for the Sales app.
- Platforms
web· Any OS (web)- Applications
- Salesforce Lightning App Builder
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
drag· Drag & dropclick· Point & clicktype· Text & forms- Work product
WP08· App/system state- Conditions
licensed· Licensed pro app- Proposed difficulty
- 4 / 5
Proposed verifier
FlexiPage: field sections and fields per input/sections.txt, visibility rules exact, no Record Detail component, app activation. Grader renders as 3 users/records and checks visible fields. API Enabled removed from the agent profile, so Metadata/Tooling API and sf CLI access are denied; Setup Audit Trail must show the change via Setup UI.
Proposed partial credit
30% sections and fields; 40% visibility rules; 30% activation and legacy removal
R05.06.01.03-T17 Design a lead-qualification blueprint with mandatory transitions in Zoho CRM
Original instruction
Zoho CRM trial, Blueprint. For Leads, build blueprint 'Qualification' on field Lead Status: New -> Contacted (requires Last Contact Date) -> Qualified (requires Budget and Timeline, owner only) -> Converted; Disqualified allowed from any state with mandatory reason; publish and apply to criteria Lead Source != Partner.
- Platforms
web· Any OS (web)- Applications
- Zoho CRM
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
drag· Drag & dropclick· Point & clicktype· Text & forms- Work product
WP08· App/system state- Conditions
- None declared
- Proposed difficulty
- 4 / 5
Proposed verifier
Blueprint definition read by admin: states, transitions, required fields, who-can-perform, criteria; grader executes transitions on test leads and checks enforcement. No Zoho CRM API OAuth client is issued to the agent; the blueprint must be built in the Blueprint editor (audit log shows its web session).
Proposed partial credit
30% states/transitions; 40% transition requirements enforced; 30% criteria and publish
R05.06.01.03-T18 Implement a role-and-sharing access matrix and prove it with test users
Original instruction
Salesforce developer org. input/access_matrix.xlsx defines who can read/edit Accounts, Opportunities and the custom object Commission__c across 5 roles and 3 profiles (incl. field-level rules). Build the role hierarchy, OWDs, sharing rules, permission sets and FLS so that every matrix cell holds; do not grant Modify All Data.
- Platforms
web· Any OS (web)- Applications
- Salesforce Setup · Excel
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP08· App/system state- Conditions
licensed· Licensed pro applong· Long-horizonrisk· Irreversible/risky- Proposed difficulty
- 5 / 5
Proposed verifier
Grader logs in as 15 test users and checks CRUD and FLS for each matrix cell (90 checks); no permission set or profile grants Modify/View All Data. API Enabled removed from the agent profile, so Metadata/Tooling API and sf CLI access are denied; Setup Audit Trail must show the change via Setup UI.
Proposed partial credit
70% matrix cells pass (proportional); 15% no over-privileged grants; 15% hierarchy correct
R05.06.01.03-T19 Configure a custom object with associations, pipeline and record layout
Original instruction
HubSpot test portal (Enterprise trial). Create custom object 'Subscription' with properties (plan, MRR, start, renewal date, status), labeled associations to Company ('Billing account') and Deal ('Originating deal'), a pipeline 'Subscription lifecycle' with 4 stages, and a record page layout with MRR and renewal date in the highlights card.
- Platforms
web· Any OS (web)- Applications
- HubSpot settings
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & formsdrag· Drag & drop- Work product
WP08· App/system state- Conditions
long· Long-horizon- Proposed difficulty
- 5 / 5
Proposed verifier
Schema read by admin: object, properties and types, association labels, pipeline stages, record customization config equal key; grader creates a test record and checks associations work. No private-app or developer token issued; the account audit log must show the change from settings UI.
Proposed partial credit
30% object and properties; 25% associations; 25% pipeline; 20% layout
R05.06.01.03-T20 Build a model-driven app with a table, views and a business process flow
Original instruction
Power Apps maker portal (Dynamics 365 trial). Create table 'Site Survey' (columns per input/survey_columns.xlsx, lookup to Account), main form and 2 views, a business process flow 'Survey to Install' with stages Schedule, Survey, Approve, Install and required steps, a security role 'Surveyor' (user-level CRUD), and model-driven app 'Field Ops' including them.
- Platforms
web· Any OS (web)- Applications
- Power Apps · Dynamics 365
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clickdrag· Drag & droptype· Text & forms- Work product
WP06· Code/engineering- Conditions
licensed· Licensed pro applong· Long-horizon- Proposed difficulty
- 5 / 5
Proposed verifier
Solution export: table/columns, forms, views, BPF stages and required steps, role privileges, app sitemap equal key; grader runs the BPF as a test user. No app registration or pac CLI auth is issued, Conditional Access admits the agent only via the sandbox browser, and solution import is denied; changes must appear as maker-portal edits in solution history.
Proposed partial credit
25% table and columns; 20% form/views; 30% BPF; 25% security role and app
Mapped research references
Existing benchmark-to-class links from the research catalog. They are not record-level annotations, executions or product endorsements.