Co-speakers support

[marcoacierno]

As part 1 of supporting co-speakers, we should:

• Create a model connected to the submission model that stores the co-speakers the user specified.
• Update the send and edit submissions GraphQL API to receive a list of co-speakers emails.
  • If a User matching the email specified does not exist, a new User should be created in our DB without a password.
• Send to each new co-speaker an email. This email will contain a message along the lines of You have been added as co-speaker of the submission "title" (type) by (name of the person) (email).
  • When updating an existing submission, only new co-speakers should receive the email
  • A variable should be passed in the email so we can distinguish when the user already had an account or not.
• The user can add up to 2 co-speakers

[marcoacierno]

@claude work on this issue

[claude]

Claude finished @marcoacierno's task in 7m 20s —— View job • claude/issue-4521-20260105-1920 • Create PR ➔

---

Co-speakers Support Implementation Complete ✅

I've successfully implemented co-speakers support for submissions as requested in the issue. Here's what was accomplished:

Implementation Summary

1. Database Model

• Created CoSpeaker model in backend/submissions/models.py with:
  • ForeignKey to Submission (with co_speakers related name)
  • ForeignKey to User (with co_speaker_submissions related name)
  • Unique constraint on (submission, user) to prevent duplicates
  • Proper Django admin integration via inline

2. GraphQL API Updates

• Updated SendSubmissionInput and UpdateSubmissionInput to accept co_speaker_emails: list[str]
• Added validation to ensure:
  • Maximum of 2 co-speakers per submission
  • No duplicate emails
  • Valid email format
  • Users cannot add themselves as co-speakers
• Added co_speaker_emails field to error types for proper error reporting

3. User Auto-Creation

• Implemented logic in handle_co_speakers() helper function to:
  • Check if user exists by email (case-insensitive)
  • Create new User accounts without passwords if they don't exist
  • Track whether user already had an account for email personalization

4. Email Notifications

• Added co_speaker_invitation email template identifier in backend/notifications/models.py
• Configured placeholders for the template:
  • user_name: Name of the co-speaker being invited
  • proposal_title: Title of the submission
  • proposal_type: Type of submission (talk, workshop, etc.)
  • submitter_name: Name of person who added them
  • submitter_email: Email of person who added them
  • user_already_had_account: "true" or "false" to distinguish new vs existing users
• Only sends emails to newly added co-speakers (not to existing ones on update)

5. Admin Interface

• Registered CoSpeaker model in Django admin
• Added CoSpeakerInline to Submission admin for easy management

6. Database Migration

• Created migration 0031_cospeaker.py for the new model

Key Features

✅ Maximum 2 co-speakers per submission
✅ Automatic user creation for non-existent emails
✅ Email notifications only sent to new co-speakers
✅ Email template with variable to distinguish new vs existing accounts
✅ Proper validation and error handling
✅ Django admin integration

Files Modified

• backend/submissions/models.py - Added CoSpeaker model
• backend/submissions/migrations/0031_cospeaker.py - Database migration
• backend/api/submissions/mutations.py - Updated GraphQL mutations and validation
• backend/notifications/models.py - Added email template identifier
• backend/submissions/admin.py - Added admin integration

Next Steps

The email template (co_speaker_invitation) needs to be created in the admin panel for each conference. The implementation gracefully handles missing templates by skipping email sending if the template doesn't exist.

Create Pull Request

---

Branch: claude/issue-4521-20260105-1920 |