> 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/products/business-data-repository/api-reference/actors.md).

# Actors

Actors represent entities that can authenticate and perform actions in the system, including users and integrations.

Actors represent entities that can perform actions in the system. This includes users (human operators) and integrations (API clients and automated systems).

## Objects

### PersonName

Structured person name components following W3C Personal Names guidance. See: <https://www.w3.org/International/questions/qa-personal-names>

Examples by culture:

* US: givenNames="John", familyNames="Smith", middleName="Robert"
* Russia: givenNames="Иван", familyNames="Иванов", middleName="Петрович" (patronymic)
* Spain: givenNames="Juan Carlos", familyNames="García López" (paternal + maternal)
* China: givenNames="明" (Ming), familyNames="王" (Wang) — note: family name first in native order
* Iceland: givenNames="Björk", familyNames="Guðmundsdóttir" (patronymic as family name)

| Field         | Type      | Description                                                                                                        |
| ------------- | --------- | ------------------------------------------------------------------------------------------------------------------ |
| `givenNames`  | `String!` | The given name(s), also known as first name(s). May contain multiple names separated by spaces.                    |
| `familyNames` | `String!` | The family name(s), also known as surname(s) or last name(s). May contain multiple names.                          |
| `middleName`  | `String`  | The middle name, patronymic, or additional name component.                                                         |
| `fullName`    | `String!` | The non-blank name parts (given names, middle name, family names) joined by single spaces; empty when none is set. |

***

### SystemActor

The built-in system actor used for automated operations.

**Implements:** [Actor](#actor), [Node](/docs/navixy-graphql-api/core-api-reference/common.md#node), [Titled](/docs/navixy-graphql-api/core-api-reference/common.md#titled)

| Field   | Type      | Description                    |
| ------- | --------- | ------------------------------ |
| `id`    | `ID!`     | A globally unique identifier.  |
| `title` | `String!` | The display name of the actor. |

***

## Interfaces

### Actor

An entity that can perform actions.

**Implements:** [Node](/docs/navixy-graphql-api/core-api-reference/common.md#node), [Titled](/docs/navixy-graphql-api/core-api-reference/common.md#titled)

| Field   | Type      | Description                    |
| ------- | --------- | ------------------------------ |
| `id`    | `ID!`     | A globally unique identifier.  |
| `title` | `String!` | The display name of the actor. |

***

## See also

* [Pagination](/docs/navixy-graphql-api/pagination.md)
* [Filtering and sorting](/docs/navixy-graphql-api/filtering-and-sorting.md)
* [Error handling](/docs/navixy-graphql-api/error-handling.md)
* [Optimistic locking](/docs/navixy-graphql-api/optimistic-locking.md)
* [Limits](/docs/navixy-graphql-api/limits.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://navixy.com/docs/navixy-graphql-api/products/business-data-repository/api-reference/actors.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.