Catalog transfers
Move a catalog (tracks, albums and everything attached to them) from one team to another in one step, with the record in both teams' activity logs.
What it is
When a catalog changes hands, an artist moves to a new management org, two labels merge rosters, or you reorganise your own teams, the songs are only half the story. Versions, artwork, project files, release plans, splits and contracts all have to arrive with them, and both sides need a record of what actually moved. Catalog transfers do that in one step: pick the tracks and albums (or the whole catalog), pick the receiving team, and everything attached to those songs moves together.
Nothing is sold or duplicated. The catalog changes owner inside Aden, links keep working, and both teams get the transfer in their activity log.
Using it
Go to your team's settings and open "Catalog transfers". Hit "New transfer", pick the receiving team (one of your own, or any team by its link name), choose the whole catalog or specific tracks and albums, and confirm.
You need to manage both sides: as a team admin, or as an admin of the organisation the team belongs to. That's what makes org-to-org handovers work like team-to-team ones: an organisation admin moves a roster team's catalog to a team in another organisation they manage. For a handover between two separate parties, the receiving side makes you an admin first, then you transfer.
After the transfer, the sending team stays visible on each track as a previous collaborator, so credits and history read correctly, and both teams' activity logs carry the record of what moved.
Agent readiness (Ora / GEO)
Public llms.txt, markdown negotiation, OpenAPI, JSON-LD, and MCP tool listing for AI agents.
iCloud Drive
iCloud is not a connected cloud source like Dropbox or Drive, because Apple exposes no API for it. On the desktop app it is a folder on disk, so team sync can point at it, and the app downloads iCloud placeholder files before touching them.