> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/feature-documentation/designing-and-running/facilitation/grid-view.md).

# Grid View

Grid view shows several player Virtual Desktops side by side in one browser tab. Use it to **test what different players receive at the same time**, and to interact as each of them, while the exercise runs.

| Benefit                                                                                             | Feature                                                                                                                             |
| --------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| Check content reaches the right teams, positions, and roles without switching between player logins | <ul><li>One panel per player</li><li>Each panel is a live Virtual Desktop</li><li>Interact as any player from their panel</li></ul> |

### Opening Grid view

Grid view opens from its own URL, not from a tab in the Facilitator Dashboard:

`https://`**`<your-player-url>`**`.cm.cr/grid?p=`**`<space-number>`**`&num=`**`<number-of-panels>`**

<table><thead><tr><th width="170.11111450195312">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><code>p</code></td><td>Your space number (find this in the <code>Run exercise</code> window from your Editor)</td></tr><tr><td><code>num</code></td><td>How many player panels to show (e.g. how many different positions/teams you want to test)</td></tr></tbody></table>

### Logging players in

Each panel is a separate player login. Log a player into each panel to see the exercise from their point of view.

{% hint style="warning" %}
Players only receive content addressed to their **team, position, role, or Superteam**. Check the Teams table to make sure each panel's player is set up as they will be in the live exercise.
{% endhint %}

### Using Grid view

Each panel works like the player's own Virtual Desktop. You can open channels and reply, like, or post as that player. Anything you do in a panel counts as that player's activity and appears in the Facilitator Dashboard.

{% stepper %}
{% step %}

#### Access your Grid view URL

{% endstep %}

{% step %}

#### (Optional) Click and drag windows

Click and drag to resize and move player view panels to suit your preferences.

<figure><img src="https://3476309720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsNKxYbIPgfYmCR9EJgAu%2Fuploads%2FJw5NHgY9dM5qBwleNGG7%2Fgrid%20view.gif?alt=media&amp;token=27167af6-f6a9-4724-8397-3c8399280c79" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Log in to player views

Click-to-play or, if using preregistered participants, log in with player emails and passwords from the Teams table.

&#x20;Start exercise from your Facilitator Dashboard!

<figure><img src="https://3476309720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsNKxYbIPgfYmCR9EJgAu%2Fuploads%2FObBB08KEjoHL2U4KS91j%2Fgrid%20view%201.gif?alt=media&amp;token=b600b2c0-d7e5-45ab-ae96-8677d9b90cd0" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}


---

# 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://helpdocs.conducttr.com/feature-documentation/designing-and-running/facilitation/grid-view.md?ask=<question>&goal=<user_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.
