Skip to content

docs(budcustomer): add Customer Dashboard portal guide#1181

Open
jithinAB wants to merge 1 commit intomasterfrom
codex/document-customer-dashboard-portal
Open

docs(budcustomer): add Customer Dashboard portal guide#1181
jithinAB wants to merge 1 commit intomasterfrom
codex/document-customer-dashboard-portal

Conversation

@jithinAB
Copy link
Contributor

Motivation

  • Provide a single, customer-facing reference for the Customer Dashboard experience covering discovery, observability, billing, API keys and project workflows.
  • Capture UI patterns used in the app (sidebar, drawers, tabs, filters, copy/download actions) and mirror the style and structure used by existing docs such as docs/models/models.mdx.

Description

  • Add a new documentation page at docs/customer-dashboard/customer-dashboard.mdx describing the portal, USPs, features, how-to guides and FAQ.
  • The document explains key UI flows and components (Models catalog and drawer tabs, Playground iframe, Logs metrics/requests, Observability detail, Usage & Billing, API Keys, Projects, Audit) and details filters, search, buttons, tabs and drawer actions.
  • This is a documentation-only change with no code, infra, or runtime modifications.

Testing

  • No automated tests were executed because this is a documentation-only change and does not affect runtime code or services.
  • Recommended pre-merge checks (not executed here): run pre-commit run --all-files, frontend checks npm run lint / npm run typecheck in affected frontends, and validate docs build if your CI includes a docs staging step (e.g., site build).

Codex Task

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @jithinAB, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the customer-facing documentation by introducing a dedicated guide for the Bud Customer Dashboard. Its purpose is to provide a single, comprehensive reference point for users to understand and effectively utilize the portal's capabilities, ensuring a consistent and guided experience across all features.

Highlights

  • Comprehensive Customer Dashboard Guide: Introduces a new documentation page for the Bud Customer Dashboard, detailing its features, unique selling propositions, and how-to guides for various functionalities like model discovery, observability, usage tracking, API key management, and project workflows.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a comprehensive and well-structured documentation page for the Customer Dashboard. The new guide is detailed, clearly written, and accurately reflects the features present in the application code, following the style of existing documentation. I have provided a few minor suggestions to enhance consistency in terminology throughout the document. Overall, this is an excellent and valuable addition.


#### 3.4.1 Metrics tab

- View-by segmentation (Model, Project) with time-range selection.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For consistency within this document, please use 'time range' (unhyphenated) instead of 'time-range'. This will align with other mentions like 'date range' on line 81.

- View-by segmentation (Model, Project) with time range selection.


- Summary cards for total spend, total tokens, and total requests against quotas.
- Current plan visibility with billing period metadata.
- Project and time-range selectors (1d/7d/30d/90d).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For consistency with other parts of the document, please use 'time range' instead of 'time-range'.

- Project and time range selectors (1d/7d/30d/90d).


- Summary cards for total events, failed actions, and resources modified.
- Search by resource name/user/ID, action filter, resource filter, and date range filter.
- Clear filters control and export-to-CSV action.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

To maintain consistency with other descriptions in this document (e.g., 'Export (CSV) actions' on line 84), please consider rephrasing 'export-to-CSV action'.

- Clear filters control and Export (CSV) action.

@sanu17 sanu17 self-requested a review January 22, 2026 12:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants