> For the complete documentation index, see [llms.txt](https://kb.bravegen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bravegen.com/carbon/core-concepts/reporting-entities/managing-entities/entity-details.md).

# Entity Details

Manage an entity’s reporting settings, contacts, location, and change history.

The entity details view is accessed by clicking the details tab when you have a selected entity under Carbon. It shows the reporting settings and general information about a particular entity.

Users with the editor or administrator [role](/carbon/configuration/user-management/user-roles.md) will see a manage button on the top right which will allow for the updating of this information.

## Reporting Settings

Manages how an entity is included and represented in reports

<figure><img src="https://56003612-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5LvYBvfJ43u2Q5Y715DI%2Fuploads%2FAQs01OYx5O0XiMmUDAcz%2Fimage.png?alt=media&amp;token=61314a40-162b-466a-a1bf-8fe753ec583c" alt=""><figcaption></figcaption></figure>

### Display Name

The name used in the BraveGen UI and Reports. This is not related to any mapping or incoming data.

### Aliases

Entity identifiers used by this entity in incoming data. These are added whenever you merge or assign an incoming identifier to an existing entity. Removing an alias will break detatch the identifier into a separate entity along with any sources using that identifier. See [Moving & Merging Entities](/carbon/core-concepts/reporting-entities/managing-entities/moving-and-merging-entities.md)

### Entity Type

Determines what type of entity it is, and any additional fields available on the entity. See [Entity Types](#entity-type)

### Parent Entity

Unless reporting to the Equity Share reporting boundary approach, an entity can only have a single parent entity. Users can set a Control or Equity % which indicates their level of financial / operational / equity control over the entity. All emissions from this entity will include be reported proportionally in accordance with your control type.

#### Parent Entity Effective Dates (Effective From, Effective To)

The effective to and effective from date fields on a parent entity determine the window that emissions calculated from activity data will be included in reports. Activity data collected outside this period will be stored but not included in any reports, *even if the effective dates on the inventory item would fall outside this window.*

<details>

<summary>Effective From</summary>

Setting an Effective From date on an Entity determines the first date that emissions will be reported for this entity. All entities require an effectiveFrom date.

{% hint style="info" %}
You can use this feature to exclude emissions generated before you take ownership / occupancy of a building.
{% endhint %}

</details>

<details>

<summary>Effective To</summary>

Setting an Effect To date on an Entity determines the last date that emissions will be reported for this entity. Setting an effective to date is optional; if this is left blank the entity is considered an ongoing concern.

</details>

### Include in reporting

Allows user to exclude from reporting. If this is toggled off then a reason for exclusion is required.

### Control Type

Based on your [reporting boundary](/carbon/configuration/reporting-settings/reporting-boundaries.md) you will have chosen a consolidation approach (Operational Control, Financial Control or Equity Share). A **true** value will determine whether this entity is included in reporting. A false value means that you should categorise all Scope 1 and Scope 2 as Scope 3 emissions.

### Tags

Tags are used for grouping entities and inventory during reporting.

### Principal Activity

An optional field that describes the main activity at this entity. This is output in the Organisational Boundary [Disclosure](/carbon/audit-trail/disclosures.md) in the Audit Trail Snapshot

### Additional Fields

Additional metadata, not used by the BraveGen System to aid with reporting:

* ISIC Code
* ANZSIC Code
* ABN / NZBN Number
* ACN Number
* ARBN Number
* Description

***

## Contacts

Assign known contacts or BraveGen users to an entity

#### <i class="fa-circle-dashed" style="color:$warning;">:circle-dashed:</i> <mark style="color:$warning;">Planned Functionality</mark>

<mark style="color:$warning;">This is a planned feature on the BraveGen product roadmap. For updates, or to request prioritised development of this feature, please</mark> [<mark style="color:$warning;">contact our CPO</mark>](mailto:jeremy.allen@bravegen.com)

***

## Location

Document entity address, and location for operational reference

* Address
* City
* Region
* Country
* Latitude and Longitude

<figure><img src="https://56003612-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5LvYBvfJ43u2Q5Y715DI%2Fuploads%2F3TMyQ7cKQ2EWwfYG9456%2Fimage.png?alt=media&amp;token=a24dd671-fd23-450f-aa74-43f917680c3f" alt=""><figcaption></figcaption></figure>

***

## Log

The history of any changes made to this entity or it's sources or inventory items.