Skip to main content

Sharing

(v1.0)

info

Public audio can use private or shared Worlds, Orbiters, and Collections.
Audio visibility is the main rule for sharing.

How Sharing and Permissions Work​

plantasia space uses two simple models to control access and collaboration:

  • Audio uses a visibility (audience) model — focused on listening and release permissions
  • Worlds, Orbiters, and Collections use a collaboration privacy model — focused on editing, publishing, and teamwork

Audio Visibility (Audience)​

When you publish audio, you choose who can play and discover it:

  • Private — only you can access it
  • Shared — anyone with the audio link can view it
  • Public — fully public and discoverable

This controls playback and distribution.

Entangled World, Orbiter, and Collection Permissions​

These use a collaboration model to decide:

  • Who can access the entity directly
  • Who can contribute and what role they have

Individual xPlorer Permissions​

When you invite specific xPlorers, you can assign roles:

  • Viewer — can view and experience
  • Publisher — can publish content inside the entity
  • Editor — can edit the entity, publish inside it, and invite other xPlorers

You can also define baseline access for everyone:

  • Restricted — only invited xPlorers can access
  • Anyone with the link — access via link with a selected role

Default roles for general access can be:

  • Viewer
  • Publisher
  • Editor

Who Can Change These Settings​

Inviting people and opening an entity up are two different decisions, so they sit with different people:

  • Owner — everything: invite and remove xPlorers, change their roles, and set General Access
  • Editor — can invite and remove xPlorers and change their roles, but cannot change General Access
  • Publisher and Viewer — cannot change collaboration settings

Editors can bring in another pair of hands, since they already edit and publish the entity. Deciding whether anyone with the link can reach it stays with the owner alone — as does archiving or deleting it.

If a setting is not yours to change, you will see it greyed out with a note explaining why, rather than an error after the fact.

Audio has no collaborator list. Its audience is the owner's to set — see Audio Visibility above.

This model is optimized for collaboration, contributions, and shared creation.

Important Behavior​

  • Public audio can use private or shared Worlds, Orbiters, and Collections
  • Audio visibility controls who can listen and discover the audio
  • Entity privacy controls collaboration rights and direct access

In Practice​

You can:

  • Keep a World private so only you can publish in it
  • Release public audio that uses that private World
  • Let listeners experience it through the audio

Others will not be able to open, edit, or publish inside that World unless you invite them.

Simple Rule to Remember​

Audio controls who listens.
Worlds, Orbiters, and Collections control who collaborates and publishes.

info

Audio = master visibility switch
Entities = collaboration & contribution layer

Downloading Content​

Some audios can be downloaded directly. Downloads are enabled per release by the creator: when publishing or editing an audio, the Enable Direct Downloads option allows listeners to download it.

When direct downloads are enabled, the audio page shows a Download button. It opens a dialog where you choose the version:

  • Compressed (MP3) — a smaller file for everyday listening
  • Lossless (WAV) — full quality for archival use

Released Clips can also offer a video download (original or compressed MP4) from the Clip page — only when the Clip has a captured video, and for two weeks after the capture.

Downloaded files remain covered by the release's Creative Commons license — check the license shown on the content page for what you may do with the file beyond listening.