> For the complete documentation index, see [llms.txt](https://docs.fusion.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fusion.vectra.ai/settings/account/account-overview.md).

# Overview

Getting Here Settings \> Account Accounts Overview Page The Accounts Overview page displays and allows you to manage the general settings of your company's account. The following sections and settin

## Getting Here <a href="#getting-here" id="getting-here"></a>

**Settings > Account**

## Accounts Overview Page <a href="#accounts-overview-page" id="accounts-overview-page"></a>

The Accounts Overview page displays and allows you to manage the general settings of your company's account. The following sections and settings are available:

***

### 1. Shortname <a href="#id-1-shortname" id="id-1-shortname"></a>

* **Description**: A unique identifier for your account.
* **Example**: `netography`

***

### 2. Organization\* <a href="#id-2-organization" id="id-2-organization"></a>

* **Description**: The registered name of your organization.
* **Example**: `Netography, Inc.`

### SSO Login URL <a href="#sso-login-url" id="sso-login-url"></a>

* **Description**: The account-specific URL for Single Sign-On (SSO) logins.
* **Example**: `https://netography.fusion.netography.com`

### Ingest IP <a href="#ingest-ip" id="ingest-ip"></a>

* **Description**: The IP address used for ingesting data into your account.
* **Example**: `3.210.192.217:1997`

### Outbound System IP Allow Lists <a href="#outbound-system-ip-allow-lists" id="outbound-system-ip-allow-lists"></a>

* **Description**: IP addresses that are allowed to communicate with outbound systems. These IPs are categorized into three sections:
  * **Pollers**:
    * `100.25.189.39`
    * `3.209.62.136`
    * `35.168.144.18`
  * **BGP**:
    * `3.210.210.195`
    * `34.232.43.129`
  * **Integrations**:
    * `35.168.144.18`
* **Tooltip**: Information icons (`ⓘ`) next to the categories provide additional context about each list.

### Data Retention <a href="#data-retention" id="data-retention"></a>

* **Description**: Specifies the duration for retaining raw data in your account.
* **Default Value**: `180 days`

### Rollup Retention <a href="#rollup-retention" id="rollup-retention"></a>

* **Description**: Specifies the duration for retaining rolled-up or aggregated data.
* **Default Value**: `365 days`

### AWS Custom Trust Policy <a href="#aws-custom-trust-policy" id="aws-custom-trust-policy"></a>

#### Account ID <a href="#account-id" id="account-id"></a>

* **Description**: The AWS Account ID provided by Netography for trust relationships.
* **Example**: `336133252600`

#### sts:ExternalId <a href="#stsexternalid" id="stsexternalid"></a>

* **Description**: Netography-issued External ID used when creating AWS roles.
* **Example**: `81b90cd4-85b1-5e9b-b600-f9acead5b546`

#### Trust Policy <a href="#trust-policy" id="trust-policy"></a>

* **Description**: A JSON-formatted policy used to establish AWS role trust. This is required for integrating with AWS resources.
* **Example**:

{% tabs %}
{% tab title="JSON" %}

```
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "",
      "Effect": "Allow",
      "Principal": {
        "AWS": "arn:aws:iam::336133252600:root"
      },
      "Action": "sts:AssumeRole"
    }
  ]
}
```

{% endtab %}
{% endtabs %}


---

# 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://docs.fusion.vectra.ai/settings/account/account-overview.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.