There is no admin interface to manage the song catalog. Admins should be able to review and manage all tracks from a dedicated panel.
Expected behavior
Admin-only route/panel protected by role-based access control.
List all songs with search, filters (uploader, date, status) and pagination.
View, edit metadata of, hide/unpublish and delete any song.
Moderate user uploads (e.g. flag or remove inappropriate/infringing content).
Considerations
Backend endpoints must enforce admin permissions, not only the frontend.
Log admin actions for auditing.
## Summary
There is no admin interface to manage the song catalog. Admins should be able to review and manage all tracks from a dedicated panel.
## Expected behavior
- Admin-only route/panel protected by role-based access control.
- List all songs with search, filters (uploader, date, status) and pagination.
- View, edit metadata of, hide/unpublish and delete any song.
- Moderate user uploads (e.g. flag or remove inappropriate/infringing content).
## Considerations
- Backend endpoints must enforce admin permissions, not only the frontend.
- Log admin actions for auditing.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
There is no admin interface to manage the song catalog. Admins should be able to review and manage all tracks from a dedicated panel.
Expected behavior
Considerations