fix: standardize page container layout with no-padding-parent and 100dvh sizing

[impoiler]

Summary

Standardizes the page-level container layout across multiple workspace pages to ensure consistent full-viewport height behavior and uniform padding. Previously, pages used a mix of max-w-7xl, 100vh, and inconsistent padding approaches. This aligns them all to use 100dvh with a 1rem offset and the no-padding-parent class to properly handle the parent container's padding.

Changes

• Replaced max-w-7xl width constraints and 100vh-based height calculations with a unified h-[calc(100dvh-1rem)] approach across audit logs, access profiles, business units, customers, RBAC, teams, and users pages
• Added no-padding-parent class to suppress inherited padding from parent layout containers
• Added explicit p-4 padding at the page level so each view controls its own spacing
• Wrapped the teams page view in a consistent container div (it previously had no wrapper)
• Removed overflow-y-auto from the RBAC page container, deferring scroll behavior to the inner view
• Removed unused parseAsString import from the customers page

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

Navigate to each of the following pages and verify the layout fills the viewport correctly without overflow or unexpected scrollbars:

• /workspace/audit-logs
• /workspace/governance/access-profiles
• /workspace/governance/business-units
• /workspace/governance/customers
• /workspace/governance/rbac
• /workspace/governance/teams
• /workspace/governance/users

cd ui
pnpm i || npm i
pnpm build || npm run build

Screenshots/Recordings

Before/after screenshots showing consistent full-height layout across pages recommended.

Breaking changes

• Yes
• No

Related issues

Security considerations

None.

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

Summary by CodeRabbit

• Style

  • Updated layout and spacing across workspace and governance pages (audit logs, access profiles, business units, customers, RBAC, users, etc.) for improved responsiveness.
  • Adjusted header and container padding in team and virtual key sheets.
  • Refined SCIM page layout with improved scrolling behavior.

• New Features

  • Enhanced virtual key sheet with improved form initialization, provider configuration handling, and MCP client selection UI.
  • Added a layout wrapper to the teams page.

[coderabbitai]

Warning

Review limit reached

@impoiler, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 6 minutes and 41 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 39bf3258-3336-4130-b61d-0ef7453a1692

📥 Commits

Reviewing files that changed from the base of the PR and between d99a1d8 and ffefed9.

📒 Files selected for processing (12)

• ui/app/_fallbacks/enterprise/components/user-groups/teamsView.tsx
• ui/app/workspace/audit-logs/page.tsx
• ui/app/workspace/governance/access-profiles/page.tsx
• ui/app/workspace/governance/business-units/page.tsx
• ui/app/workspace/governance/customers/page.tsx
• ui/app/workspace/governance/rbac/page.tsx
• ui/app/workspace/governance/teams/page.tsx
• ui/app/workspace/governance/users/page.tsx
• ui/app/workspace/governance/views/teamSheet.tsx
• ui/app/workspace/scim/page.tsx
• ui/app/workspace/virtual-keys/views/virtualKeyDetailsSheet.tsx
• ui/app/workspace/virtual-keys/views/virtualKeySheet.tsx

📝 Walkthrough

Walkthrough

This PR standardizes container layouts to full-width padded viewport-height wrappers across workspace/governance pages, removes an extra wrapper in TeamsView while adding one in GovernanceTeamsPage, adjusts sticky SheetHeader padding, and performs a broad refactor of the Virtual Key sheet (form defaults, submit normalization, provider UI, and MCP client UI).

Changes

Page Layout Standardization

Layer / File(s)	Summary
Governance page layout updates ui/app/workspace/governance/access-profiles/page.tsx, ui/app/workspace/governance/business-units/page.tsx, ui/app/workspace/governance/users/page.tsx, ui/app/workspace/governance/rbac/page.tsx	Access Profiles, Business Units, Users, and RBAC pages replace centered max-w-7xl containers with full-width, padded, viewport-height layouts using no-padding-parent and h-[calc(100dvh-1rem)] classes.
Workspace audit logs and customers layout updates ui/app/workspace/audit-logs/page.tsx, ui/app/workspace/governance/customers/page.tsx	Audit Logs and Customers pages update container styling to match the new layout pattern. Customers page also pulls parseAsInteger and useQueryStates directly from nuqs and reorders imports.
SCIM page layout with ScrollArea ui/app/workspace/scim/page.tsx	SCIM page wraps SCIMView in a ScrollArea component with full sizing and viewport-height calculation, moving centering and max-width styling to an inner container.

