> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/reporting-and-analytics/export.md).

# 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.