# Fields

### **Structure of Profiles**

Profiles are an OpenReview object that contains properties. The main three properties that you can expect to interact with are: 

**`id`**

* **Type:** `str`
* **Description:** The unique identifier of the profile, usually in the form `~First_Last1`.
* **Purpose:** Used as the unique reference to the user across OpenReview (e.g., for assigning roles, authorship, etc.).

`state` 

* **Type**: `str` 
* **Description**: The status of the profile
  * `Active` : Profile was moderated and is now active
  * `Active Institutional` : Profile contains an approved institutional email domain
  * `Inactive` : User has not completed Profile Registration (profile is not active)
  * `Rejected` : User needs to correct information in the profile and resubmit it for moderation
  * `Needs Moderation` : Profile is pending moderation

**`content`**

* **Type:** `dict`
* **Description:** The main body of the profile data. It contains structured information about the user.
* **Key Subfields:**
  * `names`: List of name entries. Each entry is a dict with keys like `first`, `last`.
  * `emailsConfirmed`: List of verified email addresses.
  * `emails` : List of all email addresses
  * `preferredEmail`: The primary email to be used for communication.
  * `history`: List of affiliations over time, each with `institution`, `position`, `start`, and `end`.
  * `homepage` , `gscholar`, `dblp`, `github`: Social and academic links.
  * `expertise`: Manually entered expertise areas.
  * `relations`: Manually entered relationships to other users in the OpenReview system.


---

# Agent Instructions: 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:

```
GET https://docs.openreview.net/reference/api-v2/entities/profile/fields.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.