PARSER GUIDES
Manage Team Settings
Settings & Permissions
Change team details, configure your own AI key or storage, and manage advanced team options
Use Team Settings to manage members, API keys, billing, notifications, Bring Your Own services, and advanced team options.
The options you see depend on your team permissions.
Open Advanced team settings
1. Open the team menu.
2. Click Advanced.
3. Find Team details.
guide-guides-advanced-features-team-settings-01-team-advanced.webpRequired PARSER view: Advanced team settings showing Team Name, Team Slug, Save Changes, and Danger zoneFuture alt text: Advanced team settings showing Team Name, Team Slug, Save Changes, and Danger zoneChange the team name
1. Update Team Name.
2. Click Save Changes.
The new name appears in the team switcher and shared workspace.
Change the team URL
The Team Slug is the part of the PARSER URL that identifies this team.
1. Update Team Slug.
2. Check the preview shown below the field.
3. Click Save Changes.
PARSER opens the team at its new URL. Update any saved bookmarks or shared links that use the previous team URL.
Changing the team URL does not delete its parsers or documents.
Bring Your Own Key (BYOK)
Bring Your Own Key is an optional workspace add-on. It lets PARSER process documents with a Gemini or OpenAI key owned and billed by your organization.
Open BYOK/BYOS in Team Settings. If the settings are unavailable, contact PARSER support to request access. Once access is enabled, a Team Owner or Admin can complete the setup.
Create an OpenAI key
1. Open OpenAI API keys and select the OpenAI project you want to use.
2. Click Create new secret key.
3. Enter a name that identifies the PARSER connection.
4. Select the project and permissions, then click Create secret key.
5. Copy the key immediately. OpenAI will not show it again.
guide-guides-advanced-features-team-settings-02-byok-openai-create-key.webpRequired PARSER view: OpenAI Create new secret key dialog showing the name, project, and permissionsFuture alt text: OpenAI Create new secret key dialog showing the name, project, and permissionsChoose 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 PARSER
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 PARSER recommended unless your organization requires a specific model.
5. Paste the provider key and click Save configuration.
guide-guides-advanced-features-team-settings-03-byok-openai-settings.webpRequired PARSER view: PARSER Bring Your Own Key settings with OpenAI and PARSER recommended selectedFuture alt text: PARSER Bring Your Own Key settings with OpenAI and PARSER recommended selectedPARSER verifies the key before saving it. After a successful save, the full key is hidden and cannot be viewed from PARSER.
Use Test key after changing provider permissions. To replace a key, paste the new key and save the configuration again.
Covered operations
- 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
Schema generation, rule generation, and field mapping continue to use PARSER's configured providers in this release.
Credits and provider billing
BYOK operations currently use no PARSER credits. The organization pays Gemini or OpenAI directly for model usage.
This pricing may change in the future.
Document data, selected email context, parser instructions, and schemas needed for a covered operation are sent directly to the selected provider. PARSER never displays the saved key again after storage.
Bring Your Own Storage
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.
Supported providers are:
- Cloudflare R2
- Amazon S3
- Google Cloud Storage
The following steps show Cloudflare R2. Amazon S3 and Google Cloud Storage use the provider-specific instructions shown in PARSER.
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.
guide-guides-advanced-features-team-settings-04-byos-r2-create-bucket.webpRequired PARSER view: Cloudflare R2 Create a bucket page showing bucket name, location, and storage classFuture alt text: Cloudflare R2 Create a bucket page showing bucket name, location, and storage classCreate 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 PARSER 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.
guide-guides-advanced-features-team-settings-05-byos-r2-token-scoped.webpRequired PARSER view: Cloudflare R2 token settings scoped to one bucket with Object Read and Write permissionFuture alt text: Cloudflare R2 token settings scoped to one bucket with Object Read and Write permissionCloudflare shows these credentials once. PARSER needs the S3-compatible Access Key ID and Secret Access Key, not the Cloudflare token value.
Allow browser uploads
Open the bucket, select Settings, and add this policy under CORS Policy:
[
{
"AllowedOrigins": ["https://app.PARSER.com"],
"AllowedMethods": ["GET", "PUT", "HEAD"],
"AllowedHeaders": ["*"],
"ExposeHeaders": ["ETag"]
}
]
guide-guides-advanced-features-team-settings-06-byos-r2-cors-policy.webpRequired PARSER view: Cloudflare R2 CORS Policy allowing PARSER browser uploadsFuture alt text: Cloudflare R2 CORS Policy allowing PARSER browser uploadsConnect R2 to PARSER
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 PARSER files inside one folder.
6. Click Verify and connect.
guide-guides-advanced-features-team-settings-07-byos-r2-parser-settings.webpRequired PARSER view: PARSER Bring Your Own Storage settings for Cloudflare R2Future alt text: PARSER Bring Your Own Storage settings for Cloudflare R2PARSER 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
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.
If you replace the active connection, the new connection receives future documents. Older connections remain linked to their existing documents.
Disable your storage connection
Turn off Enable to send future uploads back to PARSER-managed storage. Disabling the setting does not move or delete existing files from your bucket.
Use Test connection after changing bucket permissions. If PARSER cannot access a stored document, ask an Owner or Admin to restore the connection before processing it again.
Permanently remove a team
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.
When Remove Team is available:
1. Scroll to Danger zone.
2. Click Remove Team.
3. Read the confirmation.
4. Click Remove Team again to confirm.
guide-guides-advanced-features-team-settings-08-remove-team-confirmation.webpRequired PARSER view: Remove Team confirmationFuture alt text: Remove Team confirmationIf removal is restricted, follow the message shown in Danger zone and contact PARSER support.
Next steps
- Manage Team Members and Roles - Invite people and control access
- Manage Billing and Credits - Review the team plan and credits
- Notification Preferences - Choose team and account emails