> For the complete documentation index, see [llms.txt](https://boza.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boza.gitbook.io/docs/getting-started/demo-workspace.md).
# Exploring the Demo Workspace
When you first sign in to Boza, your workspace opens in **demo mode** — a fully interactive sandbox pre-filled with realistic sample data. It lets you explore every part of the platform and see what your own SaaS landscape will look like, before connecting any of your real tools.
The demo workspace is clearly marked and contains sample data.
***
## What Demo Mode Is
Demo mode is a safe place to learn Boza:
* Every page — Dashboard, Applications, Users, Analysis, Renewals, and more — is populated with **sample applications, users, costs, and subscriptions**.
* Nothing you click affects real systems. There are no real accounts, invoices, or integrations behind the data.
* A **welcome message** and a short **guided tour** point out the main areas when you arrive. You can replay or skip the tour at any time.
A banner indicates that you're in demo mode so you always know the data isn't yet your own.
{% hint style="info" %}
Demo mode is the best way to evaluate Boza. Browse the [Dashboard](/docs/platform/dashboard.md), open an [application's detail page](/docs/inventory/applications/app-detail.md), and try the [Analysis](/docs/platform/analysis.md) charts to get a feel for the platform with zero setup.
{% endhint %}
***
## Going Live
When you're ready to use Boza for real, connect your environment. From the workspace, start the **go-live** step and connect your identity provider — **Google Workspace** or **Microsoft Entra ID**.
Connecting your identity provider does two things:
1. Switches your workspace from demo to **live**.
2. **Clears the sample demo data**, keeping only your administrator account and the identity-provider connection. Your real users and applications then begin to sync in.
{% hint style="warning" %}
Going live **permanently deletes the demo data** — this cannot be undone. That's expected: the sample data is only there to help you explore. Once you connect your identity provider, your workspace starts filling with your organization's real data instead.
{% endhint %}
***
## After You Go Live
With your identity provider connected, continue the full setup — collaboration, finance, and the browser extension — in [Setup & Configuration](/docs/getting-started/setup-configuration.md). Use the [Go-Live Checklist](/docs/getting-started/go-live-checklist.md) to validate the first synchronization and pilot rollout. To authorize Boza in your IdP first, see [Whitelist Boza in Your Identity Provider](/docs/getting-started/whitelist-boza.md).
## Need Help?
If you have questions while evaluating Boza, contact us at ****.
---
# 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://boza.gitbook.io/docs/getting-started/demo-workspace.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.
