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
Does GridMate run on tablets?
Yes, GridMate has been successfully deployed on iPad. See below:
.webp)
How do I contact GridMate support?
You can reach out to us via email at support@gridmate.io.
For any technical assistance, please grant access to your Salesforce organization and share the following:
- The Salesforce Organization ID (Org ID)
- The page link(s) related to the issue
- The steps to reproduce the issue
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 archived data filtering?
Yes. GridMate supports archived data via admin-defined filters. Use the following JSON string to enable archived row visibility:
{
"gmpkg__allRows": true
}
Can the record Id be passed to a GridMate component on Experience Cloud?
Yes. GridMate supports this functionality. You can define the recordId property using the syntax "{!recordId}".
Got any more
questions?