Teams Components Structure and Styling

Layer / File(s)	Summary
TeamsView and GovernanceTeamsPage refactoring ui/app/_fallbacks/enterprise/components/user-groups/teamsView.tsx, ui/app/workspace/governance/teams/page.tsx	TeamsView removes its outer layout <div> wrapper around TeamsTable; GovernanceTeamsPage adds a wrapper <div> with no-padding-parent styling and data-testid="teams-view" around TeamsView. parseAsSafeString import is regrouped.
TeamSheet header padding ui/app/workspace/governance/views/teamSheet.tsx	SheetHeader horizontal padding is split between outer container (px-0) and sticky inner header (headerClassName includes px-8), preserving sticky positioning and background styling.

Virtual Key Sheet Form and UI Refactoring

Layer / File(s)	Summary
Form initialization and provider config normalization ui/app/workspace/virtual-keys/views/virtualKeySheet.tsx	Provider config rate_limit fields are explicitly mapped to token_max_limit, token_reset_duration, request_max_limit, and request_reset_duration in form defaults. Budget entries default reset_duration to "1M". Submit handler calls normalizeProviderConfigs with current form provider configs and existing VK configs.
Entity assignment and combobox options ui/app/workspace/virtual-keys/views/virtualKeySheet.tsx	Update and create payload generation sets team_id/customer_id using trimmed/non-empty checks and maps "none" to null. Combobox options include "Assign to Team/Customer" entries only when teams/customers are available.
Sheet header and provider UI rendering ui/app/workspace/virtual-keys/views/virtualKeySheet.tsx	Sheet header padding adjusted. Provider UI sections refactored: provider labels/placeholders, allowed/blocked model multiselects use wildcard ("*") semantics, allowed-key descriptions handle wildcard expansion, react-select option rendering updated, and provider budget lines default missing reset_duration to "1M".
MCP client configurations and details sheet styling ui/app/workspace/virtual-keys/views/virtualKeySheet.tsx, ui/app/workspace/virtual-keys/views/virtualKeyDetailsSheet.tsx	MCP client configurations UI is rewritten: shows default-available notice, add-client dropdown excludes already-configured clients and shows enabled-tool counts, renders tools table with wildcard/deduping behavior and selection collapse/expand logic. Virtual Key details sheet updates SheetContent and inner body padding to align with header spacing.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

Possibly related PRs

• maximhq/bifrost#3675: Also modifies ui/app/workspace/virtual-keys/views/virtualKeySheet.tsx (layout changes vs. this PR's larger provider/UI refactor).
• maximhq/bifrost#3757: Overlaps on teams area edits for teamsView.tsx and related teams UI changes.

Suggested reviewers

• akshaydeo
• danpiths

"A rabbit hums a layout tune:
Full-width fields beneath the moon,
Teams unwrapped, headers snug and tight,
Virtual keys now dance in light,
MCP tools lined up just right."

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main refactoring effort: standardizing page container layouts using no-padding-parent class and 100dvh sizing across multiple pages.
Description check	✅ Passed	The PR description comprehensively covers the summary, changes, testing instructions, and type of change, though it lacks before/after screenshots despite recommending them.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 06-04-fix_governance_pages_layout

---

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

[impoiler]

