[yasinelmi]

Summary

Adds Gherkin feature files that cover the core organization functionality built this year end to end: one full lifecycle scenario plus a file per area.

File	Scenarios cover	Related PRs
manage-organizations/organization-end-to-end-workflow.feature	Admin creates an organization, invites an editor and a viewer who accept, moves a channel in, checks the Channels tab and Settings > Storage, members access the channel by role, admin removes the viewer	all of the below
manage-organizations/create-and-edit-an-organization.feature	Empty state, create, required name, Create shortcut on My channels, editing details, read-only details for editors and viewers	#5953, #6080, #6126, #6132
manage-organizations/invite-users-to-an-organization.feature	Invite with each role (Pending …), required email, resend, revoke, sharing hidden from non-admins	#6008, #6039, #6126
manage-organizations/respond-to-organization-invitations.feature	Banner text for each role, accept, decline, cancel declining	#6039, #6126
manage-organizations/manage-organization-members.feature	Users table, role changes, removing a member	#6080, #6126
manage-organizations/access-organization-channels-by-role.feature	Admins and editors can edit content, viewers can only view, removed members lose access, Filter by organization on My channels	#6146, #6132
manage-organizations/move-a-channel-to-an-organization.feature	Offered organizations, uncontested move, Create ticket for contested moves, pending request blocks changes, requestor declines own request, Studio admins move without approval	#6161
administration/admin-migrations.feature	Contested migrations table, empty state, accept, decline, regular users blocked	#6161

Organization storage is already covered by manage-organizations/view-organization-storage.feature (#6291), which this PR leaves unchanged.

UI strings were taken from organizationStrings.js and the components, and the contested-migration rules from viewsets/organization_migration.py.

References

Builds on #5953, #6008, #6039, #6080, #6126, #6132, #6146, #6161 and #6291.

Reviewer guidance

• These are manual-reference specs, like the other files under integration_testing/features/; nothing executes them.
• The scenarios have not yet been walked through against a running Studio, so a step's wording may not exactly match the UI in a few places. Corrections are welcome.
• The invitation accept and decline controls are icon buttons, so those steps refer to them by their tooltips.

AI usage

I used Claude Code to gather the organization PRs, read the related components, strings and viewsets, and draft the scenarios following the integration_testing/features/README.md style guide. I reviewed the scenarios against the code and chose to keep one file per area.

🤖 Generated with Claude Code