> For the complete documentation index, see [llms.txt](https://docs.apica.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apica.io/platform-docs/test-data-orchestrator-tdo/user-documentation/end-user-guide-for-tdo/connecting-to-orson.md).

# Connecting to Orson

## Orson – Test Data Orchestrator

End User Guide

### Logging into TDO

Begin by logging into TDO in Chrome or Chromium.

&#x20;

The URL for accessing TDO will look like one of these examples:

&#x20;

http\:// 52.314.86.41:8080/ui/public/login (using server IP address)&#x20;

https\:// 52.314.86.41:443/ui/public/login  (with https enabled)

<http://localhost:8080/ui/public/login>   (using a remote desktop for using TDO)

<http://abcxyz00004025.apica.com:8080/ui/public/login> (where TDO is installed on a VM)

&#x20;

On the login screen, enter your user and password and click the LOGIN button.

&#x20;

<figure><img src="/files/VvCPdNGmfBcxqa5fLaWi" alt=""><figcaption><p>Orson TDO Login Screen</p></figcaption></figure>

### &#x20;Working With the Menu

&#x20;

You will see the initial splash screen.  The menu is accessed by clicking on the three stacked horizontal bars (‘burger menu’) in the upper left hand corner.

<figure><img src="/files/A9QvhIKwcjZrgX0vcZNp" alt=""><figcaption><p>Orson TDO Initial Splash Screen</p></figcaption></figure>

&#x20;

When you open the menu, you will see this.&#x20;

&#x20;

If you want to ‘pin’ the menu to the left side of your screen, click the pin icon at the top of the menu list.  If you do not ‘pin’ the menu, you will need to click the three bars each time you need to use the menu.

&#x20;

If you ‘pin’ the menu, the icon will change to a pin with a line through it.  Click this icon to unpin the menu.

### Selecting a Project

&#x20;

Click on ‘Projects’ under the Project section of the menu to open the Project screen.

&#x20;

<figure><img src="/files/IwnRjpnvOtdOpiM8jKif" alt=""><figcaption><p>Main Menu</p></figcaption></figure>

&#x20;

The project screen will display all  the projects that you have authority to access.  Move your mouse to the right of the project names and the action buttons will open.  Click the blue check box to select the project you will be working in.  When you select a project, you will see a green message box with ‘Project has been successfully selected’ and the project name will be populated in the blue context box in the upper right corner.

&#x20;

If you don’t see the project name you believe you should have access to, please contact your administrator to request access.

&#x20;

<figure><img src="/files/KSnPFAfBpVSvWKN95xEP" alt=""><figcaption><p>Project selection screen</p></figcaption></figure>

&#x20;

You must select a project to work in before you can take any other actions.  TDO is context-driven, in that all of the actions you can perform are limited to the project, coverage set, and workset you have selected.


---

# 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://docs.apica.io/platform-docs/test-data-orchestrator-tdo/user-documentation/end-user-guide-for-tdo/connecting-to-orson.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.