• fix: broaden Mantle model matching to all gpt variants #4091
• test: remove TestCollectApplicableGovernanceIDs_UserScopedModelConfigs #4090
• feat: add business unit CRUD, team assignment, and governance endpoints to OpenAPI spec #4082
• feat: add inline loading shell to #root before React mounts #4063
• fix: reduce FTS index left() cap from 800k to 250k chars to stay within tsvector limit #4057
• feat: add alias column to materialized view and filter support #4078
• feat: add "View logs" menu item to customer, team, and virtual key tables #4073
• feat: extract BudgetDisplay component with progress bar and tooltip #4055
• feat: add clickable links for routing rule, selected key, virtual key, and prompt in log detail views #4054
• fix: standardize page container layout with no-padding-parent and 100dvh sizing #4046 👈 (View in Graphite)
• fix: add colored tooltip values and subtle cursor highlight to dashboard charts #4044
• feat: add customer detail sheet and remove inline usage section from customer sheet #4026
• fix: replicates vk hierarchy flow for ghost nodes reconcilation #4088
• feat: supports multiple customers logs and usage tracking #4066
• fix: fixes virtual key model configs UI #4052
• fix: fixes cascade deletes for model configs #4051
• feat: adds support for multiple team and bu units in logstore #4041
• feat: adds team budget and rl collection exporters #4040
• dev

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

[CLAassistant]

All committers have signed the CLA.

[coderabbitai]

♻️ Duplicate comments (1)

ui/app/workspace/virtual-keys/views/virtualKeySheet.tsx (1)

1922-1937: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

**

Replace index-based React keys in MCP dropdown/table (virtualKeySheet.tsx)

SelectItem and MCP table TableRow are keyed with index (key={index} and key={`${config.mcp_client_name}-${index}`}), which can remount rows/options when ordering changes.

Suggested fix

-                                  .map((client, index) => {
+                                  .map((client) => {
@@
-                                      <SelectItem
-                                        key={index}
-                                        value={client.config.name}
-                                      >
+                                      <SelectItem
+                                        key={client.config.name}
+                                        value={client.config.name}
+                                      >
@@
-                                  <TableRow
-                                    key={`${config.mcp_client_name}-${index}`}
-                                  >
+                                  <TableRow key={config.mcp_client_name}>

MCP SelectTrigger/MultiSelect in this section also lack data-testid (only the delete button has one), which matches the already-existing data-testid concern.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@ui/app/workspace/virtual-keys/views/virtualKeySheet.tsx` around lines 1922 -
1937, The SelectItem and MCP TableRow are using unstable index keys (key={index}
/ key={`${config.mcp_client_name}-${index}`}) which can cause remounts when
order changes; update those components to use stable unique identifiers instead
(e.g., use client.config.name or a unique client ID for SelectItem and use
config.mcp_client_name or a unique row id for TableRow) and remove index-based
keys; additionally add data-testid attributes to the SelectTrigger and
MultiSelect elements (matching existing test-id patterns) so tests can reliably
target the dropdown components.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Duplicate comments:
In `@ui/app/workspace/virtual-keys/views/virtualKeySheet.tsx`:
- Around line 1922-1937: The SelectItem and MCP TableRow are using unstable
index keys (key={index} / key={`${config.mcp_client_name}-${index}`}) which can
cause remounts when order changes; update those components to use stable unique
identifiers instead (e.g., use client.config.name or a unique client ID for
SelectItem and use config.mcp_client_name or a unique row id for TableRow) and
remove index-based keys; additionally add data-testid attributes to the
SelectTrigger and MultiSelect elements (matching existing test-id patterns) so
tests can reliably target the dropdown components.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: fcfc00c5-0371-4a79-b809-87233d256671

📥 Commits

Reviewing files that changed from the base of the PR and between 3905d3b and d99a1d8.

📒 Files selected for processing (12)

• ui/app/_fallbacks/enterprise/components/user-groups/teamsView.tsx
• ui/app/workspace/audit-logs/page.tsx
• ui/app/workspace/governance/access-profiles/page.tsx
• ui/app/workspace/governance/business-units/page.tsx
• ui/app/workspace/governance/customers/page.tsx
• ui/app/workspace/governance/rbac/page.tsx
• ui/app/workspace/governance/teams/page.tsx
• ui/app/workspace/governance/users/page.tsx
• ui/app/workspace/governance/views/teamSheet.tsx
• ui/app/workspace/scim/page.tsx
• ui/app/workspace/virtual-keys/views/virtualKeyDetailsSheet.tsx
• ui/app/workspace/virtual-keys/views/virtualKeySheet.tsx

[akshaydeo]

Merge activity

• Jun 5, 2:00 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jun 5, 2:13 PM UTC: @akshaydeo merged this pull request with Graphite.