Frequently Asked Questions

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.

GridMate is built for anyone using Salesforce - from public sector teams to fast-moving commercial organizations. While it offers powerful tools for admins and developers, GridMate is especially geared toward empowering end users with intuitive, flexible, and productivity-driven experiences.

Whether you're a project manager updating records, a service rep navigating related lists, or a data analyst interacting with grids, GridMate helps streamline everyday tasks, reduce clicks, and unlock more value from your Salesforce investment.

Yes. GridMate has been a trusted Salesforce partner since 2019. Our solution is officially listed on the Salesforce AppExchange, where we’re proudly rated 5 stars across 100+ customer reviews.

You can explore GridMate’s features and customer testimonials here.

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.

GridMate is offered at a flat, all-inclusive rate that gives you access to the entire productivity suite - including all 30+ components.

• $11 per user/month when billed annually
• $14 per user/month when billed monthly

This pricing covers everything - no add-ons, feature gating, or hidden tiers.

For Non-Profits:

Eligible non-profit organizations receive 5 free licenses for life.

For Large Volume Needs:

We offer tailored pricing for:

• Organizations with a large number of users
• Experience Cloud login-based license models
• Multi-org Salesforce environments

Contact us to explore volume discounts or eligibility for non-profit licensing.

GridMate is actively maintained and regularly improved based on customer feedback and evolving platform standards. We release updates on a biannual basis, with targeted interim patches to address critical enhancements or fixes. Release notes are shared through our documentation portal to keep users informed of new features and changes.

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

Yes. GridMate has been successfully deployed on Salesforce Classic. See below:

Step-by-step guide available here.

Yes, GridMate has been successfully deployed on iPad. See below:

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:

Yes. The GridMate permission sets grant access to Apex classes, Visualforce pages, objects, and other components. When you first install the package and choose “Install for All Users,” these settings are automatically applied to existing users.

However, when new users are added later, you must manually assign the appropriate permission set. GridMate access is managed entirely through permissions, so assigning the permission set is highly recommended.

GridMate User

This is the base permission set required for any user who needs access to GridMate components (except User Grids). It includes object and field access, as well as Apex classes. Each GridMate user should have this permission.

GridMate Advanced User

This permission set is used to grant access to User Grids. Its purpose is for advanced users who require permission to create their own grids.

GridMate Admin

This permission set is used for Business Analysts to have access to the config wizard, inline configuration and SOQL Preview buttons. It's applicable only if they don't have access to the setup.

GridMate Cockpit User

The GridMate Cockpit User permission set allows users to manage all GridMate settings in one place - including grid-level field access, action controls, and component visibility. It grants access to the Cockpit tab and its features.

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.

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.

Yes. GridMate supports this functionality. You can define the recordId property using the syntax "{!recordId}".

Yes. GridMate supports archived data via admin-defined filters. Use the following JSON string to enable archived row visibility:

{
    "gmpkg__allRows": true
}

No. GridMate is a native Salesforce package. We do not store or process any data outside of Salesforce. All our components are metadata-driven and built on Salesforce APIs.

GridMate is designed with enterprise-grade security and compliance in mind. We are FedRAMP authorized, which means our solution meets the U.S. federal government’s rigorous standards for data security, access control, and operational transparency.

All GridMate components are built natively on Salesforce, ensuring that your data remains within your Salesforce environment. We do not store, process, or transmit data outside your org, and we align with best practices for secure development and deployment.

Yes. GridMate has been successfully deployed on Salesforce Classic. See below:

Step-by-step guide available here.

Yes, GridMate has been successfully deployed on iPad. See below:

Yes. GridMate supports inline editing for multiple record types simultaneously. Dependent picklists are respected as well.

Yes. GridMate supports dependent picklists, including dependent record type picklists.

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.

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.

Yes. GridMate supports this functionality. You can define the recordId property using the syntax "{!recordId}".

Yes. GridMate supports archived data via admin-defined filters. Use the following JSON string to enable archived row visibility:

{
    "gmpkg__allRows": true
}