> For the complete documentation index, see [llms.txt](https://help.usejimo.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usejimo.com/docs/getting-started/your-workspace.md).

# Your workspace

Read what the guided setup prepared, correct what is wrong, and invite the people you will need.

Step 1 is already checked when you land on the Get Started page. This page is about reading what was set up for you, correcting what is wrong, and inviting the people you will need. Ten minutes.

**You will have at the end:** a workspace whose product URLs, environment, Space and theme are right, and your developer invited.

***

## What the setup prepared

Open **Get Started** in the sidebar and expand **1. Workspace Created**. Four blocks summarize what the guided setup did with the answers you gave.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FlMSzjtFBDQozSMb2KSaq%2Fgs-step1-workspace.png?alt=media&#x26;token=42e8bb14-0be4-4ae8-842d-92918563a3f5" alt="Get Started page, step 1 expanded"><figcaption></figcaption></figure>

| Block           | What it shows                                                                        | Check                                                                                                                                                                                                                               |
| --------------- | ------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Your product    | **Website** (your public site) and **App domain** (where your users log in)          | The App domain is the one your users see in the address bar once logged in, without `https://` or a path. It became your Production environment. Wrong domain: fix it in [Settings > Environments](/docs/settings/environments.md). |
| What Jimo knows | **Help docs** (the URL the Agent read) and **Knowledge** (how many pages it learned) | Only matters if you will use the Agent. If it read your marketing site instead of your help center, change the source in [Agent > Train > Knowledge](/docs/experiences/agent/knowledge.md).                                         |
| What Jimo built | A Space named **Onboarding** with the drafts generated for your goal                 | Open it: this is where Step 3 starts. 0 experiences means the product read failed (private app, no public site); you will build from scratch at Step 3, which is fine.                                                              |
| How it looks    | The default theme: colors, font, corner radius, picked from your site                | Edit it in [Settings > Themes](/docs/build/theme.md) before you build, so every draft inherits it.                                                                                                                                  |

{% hint style="warning" %}
**The most common mistake at this step: the domain.** An environment domain is `app.example.com`, nothing more. `https://app.example.com`, `www.app.example.com/login` or a domain with a query string never matches, and the symptom shows up only at Step 5 as "it does not show". See [Environments and domains](/docs/getting-started/your-workspace/environments-and-domains.md).
{% endhint %}

## Invite your team

{% stepper %}
{% step %}

### Open the Team settings

Go to [Settings > Team](/docs/settings/team-management.md) (`/settings/team`).
{% endstep %}

{% step %}

### Invite your developer

**Invite** your developer now, with a role that can see the Installation settings. They need it for Step 4.
{% endstep %}

{% step %}

### Invite whoever will publish

Invite anyone who will publish, with a role that has the publish permission. A Viewer can look, not build; some roles can build but not publish. See [Roles and permissions](/docs/getting-started/your-workspace/roles-and-permissions.md).
{% endstep %}
{% endstepper %}

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FFXfgHAslEVshmAXDYXWB%2Fsettings-team-members.png?alt=media&#x26;token=38818771-9cf0-4d49-803c-fd44c4db9ac1" alt="Settings, Team, Members tab"><figcaption></figcaption></figure>

## One project or several?

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2F97K5P648Cgv5nM4xAQRE%2Fn07-one-project-or-several.png?alt=media&#x26;token=aa2a1d4c-e2db-493e-bfb8-6c240500b7b5" alt="One project with two environments, or two projects with their own snippet"><figcaption></figcaption></figure>

A project is one snippet, one set of experiences, one changelog, one MAU count. Keep one project when your users move between products with the same login, or when a shared changelog is fine. Create a second project when two products need separate changelogs and separate experience lists, or when different teams must not see each other's work. Staging and production never need separate projects: that is what environments are for. Details in [Environments and domains](/docs/getting-started/your-workspace/environments-and-domains.md).

## Verify

* Settings > Environments lists your production domain, bare, with no scheme or path.
* Your developer appears in Settings > Team with an invitation sent.
* The Onboarding Space opens from the sidebar.

## Go further

* [Environments and domains](/docs/getting-started/your-workspace/environments-and-domains.md): what the Domains field accepts, staging first, one project or several.
* [Roles and permissions](/docs/getting-started/your-workspace/roles-and-permissions.md): who can build, publish, install.
* [Themes](/docs/build/theme.md), [Spaces](/docs/build/spaces.md), [Project management](/docs/settings/project-management.md).

**Next page:** [Step 2, Install the Chrome extension](/docs/getting-started/install-the-chrome-extension.md)