# Manage Team Settings

Source: https://www.digiparser.com/docs/guides/advanced-features/team-settings

Settings & Permissions

# Manage Team Settings

Change team details, configure your own AI key or storage, and manage advanced team options

Copy MarkdownOpen

# [Manage Team Settings](#manage-team-settings)

Feedback

Use Team Settings to manage members, API keys, billing, notifications, Bring Your Own services, and advanced team options.

Feedback

The options you see depend on your team permissions.

## [Open Advanced team settings](#open-advanced-team-settings)

Feedback

1.  Open the team menu.
2.  Click **Advanced**.
3.  Find **Team details**.

app.digiparser.com![Advanced team settings showing Team Name, Team Slug, Save Changes, and Danger zone](https://documents.digiparser.com/docs/screenshots/2026-07-24/team-advanced.png?sig=19e21a2a243894b3d225a5beb7ec4ddec998a53b2051f925918e977631c43694)

## [Change the team name](#change-the-team-name)

Feedback

1.  Update **Team Name**.
2.  Click **Save Changes**.

Feedback

The new name appears in the team switcher and shared workspace.

## [Change the team URL](#change-the-team-url)

Feedback

The **Team Slug** is the part of the DigiParser URL that identifies this team.

Feedback

1.  Update **Team Slug**.
2.  Check the preview shown below the field.
3.  Click **Save Changes**.

Feedback

DigiParser opens the team at its new URL. Update any saved bookmarks or shared links that use the previous team URL.

Feedback

Changing the team URL does not delete its parsers or documents.

## [Bring Your Own Key (BYOK)](#bring-your-own-key-byok)

Feedback

Bring Your Own Key is an optional workspace add-on. It lets DigiParser process documents with a Gemini or OpenAI key owned and billed by your organization.

Feedback

Open **BYOK/BYOS** in Team Settings. If the settings are unavailable, contact DigiParser support to request access. Once access is enabled, a Team Owner or Admin can complete the setup.

### [Create an OpenAI key](#create-an-openai-key)

Feedback

1.  Open [OpenAI API keys](https://platform.openai.com/api-keys) and select the OpenAI project you want to use.
2.  Click **Create new secret key**.
3.  Enter a name that identifies the DigiParser connection.
4.  Select the project and permissions, then click **Create secret key**.
5.  Copy the key immediately. OpenAI will not show it again.

app.digiparser.com![OpenAI Create new secret key dialog showing the name, project, and permissions](https://documents.digiparser.com/docs/screenshots/2026-08-05/byok-openai-create-key.png?sig=0a745d4cac3cc498941ff8519fd3c1e037a039be1552e1f1a578698bd0dc6105)

Feedback

Choose **All** for the simplest setup. If you use a restricted key, allow Models read access and allow Chat Completions and Responses to write.

### [Connect the key to DigiParser](#connect-the-key-to-digiparser)

Feedback

1.  Open **Team Settings -> BYOK/BYOS**.
2.  Turn on **Enable** under **Bring Your Own Key (BYOK)**.
3.  Select **OpenAI** or **Gemini** under **AI provider**.
4.  Choose **DigiParser recommended** unless your organization requires a specific model.
5.  Paste the provider key and click **Save configuration**.

app.digiparser.com![DigiParser Bring Your Own Key settings with OpenAI and DigiParser recommended selected](https://documents.digiparser.com/docs/screenshots/2026-08-05/byok-openai-settings.png?sig=3e9158c2aea490dada1c74023a3f0bc435527b9e3f4670cd336cca755d612a3d)

Feedback

DigiParser verifies the key before saving it. After a successful save, the full key is hidden and cannot be viewed from DigiParser.

Feedback

Use **Test key** after changing provider permissions. To replace a key, paste the new key and save the configuration again.

### [Covered operations](#covered-operations)

Feedback

*   Document extraction and reprocessing
*   Advanced table extraction
*   Document classification and document type rules
*   Split with AI and value-based partitioning
*   AI matching against CSV lookup values

Feedback

Schema generation, rule generation, and field mapping continue to use DigiParser's configured providers in this release.

### [Credits and provider billing](#credits-and-provider-billing)

Feedback

BYOK operations currently use **no DigiParser credits**. The organization pays Gemini or OpenAI directly for model usage.

Feedback

This pricing may change in the future.

Feedback

Document data, selected email context, parser instructions, and schemas needed for a covered operation are sent directly to the selected provider. DigiParser never displays the saved key again after storage.

## [Bring Your Own Storage](#bring-your-own-storage)

Feedback

Bring Your Own Storage is included with the same optional add-on as BYOK. It stores new document files in a bucket owned by your organization.

Feedback

Supported providers are:

Feedback

*   Cloudflare R2
*   Amazon S3
*   Google Cloud Storage

Feedback

The following steps show Cloudflare R2. Amazon S3 and Google Cloud Storage use the provider-specific instructions shown in DigiParser.

### [Create an R2 bucket](#1-create-an-r2-bucket)

1.  Open **R2 Object Storage** in Cloudflare.
2.  Click **Create bucket**.
3.  Enter a permanent bucket name.
4.  Choose the location and storage class required by your organization.
5.  Click **Create bucket**.

app.digiparser.com![Cloudflare R2 Create a bucket page showing bucket name, location, and storage class](https://documents.digiparser.com/docs/screenshots/2026-08-05/byos-r2-create-bucket.png?sig=12d6e0d8d1dd7e9a29f02a69d15a92ab11afcc3bf66f566abd28b1f392c4a376)

### [Create scoped R2 credentials](#2-create-scoped-r2-credentials)

1.  From **R2 Object Storage**, open **Manage R2 API Tokens**.
2.  Click **Create Account API token**.
3.  Enter a name for the DigiParser connection.
4.  Select **Object Read & Write**.
5.  Select **Apply to specific buckets only**, then choose the bucket you created.
6.  Choose a token lifetime that follows your organization's security policy.
7.  Create the token and copy the **Access Key ID** and **Secret Access Key**.

app.digiparser.com![Cloudflare R2 token settings scoped to one bucket with Object Read and Write permission](https://documents.digiparser.com/docs/screenshots/2026-08-05/byos-r2-token-scoped.png?sig=6aaf3de54a73a379175d47d3d2eac3fb8d00c802dabbe0d3a4915760f731ad67)

Cloudflare shows these credentials once. DigiParser needs the S3-compatible **Access Key ID** and **Secret Access Key**, not the Cloudflare token value.

### [Allow browser uploads](#3-allow-browser-uploads)

Open the bucket, select **Settings**, and add this policy under **CORS Policy**:

```
[
  {
    "AllowedOrigins": ["https://app.digiparser.com"],
    "AllowedMethods": ["GET", "PUT", "HEAD"],
    "AllowedHeaders": ["*"],
    "ExposeHeaders": ["ETag"]
  }
]
```

app.digiparser.com![Cloudflare R2 CORS Policy allowing DigiParser browser uploads](https://documents.digiparser.com/docs/screenshots/2026-08-05/byos-r2-cors-policy.png?sig=3925f7ea77eb143823baea19f8c218bd16d68bf5654366bb1d18601be3973fc4)

### [Connect R2 to DigiParser](#4-connect-r2-to-digiparser)

1.  Open **Team Settings -> BYOK/BYOS**.
2.  Turn on **Enable** under **Bring Your Own Storage**.
3.  Select **Cloudflare R2**.
4.  Enter the Cloudflare account ID, bucket name, R2 access key ID, and R2 secret access key.
5.  Optionally enter a folder prefix to keep DigiParser files inside one folder.
6.  Click **Verify and connect**.

app.digiparser.com![DigiParser Bring Your Own Storage settings for Cloudflare R2](https://documents.digiparser.com/docs/screenshots/2026-08-05/byos-r2-digiparser-settings.png?sig=48cf439d06d9810fc729ef87bf4e5df2b8a8c79ad685fd978c7b20943f441bb3)

DigiParser checks that it can write, read, and delete a test file before activating the connection. If the check fails, your current storage remains unchanged.

### [What happens to existing documents](#what-happens-to-existing-documents)

Feedback

The connection applies only to new documents and new document files. Existing documents remain in the storage that originally received them and continue to open normally.

Feedback

If you replace the active connection, the new connection receives future documents. Older connections remain linked to their existing documents.

### [Disable your storage connection](#disable-your-storage-connection)

Feedback

Turn off **Enable** to send future uploads back to DigiParser-managed storage. Disabling the setting does not move or delete existing files from your bucket.

Feedback

Use **Test connection** after changing bucket permissions. If DigiParser cannot access a stored document, ask an Owner or Admin to restore the connection before processing it again.

## [Permanently remove a team](#permanently-remove-a-team)

Feedback

Removing a team deletes its workspace data and cannot be undone. Export anything you need and confirm that the correct team is open before continuing.

Feedback

When **Remove Team** is available:

Feedback

1.  Scroll to **Danger zone**.
2.  Click **Remove Team**.
3.  Read the confirmation.
4.  Click **Remove Team** again to confirm.

app.digiparser.com![Remove Team confirmation](https://documents.digiparser.com/docs/screenshots/2026-07-24/remove-team-confirmation.png?sig=90fffc6408562d1fb4dfaba5e4ea551a9c043cd9a59248a0104281099e39f4a6)

Feedback

If removal is restricted, follow the message shown in **Danger zone** and contact DigiParser support.

## [Next steps](#next-steps)

Feedback

*   [Manage Team Members and Roles](/docs/guides/advanced-features/team-management) - Invite people and control access
*   [Manage Billing and Credits](/docs/guides/advanced-features/billing-and-credits) - Review the team plan and credits
*   [Notification Preferences](/docs/guides/advanced-features/notification-preferences) - Choose team and account emails

How is this guide?

GoodBad

[

Manage Team Members and Roles

Invite teammates and control what they can access in DigiParser

](/docs/guides/advanced-features/team-management)[

Notification Preferences

Choose which optional emails you receive and when summaries arrive

](/docs/guides/advanced-features/notification-preferences)