> For the complete documentation index, see [llms.txt](https://docs.seedata.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seedata.io/features/seeds/person.md).

# Person

## Format

A fictitious person complete with a realistic name, job title, address and contact details. Issued as a set of data fields and delivered within a CSV file. Example: John Doe, Senior Manager, <john.doe@domain.com>, +44 1234 567890.

## Capabilities

1. **Event Raising for Inquiries**: The platform raises an event for any communication attempts made towards the seeded person by emails. Each event includes threat analysis of the interaction.
2. **Observation on the Web**: The platform monitors the web for any mentions or usage of the seeded person's details, providing threat analysis on the domain or source where the observation occurs.

## Usage

Integrate our person seeds within your organizational directories, CRM systems, or social media profiles to detect unauthorized access or malicious activity targeting these identities.


---

# 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://docs.seedata.io/features/seeds/person.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.