8000 Enhance monthly assistants CSV with granular classification data from new sharing framework · Issue #13103 · dust-tt/dust · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Enhance monthly assistants CSV with granular classification data from new sharing framework #13103
Open
@dust-agent

Description

@dust-agent

From: lena@dust.tt
Context: Customer feedback on missing granular assistant classification in monthly reports

Background

After the migration to the new assistant sharing framework (April 2025, migration 20250429_update_agent_scopes.ts), the monthly reports "assistants" CSV only shows simplified "settings" values (published/unpublished) instead of the richer classification data now available.

Before migration: Settings showed workspace/published/private distinctions
After migration: Settings only shows published/unpublished (visible/hidden scope mapping)

Customer Impact

Clara from Brevo (and likely other customers) relies on the monthly assistants report to:

  • Identify which assistants should be moved to Company folder based on usage
  • Understand assistant governance and permissions
  • Make data-driven decisions about assistant lifecycle management

The simplified "settings" column no longer provides enough granular information for these use cases.

Proposed Solution

Enhance the monthly assistants CSV export to include additional columns that leverage the new classification system:

New columns to add:

  1. tags - Comma-separated list of tag names (e.g., "Company,Marketing,Beta")
  2. has_company_tag - Boolean indicating if assistant has the "Company" tag
  3. editor_count - Number of users with edit permissions
  4. scope - Raw scope value (visible/hidden) for transparency

Keep existing:

  • settings column - Current published/unpublished mapping for backward compatibility

Technical Implementation

The data is readily available in:

  • agent_configurations.scope for raw visibility
  • agent_tag_relations + tags tables for tag information
  • group_agent_relations + groups tables for editor counts

Current implementation in getAssistantsUsageData() function in workspace_usage.ts already has scope mapping logic that can be extended.

Expected Outcome

Customers would have access to the same (and better) granular assistant classification data they had before the migration, enabling them to:

  • Continue existing reporting workflows
  • Take advantage of the new tag-based classification system
  • Make informed decisions about assistant management and governance

Front logo Front conversations

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0