◆ Salesforce

Turn on or off feature permissions

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All Salesforce tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskEnable the new Opportunity split permission for the East sales team and remove the beta access…+
Enable the new Opportunity split permission for the East sales team and remove the beta access flag for the marketing integrations for Jenna Park and Marcus Reed. Turn on the feature only for users in the East sales role, verify that pricebook editing remains restricted, and report back with a list of everyone who gained or lost permissions by 2pm Tuesday.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I change feature permissions org-wide, make approval easy for the sales leadership —…+
Before I change feature permissions org-wide, make approval easy for the sales leadership — show which features will touch revenue fields, put the expected changes to dashboards and reports up front, and flag any feature toggles that could silently expose pricebook editing or commission data so they can decide quickly.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI toggled the feature permission for Opportunity splits for Marcus Reed and several sales…+
I flipped a feature flag and commission numbers disappeared from a report.
I toggled the feature permission for Opportunity splits for Marcus Reed and several sales reports stopped showing commission numbers. Marcus needs his reports for a month-end call and his director, Elena Voss, is asking why. I don't know whether the feature changed field-level visibility or broke a report calculation. What's the most likely cause and the fastest fix to restore report numbers for his call?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross many pilots we keep toggling features and then spending days undoing side effects on…+
We oscillate between enabling features for pilots and rolling them back for safety.
Across many pilots we keep toggling features and then spending days undoing side effects on reports and commissions. What habit should I change so feature rollouts stop creating firefights, who should own the readiness checklist, and what minimal test gives 80% coverage of likely problems before toggling for a pilot group?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Salesforce's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.