> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getnetra.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Project Settings

> Configure your Netra project settings, manage team members, set up data exports, and connect integrations. Control project-level access and API keys.

Your project's command center. Manage team access, API keys, model configurations, and data exports — all from one place.

# General

Set up the basics for your project:

* **Project Name**: Edit your project's display name
* **Project ID**: View and copy your unique project identifier (read-only)

<Note>
  **Want to switch projects?** Head to the **Analytics Dashboard** and click your current **Project Name** at the top of the left nav panel. A dropdown will reveal all your available projects — just pick one to switch instantly.
</Note>

# Members

See who has access to your project at a glance. This section shows **Project Members** and **Project Admins** — the people actively collaborating within this project.

For each member, you can view:

| Detail           | Description                            |
| ---------------- | -------------------------------------- |
| **Name & Email** | Member's identity and contact          |
| **Role**         | Project Member or Project Admin        |
| **Access Level** | Permissions granted within the project |
| **Last Active**  | When they were last seen               |

<Info>
  Looking for **Organization Owners**? They won't appear here. Head over to [Organization Settings — Members](/Account-settings/Organisation#members) to view and manage them.
</Info>

### Adding Members

Click **"Add Members"** to bring new collaborators into the project — search by name or email, select the members you need, and hit save. They'll be notified right away.

# API Keys

<img src="https://mintcdn.com/netra/hTm20ddSCP9TtT6W/images/api-keys.png?fit=max&auto=format&n=hTm20ddSCP9TtT6W&q=85&s=c2a79fceacbd7154aa79e1ca80254659" alt="API Keys" width="1915" height="887" data-path="images/api-keys.png" />

Your keys to programmatic access. Each API key listed here shows its name, prefix, creation date, last usage, and quick actions to edit or delete.

### Creating a New API Key

<Steps>
  <Step title="Open Key Creation">
    Click **"Create Secret Key"** in the API Keys section.
  </Step>

  <Step title="Name Your Key">
    Give it a descriptive name so you can easily identify its purpose later.
  </Step>

  <Step title="Secure Your Key">
    Copy the generated key immediately and store it somewhere safe — the full key won't be shown again.
  </Step>
</Steps>

### Managing Existing Keys

* **Edit**: Rename a key for better identification
* **Delete**: Revoke access by removing keys you no longer need

# Models

<img src="https://mintcdn.com/netra/hTm20ddSCP9TtT6W/images/project-models.png?fit=max&auto=format&n=hTm20ddSCP9TtT6W&q=85&s=db9fcb7e4eabe7e03f414916b578e4c4" alt="Model Management" width="1910" height="882" data-path="images/project-models.png" />

Keep tabs on every language model in your project. At a glance, you can track token consumption and cost of usage across all configured models.

### Adding a New Model

<img src="https://mintcdn.com/netra/hTm20ddSCP9TtT6W/images/create-model.png?fit=max&auto=format&n=hTm20ddSCP9TtT6W&q=85&s=22cb853d46e5a03924419a92e93ec3dc" alt="create model" width="762" height="896" data-path="images/create-model.png" />

<Steps>
  <Step title="Start">
    Click **"Add Model"** to begin.
  </Step>

  <Step title="Basic Information">
    * **Model Name**: The name used in API calls and for tracking price changes.
    * **Match Pattern**: Define how this model matches incoming data using Postgres regex syntax.
      * Example: `(?i)^(modelname)$` for exact case-insensitive matching.
  </Step>

  <Step title="Configure Pricing">
    Add rate cards for the usage types that apply — input tokens, output tokens, caching, audio duration, or character count.
  </Step>
</Steps>

### Managing Existing Models

* **Duplicate**: Need a similar model? Duplicate an existing one and tweak the parameters and pricing to fit.

# Contact Points

<Columns cols={3}>
  <img src="https://mintcdn.com/netra/27XqoY2pfPeArVLM/images/contact-point1.png?fit=max&auto=format&n=27XqoY2pfPeArVLM&q=85&s=3866d2c61e462852d3e28bb3841ebe70" style={{width: '100%'}} alt="First image" width="417" height="441" data-path="images/contact-point1.png" />

  <img src="https://mintcdn.com/netra/27XqoY2pfPeArVLM/images/contact-point2.png?fit=max&auto=format&n=27XqoY2pfPeArVLM&q=85&s=35855be1081086dce415b88071e3a13e" style={{width: '100%'}} alt="Second image" width="416" height="571" data-path="images/contact-point2.png" />

  <img src="https://mintcdn.com/netra/27XqoY2pfPeArVLM/images/contact-point3.png?fit=max&auto=format&n=27XqoY2pfPeArVLM&q=85&s=5537a3b005a3e49ff030db8ed0a7c6c6" style={{width: '100%'}} alt="Third image" width="408" height="495" data-path="images/contact-point3.png" />
