Add Organizations to Invitation API Route (And Sync Events)

[ArthurMousatov]

❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

Overview

Following PR #6008, once the invitation model accepts organizations, we'll need to update the invitation querysets and any underlying sync mechanisms to allow for organization usage in invitation flows.

Complexity: Low | Medium | High
Low

Target branch:
unstable

The Change

The invitation queryset and the sync mechanism will need to accept organizations. This may require extensive changes, or may not - the implementation will be driven by CRUD/SYNC tests in test_invitation.py. I also expect the bulk of the organization sync changes to be done on Issue #5967, leaving mostly the invitation queryset changes left.

How to Get There

Issue changes will affect the /invitation/ route

Out of Scope

Frontend work is out of scope on this issue.

Acceptance Criteria

• Invitation Queryset allows the usage of organizations
• Organization invites are correctly synced with create/update/delete events

Testing

• Existing tests / lint pass
• Unit tests to cover new invitation - organization relationship (create, update, delete)
• Unit test to cover invitations with channel & organization set
• Unit test to cover channel invitations with organization role (co-owner)

References

Invitation viewset: https://github.com/learningequality/studio/blob/unstable/contentcuration/contentcuration/viewsets/invitation.py
Sync utility: https://github.com/learningequality/studio/blob/unstable/contentcuration/contentcuration/viewsets/sync/utils.py

AI usage

No AI was used in the creation of this task.

[ArthurMousatov]

@yasinelmi will cover this issue and the implementation. Please assign the issue to him! @marcellamaki