Every playlist has a Public setting. That switch controls who can view the playlist; it does not decide who can edit tracks.
Public vs. Private
| Setting | Who can view it | Can be shared | Can be followed |
|---|
| Public | People who can access public playlists on the BeatPass instance | Yes | Yes |
| Private | Owner and accepted collaborators only | Not as a public share surface | No public following flow |
Where The Setting Appears
BeatPass currently exposes the privacy setting in both places:
- The create or edit playlist dialog, using the Public switch
- The playlist context menu, using Make public or Make private
The form description is: Everyone can see public playlists.
How Privacy And Collaboration Work Together
| Combination | Result |
|---|
| Public + non-collaborative | Anyone with access can view; only the owner edits. |
| Public + collaborative | Anyone with access can view; only the owner and accepted collaborators modify tracks. |
| Private + non-collaborative | Only the owner can view and edit. |
| Private + collaborative | Only the owner and accepted collaborators can view; only those same users can modify tracks. |
Sharing And Context Menus
- Public playlists expose the normal share flow.
- Private playlists are still manageable by the owner, but they are not presented as public shareable destinations.
- Follow and unfollow actions only make sense when the viewer can access the playlist.
Making a playlist private does not turn collaborators into ordinary followers. Accepted collaborators keep access because collaboration is a separate permission path.