</Columns>

Decide where your alerts land — email inboxes, Slack channels, or both. Contact points are the destinations that get notified when something needs your attention.

### Setting Up a Contact Point

<Steps>
  <Step title="Create">
    Click **"Create Contact Point"** to get started.
  </Step>

  <Step title="Pick a Channel">
    Choose how you want to be notified:

    * **Email** — alerts sent directly to specified addresses
    * **Slack** — notifications posted to your team's workspace
  </Step>

  <Step title="Configure">
    * For **Email**: Enter the recipient addresses
    * For **Slack**: Connect your workspace and pick a channel
  </Step>

  <Step title="Test & Save">
    Fire off a test notification to make sure everything works, then save your configuration.
  </Step>
</Steps>

# Usage

<img src="https://mintcdn.com/netra/hTm20ddSCP9TtT6W/images/project-usage.png?fit=max&auto=format&n=hTm20ddSCP9TtT6W&q=85&s=b60bc566540b02c5a512b5965b07a0fd" alt="Project Usage" width="1902" height="892" data-path="images/project-usage.png" />

See exactly how your project is performing. The Usage section gives you a real-time view of resource consumption through **Span Analytics**:

| Metric                 | What it tells you                                    |
| ---------------------- | ---------------------------------------------------- |
| **Total Spans**        | Overall volume of spans generated                    |
| **Trends Over Time**   | How usage is changing day to day                     |
| **By Instrumentation** | Which instrumentations are driving the most activity |
| **Performance**        | Key performance indicators at a glance               |

# Integration

Integrations allow you to connect external services to your project for exporting and storing observability data generated by Netra. Once configured, these integrations can be used as destinations for scheduled exports, enabling long-term storage, external analysis, or compliance workflows outside the Netra platform.

<img src="https://mintcdn.com/netra/hTm20ddSCP9TtT6W/images/project-integration.png?fit=max&auto=format&n=hTm20ddSCP9TtT6W&q=85&s=1ff231a0d66f5d8195eee4f1dddd2f93" alt="Integrations" width="1887" height="891" data-path="images/project-integration.png" />

Netra supports major cloud platforms for seamless integration with your existing infrastructure.

***

### Supported Providers

<CardGroup cols={2}>
  <Card title="Amazon Web Services (AWS)" icon="aws">
    Export data to Amazon S3 buckets with IAM-based authentication.
  </Card>

  <Card title="Google Cloud Platform (GCP)" icon="google">
    Export data to Google Cloud Storage buckets with service account authentication.
  </Card>
</CardGroup>

### Adding an Integration

<Steps>
  <Step title="Start Integration">
    Navigate to **Project Settings** → **Integration** and click **Add Integration**.
  </Step>

  <Step title="Select Provider Type">
    Choose your cloud provider:

    | Provider | Description                                           |
    | -------- | ----------------------------------------------------- |
    | **AWS**  | Amazon S3 storage with access key authentication      |
    | **GCP**  | Google Cloud Storage with service account credentials |
  </Step>

  <Step title="Configure Bucket Details">
    Enter your storage bucket information:

    | Field           | Description                                    | Example                                  |
    | --------------- | ---------------------------------------------- | ---------------------------------------- |
    | **Bucket Name** | The name of your cloud storage bucket          | `my-company-netra-exports`               |
    | **Region**      | Geographic region where your bucket is located | `us-east-1` (AWS) or `us-central1` (GCP) |
  </Step>

  <Step title="Provide Authentication Credentials">
    Enter your access credentials based on the selected provider:

    <Note>
      **Your credentials are secure.** All access keys and secrets are encrypted using industry-standard encryption and stored securely. We never expose or log your credentials in plain text.
    </Note>

    <AccordionGroup>
      <Accordion title="AWS Credentials" icon="aws">
        | Field                 | Description                        |
        | --------------------- | ---------------------------------- |
        | **Access Key ID**     | Your AWS IAM access key identifier |
        | **Secret Access Key** | Your AWS IAM secret access key     |

        **Minimum Permissions Required:**

        | Permission        | Resource       |
        | ----------------- | -------------- |
        | `s3:ListBucket`   | Bucket ARN     |
        | `s3:PutObject`    | Bucket objects |
        | `s3:GetObject`    | Bucket objects |
        | `s3:DeleteObject` | Bucket objects |

        <Tip>
          We recommend creating a dedicated IAM user with only these permissions scoped to the target bucket.
        </Tip>
      </Accordion>

      <Accordion title="GCP Credentials" icon="google">
        | Field                   | Description                                         |
        | ----------------------- | --------------------------------------------------- |
        | **Service Account Key** | JSON key file contents for your GCP service account |

        **Minimum Permissions Required:**

        | Role                        | Resource      |
        | --------------------------- | ------------- |
        | `roles/storage.objectAdmin` | Target bucket |

        <Tip>
          Create a service account with only the **Storage Object Admin** role scoped to the target bucket.
        </Tip>
      </Accordion>
    </AccordionGroup>
  </Step>

  <Step title="Save & Verify">
    Click **Save Integration** to store your configuration. Netra will verify the connection by testing bucket access.
  </Step>
