> For the complete documentation index, see [llms.txt](https://docs.redivis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.redivis.com/reference/organizations/settings/advanced-data-egress-project.md).

# Advanced: Egress configuration

Redivis does not charge data egress fees on data exports. To help manage cloud costs, each user can download up to 100 GB over a 30-day window across Redivis.

An organization can remove this limit for its data by billing egress to their own Google Cloud project. This may be free or low-cost for educational institutions with an [egress waiver from Google](https://cloud.google.com/billing/docs/how-to/egress-waiver). Otherwise, Google bills the project at its standard [network egress rates](https://cloud.google.com/vpc/network-pricing).

Downloads of the organization's data then use the [Requester Pays](https://cloud.google.com/storage/docs/requester-pays) feature of Google Cloud Storage, which bills the egress for each download to the project. No data moves through the project, and Redivis cannot view or change anything in it. The configuration can also limit how much each user downloads.

The **Egress configuration** section of an organization's **Advanced** settings shows the configuration that applies to the organization.

<div data-with-frame="true"><figure><img src="https://1672950126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVodLwUXgJUGcm5Cvso%2Fuploads%2FRb3c3QvGYyaBoPUXQJnT%2FScreenshot%202026-11-20%20at%2015.16.15.png?alt=media&amp;token=2f3de0ae-3146-4e62-acbe-88db58263569" alt=""><figcaption></figcaption></figure></div>

## Configuration

An organization administrator can set the egress configuration to one of three options.

#### Default

Egress is not billed to a Google Cloud project. Each user can download up to 100 GB over a 30-day window across Redivis.

#### Custom

Egress is billed to a Google Cloud project that an organization administrator provides. A custom configuration can also set [per-user download limits](#per-user-download-limits).

#### Inherit from institution

The organization uses the egress configuration of its [institution](https://docs.redivis.com/reference/institutions.md), including its project and per-user download limits, and follows any later changes to it. This option is available only to organizations within an institution.

An organization within an institution that has not set its own egress configuration inherits the institution's. To opt out of the institution's configuration, an organization administrator can choose **Default**.

The **Egress configuration** modal shows the selected option and its settings.

<div data-with-frame="true"><figure><img src="https://1672950126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVodLwUXgJUGcm5Cvso%2Fuploads%2FdhFeY3iQVGUv7otdy2kW%2FScreenshot%202026-11-20%20at%2015.12.30.png?alt=media&amp;token=bed194d0-43d7-4cfd-9901-02ad24a7d4c4" alt=""><figcaption></figcaption></figure></div>

## Updating the Google Cloud project

When updating the Google Cloud project, Redivis opens a Google sign-in window. The administrator's Google account must have the `serviceusage.services.use` permission on the project, which the Owner, Editor, and Service Usage Consumer roles include. The project must have billing enabled.

After the sign-in, Redivis grants its service account, `redivis@redivis-identity.iam.gserviceaccount.com`, the [Service Usage Consumer](https://cloud.google.com/service-usage/docs/access-control#roles) role on the project. This role solely allows Redivis to bill downloads to the project. Redivis does not have any other access to the project.

Google Cloud can take a few minutes to apply the new role, and downloads billed to the project may fail until it does.

## Per-user download limits

A custom configuration can set **Daily**, **Weekly**, and **Monthly** limits, in GB, on how much each user downloads. An empty limit means no limit.

The following rules apply to per-user download limits:

* Limits use UTC calendar days, weeks, and months, and reset at the start of each period.
* Each limit must be greater than the limit for any shorter period.
* Limits count only downloads billed to the configuration's project.
* Organization administrators are not subject to limits.

When a user reaches a limit, they cannot download more data billed to the project until the period resets.

An institution's per-user download limits apply across every organization that inherits its configuration. For example, with a 50 GB monthly limit, a user can download 50 GB per month in total across those organizations, rather than 50 GB from each. Institution administrators are also not subject to an institution's limits.

{% hint style="info" %}
Redivis counts the bytes Google Cloud reports sending for each download. These reports can take several hours to arrive, and until then Redivis counts a download at its full requested size.

Due to the highly-concurrent nature of certain large downloads, it is possible for users to slightly exceed their egress limits, which are enforced on a best-effort basis.
{% endhint %}

## Exports billed to the project

Downloads of tables and files are billed to the project. The following exports cannot be billed to another project, and count toward each user's default 100 GB limit instead:

* Table data read directly into another environment, such as with the Redivis client libraries
* Exports to a destination outside the `us-central1` region

When an export includes data from several organizations, Redivis bills it to the project of the organization whose data makes up the largest share of the export, and that organization's per-user download limits apply.


---

# 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.redivis.com/reference/organizations/settings/advanced-data-egress-project.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.
