Skip to main content
Featured group

* Service Delivery (inc Hyperforce) *

A group dedicated to Salesforce Service Delivery (inc Infrastructure / Hyperforce / Performance / Availability etc). Expect topics such as Hyperforce, org migrations, instance refreshes, scheduled maintenance, security enhancements and feature retirement. Ask questions, find resources and get information with details, updates, best practices, and maintenance info. Although Support is your primary channel for assistance when you encounter a problem, error or serious issue, the Success Community is a valuable forum to get best practice advice and ask “how to” questions. --------------------------------------- Confidentiality Statement: http://bit.ly/11YD5E3 This group is maintained and moderated by a Salesforce employee. The content received in this group falls under the official Forward-Looking Statement: http://investor.salesforce.com/about-us/investor/forward-looking-statements/default.aspx Please also see our official Salesforce Customer Community Terms of Use.

The support staff for our Salesforce installation (Lightning) moved on to different work, and while we pursue hiring of a replacement, we are somewhat in the dark about user profiles. I've read through the basic guidance on the user access structure, i.e. Profiles, Roles, Permission Sets. However, we have a task that requires complex understanding of user permissions that we just don't have yet. 

 

We have a directive from our CEO to move a handful of users out of a profile called "Exec-Team", and we lack any guidance on how to intelligently decide which profile to move these users

to,

or whether to create new profiles.  

 

While the “Exec-Team” profile is by far our most populous, the bulk of

other

users are under one other sales-centered profile. The difficult fact is that we don’t know precisely what access these to-be-moved users would be gaining or losing. They serve a variety of roles under different departments. 

 

We want to be able to understand and fulfill business needs, while adhering to the least-privileged-access principal.  

 

We have a "standard" support level under our current contract, so have limited Salesforce support resources to draw from. Are we stuck with either waiting until we hire a Salesforce Admin expert, or else hiring an outside consultant? 

 

Thanks very much!

7 answers
  1. May 8, 7:42 PM

    RIP Perm comparator.  @Logan Boardman

    Im trying yours now and it looks great so far. 

     

    I would suggest taking a step back to catalogue generally who should be able to do and see what things in SF as a whole in your org and not do this piece meal.  And then drill in to edit/create the permissions for both object and system.

0/9000

Summer '26 Tech Updates

 

Product Innovation

  • New Features in Summer '26 Release

Release Updates

  • Enforcement and changes for Summer '26

Infrastructure Improvements

  • Instance Refresh Events and Resources

System Maintenance

  • Plan around your Preferred Maintenance Windows
  • Trust Notifications

Product & Feature Retirements

  • Retirement Monthly Newsletter
  • Upcoming Product & Feature Retirement list

Please download the attached PDF to view the presentation.

3 comments
0/9000

We are preparing for Hyperforce migration, and have previously implemented DMARC and DKIM for email communications (email to case and more).  

When the migration happens, particularly since they interact with our network settings, can I expect the existing configuration to carry over as-is?  Or will these keys/settings need to be recreated after migration?

2 answers
  1. Mar 25, 1:55 PM

    Hi Jayesh, it's been awhile, I do remember working with my network/infrastructure colleague to make changes, but not the details of exactly what we did.  I was able to go back in my email history and find the following as the guidance that was provided by SF (below).  I found a pdf doc as well (attached).  Hopeful that some of this helps!  FWIW, the timing of our migration (SB vs Prod) was a bit chaotic.  We got really short notice for  our Sandbox migration.  We did all of our prep for both SB and Prod at the same time in June '24 when we got the notice about SB, and it was lucky that we did because Prod got migrated in July  and I didn't get any advance warning.  Because our prep was already done I didn't even notice that it had happened until weeks later. So what I can say is that if you prepare well, migration is seamless.   

     

    A comprehensive list of preparation articles- "Salesforce Org Migrations overview"

    https://help.salesforce.com/s/articleView?id=000320503&type=1- "How to Prepare for an Org Migration" https://help.salesforce.com/s/articleView?id=000334938&type=1-

    "Read-Only Mode Overview"  

    https://help.salesforce.com/s/articleView?id=000334690&type=1- "Ensure you can receive email from the Salesforce application" https://help.salesforce.com/s/articleView?id=000355539&type=1- "Introducing Hyperforce - General Information & FAQ" https://help.salesforce.com/s/articleView?id=000356459&type=1- "Retain uninterrupted access to Salesforce services on Hyperforce" https://help.salesforce.com/s/articleView?id=000363860&type=1

     

     

    ----------------------------------------Domains are now a requirement for all orgs, it sounds like the customer created their MyDomain before it became mandatory and streamlined for all customers. If they have enhanced domain enabled, they will be fine. 

    From the enhanced domains article: 

    To update your Salesforce org's URLs to the latest standards, enable and deploy enhanced domains. With enhanced domains, all URLs across your org contain your company-specific My Domain name, including Experience Cloud sites and Salesforce Sites. Your URLs also remain stabilized when your org is moved to another Salesforce instance. 

     

    Best of luck with your migration!   

    Marissa

0/9000

Hi, is there a limit to the number of records soft deleted in the Recycle Bin per User?

https://developer.salesforce.com/docs/atlas.en-us.246.0.salesforce_app_limits_cheatsheet.meta/salesforce_app_limits_cheatsheet/salesforce_app_limits_platform_apicalls.htm suggests that yes, 5k per user license. But it's not mentioned anywhere else...

 

Established limitations:

  1. Org-storage limit: 25× your org's data storage allocation in MB
  2. Time Limit: up to 15 calendar days (can be extended by support to 30) unless an admin purged / hard deleted the records

The link suggests a third, per User limit. True or not?

 

Moreover, when an either limit is reached, "Salesforce automatically removes the oldest records, as long as they’ve been in the recycle bin for at least two hours." Can I infer that soft-deleted records don't run the risk of causing other records be purged from the Bin for 2 hours? Or does it merely suggest that the automated purging runs on a 2-hour schedule?

 

@Admin Tricks, @* Service Delivery (inc Hyperforce) *, @* Customer Success *

0/9000
3 answers
0/9000

I believe Hyperforce encrypts all the data at rest by default. If that is true, what additional advantage does Shield Platform Encryption bring if we are on Hyperforce?

7 answers
0/9000
1 answer
0/9000

In regards to the retirement of the default Salesforce client certificate (proxy.salesforce.com), will it be possible to generate a Self-Signed certificate greater than 1 year?

2 comments
0/9000

Spring '26 Tech Updates 

 

Product Innovation

  • New Features in Spring '26 Release

Release Updates

  • Enforcement and changes for Spring '26

Infrastructure Improvements

  •  Instance Refresh Events and Resources

System Maintenance

  • Plan around your Preferred Maintenance Windows
  • Trust Notifications 
  • Site Switches

Product and Feature Retirements

  • Retirement Monthly Digest
  • Upcoming Product and Feature Retirement List

Please download the attached PDF to view the presentation.

3 comments
0/9000

I cannot find this question answered explicitly, so want to make sure I don't steer my team wrong.  Is there any impact to Org ID when upgrading a production org to Hyperforce?

3 answers
0/9000