</Steps>

<Warning>
  Ensure your bucket has the correct permissions before saving. Integration verification will fail if Netra cannot write to the specified bucket.
</Warning>

***

### Integration Listing

The Integration page displays all configured cloud storage connections:

| Column            | Description                     |
| ----------------- | ------------------------------- |
| **Provider Type** | The cloud provider (AWS or GCP) |
| **Bucket Name**   | The target storage bucket name  |

***

# Export

<img src="https://mintcdn.com/netra/hTm20ddSCP9TtT6W/images/project-export.png?fit=max&auto=format&n=hTm20ddSCP9TtT6W&q=85&s=5e1ab86c392025fb53ed72109465fbe9" alt="Data Export" width="1902" height="897" data-path="images/project-export.png" />

Configure automated data exports to send your observability data to external storage at regular intervals. Exports allow you to maintain long-term archives, integrate with data warehouses, or comply with data retention requirements.

<CardGroup cols={3}>
  <Card title="Flexible Scheduling" icon="clock">
    Export hourly or daily based on your needs.
  </Card>

  <Card title="Multiple Formats" icon="file-export">
    Choose JSON or CSV format for compatibility with your tools.
  </Card>

  <Card title="Historical Data" icon="clock-rotate-left">
    Optionally export your complete historical data on first run.
  </Card>
</CardGroup>

***

### Creating an Export

<Steps>
  <Step title="Initiate Export">
    Navigate to **Project Settings** → **Export** and click **Create Export**.
  </Step>

  <Step title="Basic Configuration">
    Configure the fundamental export settings:

    | Field                  | Description                                              |
    | ---------------------- | -------------------------------------------------------- |
    | **Export Name**        | A descriptive name to identify this export configuration |
    | **Destination Bucket** | Select from your configured integrations                 |
  </Step>

  <Step title="Select File Format">
    Choose the output format for your exported data:

    | Format   | Best For                                                              |
    | -------- | --------------------------------------------------------------------- |
    | **JSON** | Data pipelines, programmatic processing, preserving nested structures |
    | **CSV**  | Spreadsheet analysis, SQL imports, business intelligence tools        |
  </Step>

  <Step title="Configure Export Frequency">
    Set how often data should be exported:

    | Frequency  | Description              |
    | ---------- | ------------------------ |
    | **Hourly** | Export data every hour   |
    | **Daily**  | Export data once per day |
  </Step>

  <Step title="Historical Data Option">
    Choose whether to include historical data:

    | Option  | Description                                                           |
    | ------- | --------------------------------------------------------------------- |
    | **Yes** | Include all historical data from project creation in the first export |
    | **No**  | Only export new data from the export creation time onwards            |

    <Note>
      Exporting full history may result in a large initial export depending on your project's data volume. Subsequent exports will only include incremental data.
    </Note>
  </Step>

  <Step title="Set Path Prefix">
    Configure the folder structure for exported files:

    | Field           | Description                                                  | Example                     |
    | --------------- | ------------------------------------------------------------ | --------------------------- |
    | **Path Prefix** | Directory path within your bucket where files will be stored | `netra/exports/production/` |

    **Resulting file path:** `s3://your-bucket/netra/exports/production/2026-01-29/traces_001.json`
  </Step>

  <Step title="Review & Create">
    Review all settings and click **Create Export** to activate the export schedule.
  </Step>
</Steps>

***

### Export Listing

The Export page displays all configured export jobs with the following information:

| Column             | Description                                        |
| ------------------ | -------------------------------------------------- |
| **Export Name**    | The name you assigned to identify this export      |
| **File Format**    | Output format (JSON or CSV)                        |
| **Path Prefix**    | Directory path within the destination bucket       |
| **Frequency**      | Export schedule (Hourly or Daily)                  |
| **Status**         | Current state of the export (Active, Paused, etc.) |
| **Created At**     | When the export configuration was created          |
| **Last Synced At** | Timestamp of the most recent successful export     |