# Export

Export lets you pull structured data out of Siit whenever you need to analyze it elsewhere or share a snapshot with stakeholders. You can export any core object, filter to exactly the rows you need, and the data you see is governed by your role and field visibility.

#### What you can export

* Requests: full request table with requester context, status, priority, SLA dates, tags, channel, inbox, assignee, service/category, rating, and more.
* Communication: outbound messages and satisfaction surveys.
* People: directory data and groups (department, team, office, legal entity).
* Services: catalog items and configuration metadata.
* Applications: app inventory and ownership fields.
* Equipment: device inventory, lifecycle, ownership, and key attributes.
* Workflows: titles, state (Live/Paused/Draft), trigger, category, and usage counts.

Suggested visual

* \[Screenshot] Export page with tabs (Requests, Communication, People, Services, Applications, Equipment, Workflows)

#### Filters

Filters use the chip-based filter bar to narrow your export. Filters vary by object and typically include:

* Requests: Requester, Requester team/department/office, Associated to (service), Service category, Channel and Channel details, Status, Priority, Inbox, Assignee, Created at, First replied at, Completed at, Rating, Tags, Approval pending, Archived.
* People: Department, Team, Office location, Legal entity, Employment type, Lifecycle.
* Applications: Category, Owner, Lifecycle, Sensitive data.
* Equipment: Type, Lifecycle, Owner, Office location, Last contact date.

💡 Tip

* Apply date filters first (Created at, Completed at) to keep exports focused and fast.

#### Permissions and scope

* Role-based access: Only users with the Export permission can access the Export area. Admins can restrict which objects are exportable per role.
* Field visibility: Sensitive fields (for example, compensation or PII) respect field visibility settings. If a field is off for your role, it won’t appear in the preview or file.
* Data scope: Exports respect object-level permissions. You can only export what you can view in Siit.


---

# Agent Instructions: 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:

```
GET https://docs.siit.io/reporting-and-analytics/export.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.