> For the complete documentation index, see [llms.txt](https://mozarkdocs.gitbook.io/appx_documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mozarkdocs.gitbook.io/appx_documentation/test-infrastructure-documentation/getting-started/create-your-first-workflow.md).

# Create your first workflow

## Getting Started

Use this page to access the portal, sign in, and select the appropriate working context before your first test.

### Prerequisites

Before you begin, make sure you have:

* An invitation email from your organization's platform administrator, or an account already created for you by your administrator.
* Access to an email inbox that can receive verification codes, if multi-factor authentication is enabled.
* Membership in at least one organization, app, and project in the Mozark Admin Control Panel.
* A modern Chromium-based desktop browser:
  * Google Chrome 110+
  * Microsoft Edge 110+
* Safari and Firefox support is limited for live device streaming.
* A stable internet connection. Live session streaming uses WebSocket connections and works best with low latency.

### Logging in

The Testing Portal uses Single Sign-On through the Mozark identity provider.

You do not create a separate password for this portal.

1. Open the portal URL provided by your administrator, such as `testing.mozark.ai`.
2. If you are not already signed in, the portal redirects you to `auth.mozark.ai`.
3. Enter your credentials on the sign-in page.
4. Use your corporate email and password, or your organization's identity provider if SAML or OAuth federation is enabled.
5. After authentication succeeds, the portal redirects you back automatically.

Your session token is stored securely and refreshed in the background.

If your session expires while you are active, the portal redirects you back to the sign-in page.

Save work regularly, since open forms or unsaved changes may be lost.

{% hint style="info" %}
**Tabs stay in sync**

If you sign out in one browser tab, all open portal tabs sign out within seconds.

This behavior prevents stale sessions.
{% endhint %}

### Selecting your working context

The portal organizes data in a three-level hierarchy:

`Organization → App → Project`

Before you run any test, confirm that the correct context is selected.

Sessions, files, and bugs are always scoped to the active project.

1. Open the top navigation bar.
2. Click your user avatar or name on the right side.
3. Select your **Organization**.
4. Select your **App**.
5. Select your **Project**.

If you belong to multiple organizations, choose the one you want to work in first.

The selected organization controls which apps and projects are available.

Projects usually map to a release, feature area, or team.

Use the search box in the dropdown if the project list is long.

The portal saves your selection automatically.

When you return in the same browser, your last-used organization, app, and project are preselected.

{% hint style="warning" %}
**Always verify your project before launching a session**

Sessions, bugs, and files stay tied to the project that was active when they were created.

If you launch a session under the wrong project, its results will not appear in the intended project's history.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://mozarkdocs.gitbook.io/appx_documentation/test-infrastructure-documentation/getting-started/create-your-first-workflow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.