> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/command/getting-started/first-steps.md).
# First Steps
A fifteen-minute first session in YouDesign Command, from signing in to building, sharing and asking about your first piece of content.
This page walks you through your first session in about fifteen minutes. By the end you will have picked a persona, taken the guided demo, created and filled your first piece of content, shared it, and asked the assistant a question. Each step links to the reference page if you want more detail.
## What you need
| You need | Why |
| ---------------------------------------------------- | ------------------------------------------------------------------------ |
| A ServiceNow account on your organisation's instance | Command runs inside ServiceNow and uses your normal sign-in. |
| The Command link from your administrator | It opens the portal directly. |
| At least one persona assigned to you | It decides what you can create. Ask your administrator if you have none. |
New terms are explained in [Key concepts](/command/getting-started/getting-started.md#key-concepts).
## 1. Open Command
1. Open the link your administrator gave you.
2. If you are not signed in to ServiceNow yet, sign in as usual.
3. Wait for the loading screen to finish. You land on **Home**.
Home shows your tasks, the records you own, a box to ask a question, and your recent work. See [Home](/command/the-portal/portal.md#home).
Home
## 2. Pick your persona
1. Click your **avatar** at the right end of the top bar.
2. Under **Working as**, click the persona that matches your role.
3. Click outside the menu to close it.
Switching persona later never moves or hides your saved content. See [Personas](/command/the-portal/personas.md).
## 3. Take the guided demo
The demo builds example content in front of you: a SWOT, a Gravity Map, a TIME Analysis and an executive dashboard. Where your instance has business applications with TIME scores, it uses them.
1. Click **Command Dialog** on the right edge of the screen. On a phone, use the assistant button in the top bar.
2. Type `give me a demo` and press **Enter**.
3. Click **Next** to move through the steps.
4. Press **Esc** at any time to leave.
{% hint style="info" %}
Nothing from the demo is saved. Its tabs close when you leave, and nothing is written to My Space.
{% endhint %}
## 4. Create a folder
1. Click **My Space** in the activity rail.
2. Click **Add content** (the **+**) in the panel header and choose **New folder**.
3. Type a name, for example `My first analysis`, and press **Enter**.
My Space
## 5. Create your first Table
1. Open the new folder's **⋯** menu and choose **Add Table**.
2. Type `Business applications` as the name and press **Enter**.
3. The Table opens in a new tab. It says **This table is empty**.
New content is saved to My Space automatically. Every other type is created the same way; see [Content types](/command/the-portal/content-types.md).
The Create menu lists every type you can create
## 6. Put records into it
1. Click **Data Hub** at the bottom of the activity rail.
2. Click **Select table**, type `Business Application` and pick it.
3. Drag a few rows from **Current state** onto your Table. To add the whole list, drag the **Current state** header.
4. Close the Data Hub with **Close Data Hub**, or leave it open while you work.
5. Try **Fields** to add columns, the **Filters** funnel to narrow rows, and a column header to sort.
## 7. Share it
1. Click **Share** in the content header.
2. Choose **People** or **Groups**, then **Viewer** or **Editor**.
3. Search for the person or group, add them, and click **Share**.
The person gets a notification. See [My Space and sharing](/command/the-portal/my-space.md) for links, folders and access rules.
## 8. Ask the assistant a question
1. Open the **Command Dialog**. The chip above the message box shows the item you are looking at, so you can ask about it directly.
2. Try one of these:
| Ask | You get |
| -------------------------------------------- | --------------------------------------- |
| `what are we looking at?` | A summary of the open content. |
| `which applications should we decommission?` | A ranked list of retirement candidates. |
| `what depends on ?` | A dependency map of that application. |
| `create a roadmap` | A new Roadmap, opened in a tab. |
3. Click the chips under an answer to follow up, for example **Show these as a TIME Analysis**.
When the assistant proposes to create something larger, such as a dashboard, it shows a preview first. Click **Yes, create it** or **Cancel**. To start a fresh conversation, click **Reset thread**. More requests are listed in [Command Dialog](/command/features/command-dialog.md).
## 9. Tidy up your tabs
1. Close a tab with its **×**. A message offers **Undo**.
2. Click **All tabs**, or press **Ctrl+K** (**⌘+K** on a Mac), to search tabs, reopen **Recently closed** ones, or close tabs **Not used in 7 days**.
## What next?
* Work through a real question in [Use cases](/command/getting-started/use-cases.md).
* See what else Command can do in the [Feature map](/command/getting-started/features.md).
* Stuck? Try [FAQ and troubleshooting](/command/getting-started/faq.md).
---
# 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.ins-pi.com/command/getting-started/first-steps.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.
