> For the complete documentation index, see [llms.txt](https://docs.gridmate.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gridmate.io/advanced-guides/user-grid/user-grid-deployment-process.md). # User Grid - Deployment Process Move User Grids between orgs with the Admin Cockpit or the SF CLI Plugin. GridMate offers two deployment options for User Grids: a graphical interface through the **Admin Cockpit** and [**SF CLI Plugin**](/tools/sf-cli-plugin.md). The scenario in this tutorial is to create Accounts and Contacts User Grids and move them from one org to another. User Grids exported in Salesforce metadata like format (JSON), can be easily modified using popular tools like VS Code before importing them back. ## Prerequisites ### Enable GridMate Advanced User {% stepper %} {% step %} #### Find the user Go to setup, and on the quick find Box search for Users. {% endstep %} {% step %} #### Open the user Click on the desired **Full Name.** {% endstep %} {% step %} #### Open the permission set assignments Click on Permission Set Assignments.

{% endstep %} {% step %} #### Edit the assignments Click on edit assignments.

{% endstep %} {% step %} #### Enable the permission set Enable **GridMate Advanced User**.

{% endstep %} {% endstepper %} ### Enable GridMate Cockpit User {% stepper %} {% step %} #### Find the permission set Go to setup, and on the quick find Box search for Permission Sets. {% endstep %} {% step %} #### Open the permission set Click on the **GridMate Cockpit User**.

{% endstep %} {% step %} #### Manage assignments Click **Manage Assignments**.

{% endstep %} {% step %} #### Assign the user Ensure the existence of desired user, if not, click **Add Assignment** to add it.

{% endstep %} {% endstepper %} ### SF CLI Plugin Setup {% stepper %} {% step %} #### Clone the repository Clone the repository.

``` git clone https://github.com/GridMate/gridmate-sf-plugin ``` {% endstep %} {% step %} #### Install npm modules Go to the plugin directory and Install npm modules.

``` npm install ``` {% endstep %} {% step %} #### Link the plugin Link the plugin to your cli installation.

``` sf plugins link . ``` {% endstep %} {% endstepper %} ## User Grids Setup We are now ready to start using the **GridMate User Grid** to create **Accounts** and **Contacts** Grids. ### Accounts User Grid * On the App Launcher search for **GM - User Grids**.

* Click New.

* Create Accounts User Grid: * Object Name: **Account** * List View: **All Accounts** * Grid Name: **Accounts**

### Contacts User Grid * Create Contacts User Grid: * Object Name: **Contact** * List View: **All Contacts** * Grid Name: **Contacts**

### Inline Component Setup * Go to **Config Wiz** on the **Accounts** User Grid.

* Select the **inline Components** tab. * User Grid : **Contacts**. * Condition : ```json { "and": [ { "AccountId": { "operator": "=", "value": "$recordId" } } ] } ```

## User Grids Deployment ### Deployment Using **Admin Cockpit.** The Accounts and Contacts User Grids are created and the inline component is also configured, we can start the Deployment using **Admin Cockpit**. #### User Grids Export * On the App Launcher search for the **GM - Admin Cockpit**.

* Select the **User Grid Maintenance.** * Select the **Accounts** and **Contacts** User Grids. * Click **Export** to export them.

* Open the **Accounts** User Grid using **Visual Studio Code** for example:

* Change the Owner **Username** to match the target org.

* Open the **Contacts** User Grid using **Visual Studio Code**.

* Change the Owner **Username** to match the target org.

#### User Grids Import * Moving to the target org (Demo 13 in our example). * Import the **Accounts** and **Contacts** User Grids using the **GM - Admin Cockpit**

* First import the **Contacts** User Grid. Inline grids should be always imported first to be able to link them when parent grids are imported.

* Second import the Account User Grid.

### Deployment Using CLI Plugin After completing the [SF CLI Plugin Setup](#sf-cli-plugin-setup), we can now **Export/import** the User Grids. #### User Grids Export * Export the User Grid Using [SF Cli Plugin](/tools/sf-cli-plugin.md)

``` sf gmpkg usergrid export -o gmpkg-demo10 --api-version=58.0 -d "./usergrids" -n "Contact_nr9ma,Account_kozsu" ``` #### User Grids Import * Change the Owner of the User Grids as explained in [Deployment Using Admin Cockpit](#deployment-using-admin-cockpit) * Import the **Contacts** User Grid Using [SF Cli Plugin](/tools/sf-cli-plugin.md)

``` sf gmpkg usergrid import -o demoOrg13 --api-version=58.0 -f "./usergrids/Contact_nr9ma.json" ``` * Import the Account User Grid Using [SF Cli Plugin](/tools/sf-cli-plugin.md)

``` sf gmpkg usergrid import -o demoOrg13 --api-version=58.0 -f "./usergrids/Account_kozsu.json" ``` ## Final Result Using either the **Admin Cockpit** or the **SF CLI Plugin** to obtain the desired results, on our target org (**Demo** **13**), locate the **Accounts** User Grid and **Contacts** Grid as an **inline component**.

## Next steps


Grid - Admin Cockpit	Maintain User Grids and secure field and action access in the GridMate Cockpit.	Grid - Admin Cockpit
SF Cli Plugin	Export and import User Grids with the GridMate sf plugin.	SF Cli Plugin
User Grid	Create and configure your own grids from the Config Wiz.	User Grid

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.gridmate.io/advanced-guides/user-grid/user-grid-deployment-process.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.