Skip to content

When a user updates their email address in their main amazee account, that change should automatically be reflected in the Lite LLM system as well. #21

@bonus414

Description

@bonus414

As a Drupal site administrator using the amazee AI provider,

I want to have my account email changes automatically propagated to the amazee AI provider and Light LLM backend,

so that I can ensure consistent identity, permissions, and access across the entire AI integration without needing to reconfigure or reauthenticate.

Objectives
• Maintain identity consistency between the Drupal site and amazee AI infrastructure (including Light LLM).
• Avoid broken integrations or access issues caused by outdated email addresses.
• Ensure amazee receives real-time updates about user identity changes within the Drupal ecosystem for auditability, personalization, and support purposes.

Acceptance Criteria
1. Given a user is authenticated and has access to their profile in Drupal,
When they update their email address in the Drupal user account settings,
Then the new email is automatically propagated to the amazee AI provider and associated Light LLM configuration.
2. Given the email has been updated successfully,
When the user accesses the AI provider configuration screen in Drupal,
Then the updated email is shown and linked to the correct usage data, keys, and limits.
3. Given a backend sync fails during the propagation,
When the system detects this failure,
Then a relevant error log is recorded, a warning is optionally shown in the Drupal UI, and optionally an email alert is sent to site admins or support.
4. Given an updated email is propagated,
When the same user accesses Light LLM capabilities within Drupal (e.g. chat completions, AI generation, etc.),
Then their usage and personalization data are preserved and linked to the new email identity.

Image

Metadata

Metadata

Assignees

No one assigned

    Projects

    Status

    Icebox

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions