Object Timeline
See everything. Miss nothing.
Bring every record’s story into focus with a unified timeline that displays more than just activities. The Object Timeline component lets you view emails, calls, milestones, orders, and any related object - standard or custom - in a single, seamless view. Whether it’s embedded inline or expanded across a full page, Object Timeline turns scattered data into clear context.
Timelines reimagined. Context restored.
One timeline. 360° visibility.
Don’t settle for a limited activity feed. Go beyond tasks and emails to see every object tied to your process.
- View all Salesforce-supported activities like emails, tasks, events, and calls
- Add any custom or standard object to the timeline - no restrictions
- Display non-activity records like Project Milestones, Quotes, Sales Orders, and more
Context where you need it.
Timeline views aren’t just for detail pages anymore.
- Add Object Timeline inline within any Grid or Lightning page
- Instantly access a timeline view while inspecting or drilling into a record
- Give users the full picture - without needing to click away
Tailored to your process.
Every business is different. This component molds to your structure.
- Define which objects and record types appear
- Control field visibility and layout
- Create grouped or filtered views to suit different workflows
See the Object Timeline
in action!

Make the leap from standard to standout.
Unlock a complete timeline experience - no more blind spots, no more object limits.
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.
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.
How do partner rewards work?
Partners who refer or sell GridMate earn a predefined percentage of the deal value. It’s simple, transparent, and rewarding.
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}".
Is GridMate a managed package?
Yes. GridMate is a Salesforce-managed package, which means it’s securely versioned, upgradeable, and adheres to Salesforce’s best practices for packaging, deployment, and security. This ensures a clean upgrade path and minimizes risk across sandbox and production environments.
Got any more
questions?
