> For the complete documentation index, see [llms.txt](https://help.swarmia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.swarmia.com/data-model/entities/author.md).

# Author

Authors are the people or bots that can be attributed different kinds of work items (commits, pull requests, reviews). Authors can be linked to multiple identities across different systems (GitHub, Slack, Jira, etc.).

## Properties

### ID

`id` - [uuid](/data-model/types/uuid.md)

ID of the author.

### Name

`name` - [text](/data-model/types/text.md) | null

Name of the author, resolved from their linked Swarmia user or, failing that, from their identities in connected integrations. Null when none of them carry a name or a username.

### Email

`email` - [text](/data-model/types/text.md) | null

Preferred work email of the author, resolved from their identities using the organization work email domain preferences.

### Is bot

`isBot` - [boolean](/data-model/types/boolean.md)

Whether this author is marked as a bot.

### Is current GitHub member

`isCurrentGitHubMember` - [boolean](/data-model/types/boolean.md)

Whether this author is currently a member of one or more GitHub organizations associated with this Swarmia organization.

### Timestamp

`timestamp` - [timestamp](/data-model/types/timestamp.md)

Time when this author was first seen by Swarmia in any of the connected integrations.

### Included in Capex report

`includeInCapexReport` - [boolean](/data-model/types/boolean.md)

Whether this author is included in the organization’s Capex report. All non-bot authors are included by default, and can be manually excluded or re-included.

### FTE allocation

`fteAllocation` - [double](/data-model/types/double.md) | null

FTE measures developer effort. By default, each developer gets 1 FTE per month, distributed across projects based on related commits, activity on PRs, and completed issues. 0 means the person doesn’t work as a developer. Null for bots, which are excluded from FTE.

## Relations

### Member of teams

`memberOfTeams` - [Team](/data-model/entities/team.md) (1-N)

Teams this author is a member of.

### Team memberships

`teamMemberships` - [Team membership](/data-model/entities/team-membership.md) (1-N)

Team membership periods for this author, including inherited memberships through the team hierarchy.

### Assigned issues

`assignedIssues` - [Issue](/data-model/entities/issue.md) (1-N)

Issues this author is currently assigned to.

### Pull requests

`pullRequests` - [Pull request](/data-model/entities/pull-request.md) (1-N)

Pull requests created by this author.

### Attribute values

`attributeValues` - [Author attribute value](/data-model/entities/author-attribute-value.md) (1-N) - **Beta**

Attribute values this author holds.

{% hint style="info" %}
This page is automatically generated
{% endhint %}


---

# 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://help.swarmia.com/data-model/entities/author.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.