Uforiya is built around two levels of organisation: projects and tracks. Both have their own collaborators, roles and permissions that work independently of each other. This page explains exactly how everything works so you always know who can do what and why.
Every track on Uforiya must belong to a project. When you upload a track you choose to either create a new project or add it to an existing one, including both projects you own and projects you are an editor on.
You cannot upload a track without assigning it to a project. You can create a new project during upload or add to an existing one you own or edit.
Name, type and visibility are mandatory. Cover image and all other details are optional. Project type must be one of: Single, EP, Album, Mixtape or Playlist.
Title and visibility are mandatory when uploading a track. All other metadata such as featuring artists, BPM and key are optional. If the project is private, the track will be private regardless of the visibility you set.
Whoever uploads a track is its owner, regardless of their role in the project. Uploading to someone else's project does not give them ownership of your track.
BPM and key are detected automatically on upload. You can override either value manually if the detection is incorrect.
Uforiya has collaborators at two separate levels: project level and track level. These are managed independently. Adding someone to a project does not automatically add them to any track, and adding someone to a track does not give them project access.
At both levels, a collaborator is either an Editor or a Listener. The permissions for each role differ between project and track level and are explained in the sections below.
Managed from Project Settings. Only the project owner can manage project collaborators. Project collaborators have access to all tracks in the project regardless of individual track visibility settings. Project editors have the same capabilities as a track editor on every track in the project.
Managed from Track Settings by the track owner. Track collaborators are separate from project collaborators. They can view project collaborators from Project Settings but cannot manage them.
Both track and project collaborators can view project collaborators from Project Settings. Only the project owner can manage them.
Every person in a project has one of three roles. These roles control what they can do within the project.
| Role | Permissions |
|---|---|
| OwnerOwner | Full control. Can invite and remove collaborators, delete the project, change project visibility, edit all project and track data, and upload new versions of any track. There is one owner per project. |
| EditorEditor | Can upload tracks to the project and retain ownership of those tracks. Has the same capabilities as a track editor on all tracks in the project. Can edit some track data as specified in the app. Cannot invite or remove collaborators, delete the project, or change project visibility. |
| ListenerListener | Listen access only. Can stream all tracks in the project but only the current version of each track. Cannot upload, edit or manage anything. |
Collaborators are invited by username or email. You can invite someone who does not yet have a Uforiya account by email; they will receive an invitation to join.
At the track level, collaborators are also either Editors or Listeners. All track editors have the same permissions; there is no permission difference between them at this level.
Each editor on a track is assigned a credit role to document their contribution. Since anyone with access to the track can see all editors and their roles, these serve as credits for the record.
| Role | Permissions |
|---|---|
| OwnerOwner | Full control over the track. Can invite and remove track collaborators, mark a version as current, edit all track data, set track visibility, and remove the track from a project if the project is not owned by them. |
| EditorEditor | Can upload new versions of the track from Track Settings and edit some track data as specified in the app. All editors have the same permissions regardless of their assigned credit role. |
| ListenerListener | Listen access only. Can stream the current version of the track. Cannot upload, edit or manage anything. |
Credit roles are for documentation, not permissions. A producer and an engineer on the same track have identical editing capabilities; the credit role records their contribution to the record, not their level of access.
Versions are the core of Uforiya. Every time an audio file is uploaded for a track it is saved as a new version. Nothing is overwritten. Your full version history is always there.
New versions can only be uploaded from Track Settings. This keeps version history intentional and organised.
The track owner, the project owner, and any project or track editor can upload a new version of a track.
Only the track owner can mark a version as current. This ensures nothing is officially changed without the track owner's sign-off, even if editors can upload new files.
Every version you upload stays on the platform. You can go back to any version at any time. Old versions are never removed when a new one is uploaded.
The number of versions allowed per track is determined by the track owner's plan, not the uploader's plan. See Section 09 for plan limits.
As long as you have not reached your plan's version limit for a track, you can keep uploading new versions. If you reach the limit, you will need to upgrade your plan to continue.
Visibility is controlled at two levels: project and track. The project's visibility sets the boundaries. Track visibility cannot exceed what the project allows.
Only invited collaborators can access the project. All tracks inside a private project are private regardless of their individual visibility settings. No exceptions.
Any Uforiya user with the project link can view the project. When a project is public, each track owner can set their track's visibility independently; some tracks can be private while others are public.
The project owner sets and changes project visibility. The track owner sets and changes the visibility of their own tracks within the bounds of the project's visibility.
Track visibility cannot exceed project visibility. If a project is private, all tracks inside it are private regardless of individual track settings. Making a project public gives each track owner the ability to choose their track's visibility independently.
A Uforiya account is required to access any content on the platform, including public projects.
Track ownership always stays with whoever uploaded the track. There are several situations where a track can be separated from a project and become a standalone single.
If a project owner deletes a project, all tracks uploaded by editors within that project are not deleted. They become standalone projects with the type Single, still owned by the original track owner.
The project owner can remove a track uploaded by an editor from their project. The removed track becomes a standalone Single owned by the original track owner.
A track owner can remove their own track from a project at any time. This applies only when the project is not owned by the track owner. The track becomes a standalone Single under their ownership.
Track ownership never transfers automatically. Ownership transfer is not available in the current version of Uforiya but is planned for a future release.
You must have a Uforiya account to use the platform. This includes accessing public projects; all content on Uforiya is behind an account.
Creating an account is free. The Free plan gives you 25 tracks, 5 versions per track and unlimited collaborators. No credit card required.
Your plan determines how many tracks you can upload and how many versions each track can have. These limits are tied to your account, not to any specific project.
| Plan | Tracks | Versions per track | Collaborators |
|---|---|---|---|
| Free | 25 | 5 | Unlimited |
| Pro | 250 | 10 | Unlimited |
| Premium | 1,000 | 15 | Unlimited |
Your track limit counts every track you upload, regardless of which project it belongs to. If you upload a track to another user's project, it counts toward your limit. If someone uploads a track to your project, it counts toward their limit.
The version limit for any given track is set by the track owner's plan, not the plan of whoever is uploading the version.
We want Uforiya to work for the people who actually use it. If you believe a rule is unclear, unfair, or does not fit how you work, send us an email and we will review it. We cannot promise every rule will change, but every request will be read.
Use the subject line format below so we can route your request correctly. Include your Uforiya username, the section name or number, and describe what you think should be different and why.