[impoiler]

Summary

The virtual keys CSV export now includes an "Assigned User Email" column. Previously the export showed only the "Assigned To" value, so there was no way to see which user's email a key belonged to. This adds that email to the export.

Changes

• Added an "Assigned User Email" column to the virtual keys CSV export, placed right after "Assigned To".
• Each row's value comes from vk.assigned_user?.email. It is an empty string when the key has no assigned user, so the column count stays consistent across rows.
• The new cell uses the same quoting and escaping as the other columns.
• Both the "current page" and "all" export scopes include the column, since they share the same CSV builder.

Type of change

• Bug fix
• Feature
• Refactor
• Documentation
• Chore/CI

Affected areas

• Core (Go)
• Transports (HTTP)
• Providers/Integrations
• Plugins
• UI (React)
• Docs

How to test

1. Open the Virtual Keys page in the workspace.
2. Make sure at least one key is assigned to a user and at least one is not.
3. Export the CSV for both the current page and all keys.
4. Open the file and check the following:
   • The header has "Assigned User Email" after "Assigned To".
   • Keys with an assigned user show that user's email.
   • Keys without an assigned user have an empty cell.
   • Later columns (Budget Limit, Budget Spent, Budget Reset, Description, Created At) are still aligned with their headers.

# UI
cd ui
pnpm i || npm i
pnpm test || npm test
pnpm build || npm run build

Screenshots/Recordings

Not included. A sample of the exported CSV can be attached if needed.

Breaking changes

• Yes
• No

The new column is inserted in the middle of the CSV, so anything that reads the export by column position will see later columns shift by one. Tools that read by header name are unaffected.

Related issues

N/A

Security considerations

The export now includes user email addresses, which are PII. The data is already available to users who can view virtual keys. Anyone who shares exported files should handle them accordingly.

Checklist

• I read docs/contributing/README.md and followed the guidelines
• I added/updated tests where appropriate
• I updated documentation where needed
• I verified builds succeed (Go and UI)
• I verified the CI pipeline passes locally if applicable

[coderabbitai]

Important

Review skipped

Review was skipped as selected files did not have any reviewable changes.

⚙️ Run configuration

• Source mode: Auto
• Repository: maximhq/bifrost
• Branch: 10-23-feat&#95;add&#95;assigned&#95;to&#95;email&#95;column&#95;into&#95;vk&#95;export
• File: .coderabbit.yaml
• Commit: aa16f49
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Team
• Run ID: dbf6487a-94ed-43f1-b48e-bef68f58c6cd

📥 Commits

Reviewing files that changed from the base of the PR and between d6f4f9e and aa16f49.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Source mode: Auto
• Repository: maximhq/bifrost
• Branch: 10-23-feat&#95;add&#95;assigned&#95;to&#95;email&#95;column&#95;into&#95;vk&#95;export
• File: .coderabbit.yaml
• Commit: d6f4f9e
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Team
• Run ID: f2992bb0-160d-47c4-adf3-85feaf3201de

📥 Commits

Reviewing files that changed from the base of the PR and between 6b53591 and d6f4f9e.

📒 Files selected for processing: 1

• ui/app/workspace/virtual-keys/views/virtualKeysTable.tsx

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 6 remain after this review.

📝 Summary

Summary by CodeRabbit

• Improvements
  • Virtual-key CSV exports now include the assigned user’s email, or an empty value when unavailable.

The virtual-key CSV export adds an Assigned User Email column after Assigned To. Rows use the assigned user’s email, or an empty string when no email is available.

Changes: Virtual-key CSV export

Layer / File(s)	Summary
Add assigned user email column ui/app/workspace/virtual-keys/views/virtualKeysTable.tsx	The CSV header adds Assigned User Email after Assigned To. Each row includes the assigned user’s email, or an empty string when it is unavailable.

Priority: ➖ Normal

Estimated code review effort: 1 (Trivial) | ~3 minutes

Suggested reviewers: akshaydeo

Merge Risk: ⚪ Minimal · up to d6f4f

The export change is ready to merge with no actionable risk identified.

Pre-merge checks: 4 · 1

Failed checks: 1 warning

Check name	Status	Explanation	Resolution
Docstring Coverage		Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

Passed checks: 4 passed

Check name	Status	Explanation
Title check		The title clearly and concisely identifies the main change: adding an assigned user email column to the virtual keys CSV export.
Description check		The description is complete and relevant. It explains the change, affected UI area, manual validation steps, CSV compatibility impact, PII considerations, and breaking-change status. It does not repor…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Description check

Explanation

The description is complete and relevant. It explains the change, affected UI area, manual validation steps, CSV compatibility impact, PII considerations, and breaking-change status. It does not report completed test or build results, and it does not include screenshots, but these omissions are not critical for this small change.

✨ Finishing Touches: 💡 1

📝 Generate docstrings: 💡

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}

[impoiler]

• perf(logstore): add one-pass usage reads for per-entity rollups #8747
• feat(ui): add assigned user email column to virtual keys CSV export #8945 👈 (View in Graphite)
• dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

[danpiths]

Merge activity

• Oct 23, 7:56 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Oct 23, 7:57 AM UTC: Graphite rebased this pull request as part of a merge.
• Oct 23, 7:59 AM UTC: @danpiths merged this pull request with Graphite.