Record Access Roadmap (Ideas & comments)
Frequent Requests
If you’d like to share your thoughts, please vote and comment! We listen and do take your voting into consideration, even if it takes us (or Larry Tung) some time to respond.
Restriction Rules Enhancements (partition records by line of business)
Wouldn’t it be great if we could partition records by line of business?
Salesforce, please add support for Standard Objects:
The object owners will need to prioritize adding Restriction Rule support. If you don’t see your object listed, please create a new idea and at mention Larry Tung. I can update this document and also let the object owner know.
Also, could you make rules more configurable?
- IN operator
- cross object lookup aka spanning fields (one reference in the record criteria isn’t enough; what about the user criteria?)
What if you could partition queues (public groups and roles) similar to how you could handle record data?
Is disabling the hierarchy for standard objects critical to your business? If so, what objects? Or would you need to do this by record type?
Enhancements in configuring public groups and queues (Setup/Admin UI)
[Winter ’25] Description Field on Public Groups and Queues [Summer ’24 with summaries] Add "Where is it used ?" button for Public Group [Winter ’24] Show inactive user in public groups (I shared how to do this with SOQL and it is now available through a Custom Report Type)[Winter ’24] Who is in which queues? - You can do this with SOQL and also in a Custom Report Type (GroupMembership)
What about conditionally hiding fields?
What about making our lives easier when it comes to errors due to lack of access?
What about External users?
- Hopefully with restriction rules on standard objects, we could address filtering on existing sharing sets.
What’s another top request you hear?
- No plans to support formula due to performance considerations.
- now available through Account Share Custom Report Type for RowCause = Team or Manual.
[Winter ’24] Reporting on Queue membership