Record Layout
Dynamic layouts. Seamless visibility.
Create elegant, flexible record views for any object - standard or custom. The Record Layout (LWC) component brings structure and style to related data, even for objects Salesforce’s UI API doesn’t fully support, like Events and Tasks.
Power up your layouts with precision.
Customize every detail. Control every view.
Build record layouts that adapt to your needs. Define sections, control field visibility, and group related information in a way that’s clear and purposeful. No more rigid layouts - just intuitive, streamlined views.
Style it your way.
Apply custom styling to sections, fields, and headers. Whether you're enhancing internal UX or elevating external community pages, make every record layout feel like it was made just for your users.
Slim it down. Keep it sharp.
Want a minimalist layout? Choose to hide section headers for a sleeker, more immersive display - perfect for embedded components or community-facing use cases.
Built for the details that matter.
Whether you're showcasing a contact’s full engagement history, displaying all details for an Event, or building a clean view for Task records, Record Layout (LWC) gives you the control Salesforce UI API lacks.
See the Record Layout
in action!
Make the leap from standard to standout.
Unlock the flexibility Salesforce layouts can’t match - especially for unsupported objects.
Frequently Asked Questions
Can I prevent my users from creating, editing, or deleting filters?
Yes. By default, GridMate provides a permission set called GridMate User to easily grant access to package components, including object settings, Apex classes, and more.
With this permission set assigned, users can create, edit, and delete end-user filters - provided this option is enabled on the grid.
However, in certain scenarios, admins may want to restrict these actions. Rather than duplicating and manually adjusting the permission set, we recommend using the Muted Permission Set feature in Salesforce.
1. Create a Permission Set Group that includes the GridMate User permission set.
2. Add a Muted Permission Set to that group by creating a new Muted Permission Set.
3. In the Muted Permission Set, mute Create/Update/Delete access for the DataGrid Preferences object.
4. Finally, remove all direct assignments of the GridMate User permission set from users. Instead, assign them the new Permission Set Group.
This approach ensures your users retain access to essential GridMate components while preventing them from modifying filter settings.
Please refer to Salesforce documentation for Muted Permissions.
Does GridMate support dependent picklists?
Yes. GridMate supports dependent picklists, including dependent record type picklists.
Are GridMate grids supported on the Salesforce Mobile App?
Absolutely! Here's what we recommend:
- Duplicate the existing grid in your Salesforce Org. This duplicated grid should be specifically configured for access by mobile users.
- Set a unique name that clearly identifies it as a mobile-friendly grid.
There are two key considerations when it comes to accessing grids on mobile devices:
Set the width for each column – This allows users to scroll horizontally.
Refer to column width specification here.
Set the height of the grid – This enables vertical scrolling.
Refer to the height specification here.
Note: We will be introducing a new component called ‘Mobile Grids’, which will be optimized specifically for mobile phones.
What is GridMate?
GridMate is a Salesforce ISV on the Salesforce AppExchange, offering 30+ Lightning components designed to boost adoption, utilization and productivity within Salesforce by enhancing its user experience and overcoming native limitations.
Rated 5 stars on AppExchange, GridMate is industry-agnostic and designed for a broad spectrum of use cases, empowering end users with the confidence and tools they need to excel in their day-to-day Salesforce tasks efficiently.
Should we grant a GridMate license to every user?
No, GridMate licenses should be granted only to relevant users. GridMate components can be combined with standard components using visibility conditions in the Lightning App Builder.
We recommend creating a custom permission set, assigning it to licensed users, and then using this permission to control component visibility in the Lightning App Builder. See below:
Got any more
questions?
