Expand Favorites into personal sets with consolidated overview pages

Summary

Expand Favorites into an admin-enabled, personal left-navigation area where users can pin important SimpleChat objects and organize them into named sets. A set is a lightweight personal grouping, not a group, project, workspace, or access boundary.

Clicking a set should open a consolidated set overview page that brings the pinned items together into one useful view while preserving each item's original permissions.

User Value

Users often work around a task, customer, investigation, meeting, deliverable, or recurring workflow that spans several SimpleChat surfaces. Favorites sets would let a user collect the relevant conversations, files, agents, groups, and workspaces in one place without creating a new shared workspace or changing access for anyone else.

Proposed Behavior

• Admins can enable or disable the Favorites feature.
• When enabled, the left navigation includes a Favorites section.
• Users can create named sets under Favorites using a plus action.
• The UI may use a folder-style icon for recognition, but the user-facing term should be set.
• Users can pin supported objects to Favorites generally or to a specific set.
• Favorite sets are personal to the user and are not shareable in the initial design.
• Users can rename, reorder, and remove sets.
• Users can reorder or remove pinned items without deleting the original item.
• Favorite records should store user ownership, item type, item id, display metadata, ordering, set membership, and stale/deleted/access-lost state.
• Favorites must never grant access; every item link, preview, search, or AI summary must respect the original permissions for that object.

Supported Pin Types

Initial supported item types should include:

• Conversations
• Files/documents
• Agents
• Groups
• Public workspaces

Potential future pin types to consider:

• Saved prompts
• Actions/tools
• Saved searches
• Dashboards or exports
• Admin-approved external links

Set Overview Page

Clicking a set should open a consolidated overview page for that set. The page should help the user understand and use the pinned items together rather than simply showing a flat list.

Candidate overview content:

• Header/hero card with set name, optional description, icon/color/logo, and edit controls.
• AI-generated brief for the set based only on content the current user can access.
• Recent activity across pinned conversations, files, groups, and workspaces.
• Conversations section with recent messages, unread indicators, continue-chat actions, and optional conversation summaries.
• Files section with pinned documents, tags/metadata, recently updated files, and open/search actions.
• Agents section with pinned agents, descriptions, model/source context, and start-chat/start-action actions.
• Groups and public workspaces section with quick links and available context.
• Suggested next steps or related items derived from accessible pinned content.
• An optional Ask this set entry point that scopes retrieval and citations to accessible items in the set.
• An unavailable-items area for deleted objects or objects the user can no longer access.

Permissions and Security Requirements

• Favorites and sets are personal navigation/organization metadata only.
• Sets do not create shared membership, shared permissions, or new content access.
• The consolidated overview must filter or omit inaccessible items.
• AI summaries must only use content the current user is authorized to read.
• Stale, deleted, or access-lost references should be visible only as safe placeholders where appropriate.
• Frontend routes must receive sanitized settings data only.

Acceptance Criteria

• Existing issue scope is expanded from a simple favorites hub to personal Favorites sets.
• Admin setting exists to enable or disable Favorites.
• Left navigation shows Favorites only when enabled and available to the user.
• Users can create, rename, reorder, and delete personal sets.
• Users can pin and unpin conversations, files/documents, agents, groups, and public workspaces.
• Users can assign pinned items to one or more sets, or at minimum move items between sets if multi-set membership is deferred.
• Clicking a set opens a consolidated overview page.
• The overview page groups pinned items by type and provides useful actions for each type.
• The overview page includes permission-aware summaries or activity only for content the user can access.
• Deleted or access-lost items are handled gracefully.
• Backend APIs enforce ownership and original object permissions.
• Functional and/or UI tests cover favorite set creation, pinning, unpinning, overview rendering, and permission filtering.
• Documentation and release notes are updated when implemented.

Open Questions

• Should AI-generated set briefs be generated on demand, manually refreshed, or cached?
• Should set branding support uploaded logos, predefined icons/colors, or both?
• Should an item be allowed in multiple sets in phase one?
• Should Ask this set be part of the first implementation or a follow-up enhancement?
• Should the overview page live inside the chat experience, a workspace-style page, or its own route?

Notes

• Preferred terminology: Favorites for the nav section and set for user-created groupings.
• Related existing capabilities: pinned conversations, left-hand navigation, groups, public workspaces, agents, and document/file workspaces.
• This issue intentionally treats Favorites sets as personal organization, not collaboration, sharing, or permission management.