> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/navixy-graphql-api/business-data-repository.md).

# Business Data Repository

- [Business Data Repository overview](https://navixy.com/docs/navixy-graphql-api/business-data-repository/overview.md): Business Data Repository manages assets, devices, geo objects, schedules, custom fields, and catalogs through Navixy GraphQL API.
- [Guides](https://navixy.com/docs/navixy-graphql-api/business-data-repository/guides.md)
- [Managing device records and identifiers](https://navixy.com/docs/navixy-graphql-api/business-data-repository/guides/managing-device-records-and-identifiers.md): Register and manage GPS trackers, sensors, and other hardware devices.
- [Managing device inventory](https://navixy.com/docs/navixy-graphql-api/business-data-repository/guides/managing-device-inventory.md): Create inventories, assign devices to them, transfer devices, and track assignment history.
- [Creating assets and assigning devices](https://navixy.com/docs/navixy-graphql-api/business-data-repository/guides/creating-assets-and-assigning-devices.md): Create and manage assets: vehicles, equipment, and other tracked objects.
- [Organizing assets into groups](https://navixy.com/docs/navixy-graphql-api/business-data-repository/guides/organizing-assets-into-groups.md): Organize assets into typed, color-coded collections for fleet segmentation and reporting.
- [Defining and using custom fields](https://navixy.com/docs/navixy-graphql-api/business-data-repository/guides/defining-and-using-custom-fields.md): Define and use custom fields to attach domain-specific data to entities.
- [Defining recurring schedules](https://navixy.com/docs/navixy-graphql-api/business-data-repository/guides/defining-recurring-schedules.md): Create, update, query, and delete JSCalendar-aligned schedules compatible with RFC 5545 (iCalendar).
- [Creating geofences, POIs, and routes](https://navixy.com/docs/navixy-graphql-api/business-data-repository/guides/creating-geofences-pois-and-routes.md): Create geofences, POIs, and routes in different shapes using GeoJSON geometry.
- [Investigating changes with audit logs](https://navixy.com/docs/navixy-graphql-api/business-data-repository/guides/investigating-changes-with-audit-logs.md): Reconstruct who changed an entity, what they changed, and when with entityHistory and auditEvents queries.
- [Business Data Repository API reference](https://navixy.com/docs/navixy-graphql-api/business-data-repository/api-reference.md): How the Business Data Repository reference is organized: one page per category for workspaces, actors, devices, assets, geo objects, schedules, custom fields, audit, and catalogs.
- [Workspaces](https://navixy.com/docs/navixy-graphql-api/business-data-repository/api-reference/workspaces.md): Workspaces are isolated tenants that own all business data: members, devices, assets, geo objects, and configuration. Navixy Console provisions and owns them, so this API exposes workspaces read-only.
- [Members](https://navixy.com/docs/navixy-graphql-api/business-data-repository/api-reference/workspaces/members.md): Query reference for workspace members: which users belong to a workspace, whether each membership is active, and when it was assigned.
- [Actors](https://navixy.com/docs/navixy-graphql-api/business-data-repository/api-reference/actors.md): Actors represent entities that can authenticate and perform actions in the system, including users and integrations.
- [Users](https://navixy.com/docs/navixy-graphql-api/business-data-repository/api-reference/actors/users.md): Reference for user accounts and user-defined catalog items: the read-only User object and the mutations that manage hierarchical catalog entries.
- [Integrations](https://navixy.com/docs/navixy-graphql-api/business-data-repository/api-reference/actors/integrations.md): Queries and mutations for integration accounts used by API clients, automated systems, and third-party service connections.
- [Devices](https://navixy.com/docs/navixy-graphql-api/business-data-repository/api-reference/devices.md): Complete reference for devices: register GPS trackers and sensors, manage hardware identifiers, link devices to assets, and track relations.
- [Inventory](https://navixy.com/docs/navixy-graphql-api/business-data-repository/api-reference/devices/inventory.md): Complete reference for device inventory. Manage warehouses, assign devices to inventory locations, and query assignment history.
- [Assets](https://navixy.com/docs/navixy-graphql-api/business-data-repository/api-reference/assets.md): Complete reference for assets: queries, mutations, and types for the trackable business objects your workspace monitors and manages.
- [Asset groups](https://navixy.com/docs/navixy-graphql-api/business-data-repository/api-reference/assets/groups.md): Complete reference for asset groups: group types with membership rules, groups, memberships, and history.
- [Geo objects](https://navixy.com/docs/navixy-graphql-api/business-data-repository/api-reference/geo-objects.md): Complete reference for geo objects: queries, mutations, and types for geofences, points of interest, and routes with GeoJSON geometry.
- [Schedules](https://navixy.com/docs/navixy-graphql-api/business-data-repository/api-reference/schedules.md): Complete reference for schedules, including queries, mutations, and types for defining recurring time patterns such as working hours and maintenance windows (iCalendar-compatible).
- [Custom fields](https://navixy.com/docs/navixy-graphql-api/business-data-repository/api-reference/custom-fields.md): Type definitions for custom field definitions, including field types, params, options, filter inputs, and the patch input used in asset and geo object mutations.
- [Audit](https://navixy.com/docs/navixy-graphql-api/business-data-repository/api-reference/audit.md): Query the audit trail to retrieve a paginated, filterable log of entity create, update, and delete events across your workspace.
- [Catalogs](https://navixy.com/docs/navixy-graphql-api/business-data-repository/api-reference/catalogs.md): Explains catalogs as Business Data Repository reference data, including the CatalogItem interface, item origins, display metadata, and hierarchical items.
- [Catalog items](https://navixy.com/docs/navixy-graphql-api/business-data-repository/api-reference/catalogs/catalog-items.md): Queries, mutations, and types for catalog items, the configurable lookup entries used for device types, asset types, statuses, and other reference data.
- [Catalog reference](https://navixy.com/docs/navixy-graphql-api/business-data-repository/api-reference/catalogs/catalog-reference.md): Cross-reference of all catalog types organized by entity. Use this page to find which catalog backs a given field.
- [Tags](https://navixy.com/docs/navixy-graphql-api/business-data-repository/api-reference/catalogs/tags.md): Complete reference for tags. Create and manage flexible labels for classifying assets, geo objects, and other entities.
- [System catalogs](https://navixy.com/docs/navixy-graphql-api/business-data-repository/api-reference/catalogs/system.md): Predefined system catalog items available to all workspaces. These read-only reference types cannot be modified or deleted.


---

# 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://navixy.com/docs/navixy-graphql-api/business-data-repository.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.