A teammate who needs the same drafts is not the same problem as a listener who should find a finished record. Invite people into a workspace when the catalogue should stay limited to named collaborators; publish an album when the set is meant to be public.
Suno’s 15 October 2026 collaboration note describes shareable workspaces as a library that only invited people can access, for Pro and Premier. It does not document the invite control, the exact permission list, or what happens to songs already marked Public. This article is a decision guide checked on 16 October 2026, not an account test and not a button-by-button walkthrough.
A shared folder is not an album
Three places can hold the same files. They answer different questions.
| Place | Who is meant to see it | Typical job |
|---|---|---|
| Library | You, unless you change a song’s visibility | Daily drafts, takes and unfinished versions |
| Shareable workspace | People you invite, according to the October note | A team catalogue that is not a public release |
| Album | Followers and the public once you publish | A sequenced body of work with a cover and notice |
The January 2025 Workspace help page, still current when checked on 16 October 2026, is about organising your own Create menu: naming a workspace, parking Extends together, and moving songs from the Library. It does not describe invites. Use it for filing. Do not copy those steps as a collaboration procedure.
Individual song links are a third mechanism. Suno’s sharing help says new songs default to Private/Link Only: someone with the URL can open that song, which is not the same as joining a workspace library.
What 15 October actually claims
The release note, read in full, supports only these statements:
- Shareable workspaces let a team share a library of songs.
- Only the people you invite can access that workspace.
- The feature is for Pro and Premier.
- Premier users also get shareable custom models with twice the inputs; that is a separate task, covered in the custom model workflow.
It does not name the invite field, say whether an invitee can generate, download or delete, or promise that unpublished songs stay unpublished after they sit in a shared workspace. If your interface shows an invite control, treat the on-screen labels as the current contract. If it does not, do not invent a sequence from the headline.
Exercise: three roles, one song list
Use this original planning sheet. It is not a tested Suno project.
Imagine a short theme for a product walkthrough: four instrumental beds, two vocal stings, and three rejected takes. Assign the files before anyone is invited.
| Role | Needs to hear | Should not receive |
|---|---|---|
| Composer | All current candidates, including rejected takes | The public album link, until sequencing is finished |
| Editor | The two vocal stings and the chosen beds, labelled by version | Earlier beds that were already discarded |
| Client | Only the four beds in intended order | Rejected takes, stems experiments, or private voice memos |
Write the list as you would a folder name, not as a press release: walkthrough-beds-client-v2. Then mark each file: unpublished draft, already public, or someone else’s song. A workspace is a poor place to park a track you do not own or a memo you never meant a contractor to keep.
Check before you invite
Go through the actual list, not the workspace title.
- Remove practice takes you would not hand to the client.
- Note any song already set to Public; inviting someone into the workspace does not unsay a public page.
- Leave out other creators’ tracks. An album of your own work has that rule on record; a shared folder should follow the same caution even when help text is silent.
- Record who was invited and why, next to the workspace name.
Remix permissions still belong to each song. Enabling Cover or Extend for a teammate is a different switch from workspace membership; check Visibility & Permissions on the tracks that matter.
If you needed a public body of work
Followers, a cover image, and a notification are album jobs. Use the playlist-to-album tutorial when the sequence is ready to be public, including the warning that publishing the album publishes every included song.
If the next step is a download, credits log or destination platform, finish with the publishing checklist. A shared workspace does not replace those records.
FAQ
Does inviting someone publish the songs in that workspace?+
The 15 October 2026 note says only invited people can access a shareable workspace. That is not the same as publishing an album, which makes included songs public. Confirm the current privacy labels in the workspace before adding drafts.
Can a Basic account create a shareable workspace?+
The announcement limits shareable workspaces to Pro and Premier. The older Workspace help page describes personal organisation and does not grant sharing. Check the plan shown in your account.
Is this the Workspace tool launched in January 2025?+
Workspaces as folders have existed since then. The 15 October 2026 note adds sharing a library with invited people. Do not treat the 2025 create-a-folder steps as an invite tutorial.
Is sending a song link the same as sharing a workspace?+
No. Suno's sharing help describes Copy Link and Public visibility for individual songs. A workspace share is a library for people you invite, according to the October announcement.
