User Story: Add Admin Page for Adjusting Prompt Parameters

[BradleyCharles]

Admin User Story

Title: Admin Page for Adjusting Prompt Parameters

• As an administrator of the Opportunity Center chatbot
• I want a secure admin page where I can view and adjust prompt parameters (temperature, max tokens, system role instructions, fallback responses)
• So that I can fine-tune chatbot behavior for different audiences without redeploying code.

Acceptance Criteria:

• Admin login required (role-based access control).
• Parameters displayed with clear labels, tooltips, and default values.
• Changes can be saved, validated, and applied immediately (with rollback option).
• Audit log tracks who changed what and when.
• Parameters persist across sessions and are version-controlled.

---

Admin Figma Wireframe

---

Admin UI Dev Tasks

Sprint 1: Foundation & Layout

• Configure admin panel route (/admin/prompts) in frontend router.
• Implement role-based access control.
• Build sidebar navigation (Dashboard, Prompt Settings, Logs, User Management).
• Set up base layout with responsive grid and design system integration.

Sprint 2: Prompt Parameter Form

• Create form components for parameters (slider, numeric input, text area, text input).
• Add tooltips/help icons for each parameter.
• Fetch and display current parameter values from backend API.
• Client-side validation (temperature range, token limits, required fields).

Sprint 3: Actions & Controls

• Implement Save Changes button → API call + success/error toast.
• Implement Reset to Defaults button → reload default values.
• Implement Rollback button → restore last saved version.
• Add confirmation modal before saving changes.

Sprint 4: Change History & Feedback

• Build change history table (parameter, old value, new value, admin, timestamp).
• Add pagination/scroll for long history.
• Highlight most recent change.
• Integrate with backend audit log API.

Sprint 5: Polish & Testing

• Apply consistent styling (colors, typography, spacing).
• Ensure WCAG 2.1 AA accessibility compliance.
• Responsive layout for desktop/tablet.
• Unit tests for form components.
• Integration tests for save/reset/rollback flows.
• Accessibility tests (screen reader, keyboard navigation).