> For the complete documentation index, see [llms.txt](https://docs.giize.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.giize.com/ticket-dashboard-en/feature-guides/order-report.md).

# My Portal And Portal Tools

## Purpose

The IT Portal area is split into two browser pages:

* `My Portal` tracks orders created by or linked to the current SDP user
* `Portal Tools` provides report, asset lookup, creation, and supported approval actions

Together they are used to:

* scrape order data from IT Portal
* filter and inspect order flows
* support return, replacement, and offboarding-related request creation
* export structured JSON for later analysis

## Runtime Model

* Playwright is used to keep the IT Portal session alive
* the app then calls JSON endpoints under `/am_ajax`
* cached session state reduces repeated login prompts
* local handlers live in `server/routes/orders.mjs` and domain logic in `server/it-portal.mjs`

## Frontend Structure

`OrderReportPage.jsx` owns orchestration. Large panels and modals live under `frontend/src/pages/order-report/` following the C3 split.

## Typical Use Cases

* return device workflows
* replacement device flows
* employee offboarding collection flows
* reporting and export

## Important Behavior

* session reuse matters; stale cookies usually look like silent data failures
* many workflow rules are workflow-specific, not globally interchangeable
* direct manager and asset lookup fields often gate request creation

## Related References

* `API Reference / IT Portal API`
* `API Reference / Staging API` when planning future request-side integrations