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. Everything else is optional. Supported formats are MP3, WAV, FLAC, AIFF, AAC and M4A. You can upload up to 20 files at once. Each becomes its own track with its own title, sharing the project, genre and visibility you pick.
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. The one exception is a private session, where the host owns every track. See Section 17.
BPM, key, duration and format are detected automatically on upload. You can override BPM and key 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. Private sessions add a third role, Admin. See Section 17.
Managed from Project Settings. Only the project owner can invite, remove or change the role of a project collaborator. Project collaborators have access to every track in the project, and project editors can do anything a track editor can do on those tracks.
Managed from Track Settings by the track owner or the project owner. Track collaborators are separate from project collaborators and only have access to the track they were invited to.
The collaborator list shows who holds which role and who has an invite pending. It is only visible to the owner and to people who were actually invited to the track or project. Someone who arrived through a share link cannot see it.
If you want people to see who worked on a track without showing them the access list, that is what Credits is for. See Section 05.
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 project details, and upload new versions of any track in the project. There is one owner per project. |
| EditorEditor | Can upload tracks to the project and keeps ownership of those tracks. Has the same capabilities as a track editor on every track in the project. Cannot invite or remove collaborators, delete the project, or change project visibility. |
| ListenerListener | Listen access only. Can stream the tracks in the project, current version only. Cannot upload, edit or manage anything. |
Project 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. Private sessions also have an Admin role, who helps the host run the session. See Section 17.
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.
When you invite an editor you also choose what they did on the track: producer, engineer, songwriter and so on. That choice is their credit, and it appears in the track's Credits. It does not change what they can do.
| Role | Permissions |
|---|---|
| OwnerOwner | Full control over the track. Can invite and remove track collaborators, mark a version as current, edit track details and credited artists, set track visibility, manage the share link, and decide whether editors can download. |
| EditorEditor | Can upload new versions and stems from Track Settings, and update BPM and key. All editors have the same permissions regardless of their credit. |
| ListenerListener | Listen access only. Can stream the current version of the track and see its credits. Cannot upload, edit, download or manage anything. |
Credits are for the record, not for access. A producer and an engineer on the same track have identical editing capabilities. The credit says what they did; the role says what they can do.
Every track has a Credits tab listing everyone who worked on it, grouped by what they did. Credits are the liner notes: anyone who can hear the track can see them, including someone who opened it from a share link with no account.
Credits come from three places and they all appear in the same list.
The artist line under the track title. It starts with the person who uploaded the track, and the track owner can add or remove names. A track must always have at least one credited artist, so you can remove your own name only once someone else is credited.
Every editor you invite is credited by what you invited them as. Change their credit in Collaborators and the Credits list updates with it. Listeners are not credited, since they did not work on the track.
The track owner can add anyone by name from the Credits tab, with the role they played. Use this for people who are not on the platform. If they do have an account, invite them as a collaborator instead so they get access too.
On a project page, a track only shows its own artist line when it differs from the project's. If the whole project is by one artist, the header already says so.
Versions are the core of Uforiya. Every time an audio file is uploaded for a track it is saved as a new version. Uploading never overwrites anything. Your full version history is there until you choose to delete a version.
There is no cap on how many versions a track can have, on Free or on Pro. The only ceiling is your storage. See Section 16.
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.
A new version never removes or changes an old one. You can go back to any version at any time.
Open a version in the audio tools, edit it, then either save the result as a new version or replace that version with it. Replacing is the only way a version's file changes, and the previous file is not kept.
The track owner and project owner can delete any version. Editors can delete versions they uploaded themselves. The current version can't be deleted, so make another version current first.
Versions never count as new tracks. A track with twenty versions is still one track.
Stems are the individual parts of a mix: drums, bass, vocals, whatever you want to keep separate. On Uforiya stems belong to a version, not to the track as a whole, so you always know which mix a given set of stems came from.
Open a version in Track Settings and add stems to it. Each stem gets a name and a category so the list stays readable.
When you upload a new version you can bring stems from an earlier one across instead of uploading them again. Nothing is duplicated in storage when you do.
Only owners and editors. Listeners cannot see or download stems, and neither can anyone who opened the track from a share link.
500MB per stem. Stems count toward the storage of whoever uploaded them, same as anything else, except in a private session, where the host pays.
If you upload the same stem file twice to the same track, Uforiya recognises it and links the existing file rather than storing it again.
Every track can have lyrics attached to it. Owners and editors can write and edit them at any time.
The track owner, the project owner, and any editor. Lyrics belong to the track, not to a single version, so they stay put when you upload a new mix.
Owners and editors always can. The track owner decides whether listeners see them, with a switch in Access. It is off by default.
Showing lyrics to listeners does not change who can reach the track. It only decides what the people who already have access can read.
Projects and tracks each have their own visibility, and they are independent of each other. A private project is your workspace; a public track is something you chose to release. You can have both at once.
Only people who were invited can reach it. A private project is not browsable by anyone else and has no share link.
Anyone with the link can listen, with or without an account. A public project also lets anyone with its link browse the public tracks inside it.
This works, and it is the normal way to release one song out of a project you are still working on. The track is reachable by its own link. The rest of the project stays private, and the project itself has no link.
The project owner sets the project's visibility. The track owner sets their own track's. Neither one overrides the other.
Making a track private immediately removes everyone who joined it through a public link. People you invited directly keep their access. Going private does not undo an invitation.
Downloading gives someone the actual audio file, so it is held tighter than listening.
The track owner and the project owner can download any version of a track at any time.
The track owner decides whether editors can download. It is off by default. Turn it on in Track Settings when you want your collaborators to have the files.
Listeners and anyone using a share link can only stream. There is no setting that changes this.
Stems follow the same rule as versions. Only people who can see stems at all (owners and editors) can download them. Private sessions have their own download rules. See Section 17.
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, 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. Transferring ownership to someone else is not available in the current version of Uforiya but is planned for a future release. Private sessions work differently: the host owns every track in them. See Section 17.
Deleting is deliberate on Uforiya, and you will always be asked to confirm. But mistakes happen, and we would rather get your music back than be strict about it.
Only the person who uploaded a track can delete it. A project owner who did not upload it can remove it from their project instead, which turns it into a standalone single rather than destroying it. In a private session the host can delete any track. Admins cannot. You can delete tracks you uploaded only while you are still a member.
Email support@uforiya.com with your username and the name of what you lost. We cannot promise to get everything back, but in most cases we can recover it within 30 days of deletion. After that, assume it is gone.
Deleting a project deletes the tracks you uploaded to it. Tracks other people uploaded survive as standalone singles. See Section 12.
Uforiya has seven audio tools you can use on any file, whether or not it is on the platform: Trim, Fade, Convert, Compress, Pitch, Tempo and Normalize.
Trim, Fade, Convert and Compress work with no sign-up at all. Drop a file in, get it back.
Signing up unlocks Pitch, Tempo and Normalize, raises your daily limit, and lets you send a result straight into one of your projects.
There is a daily cap on how many files you can process. It is higher with an account and higher again on Pro.
Files you put through the tools are not added to your library and do not count toward your storage unless you choose to send the result into a project.
You need one to upload, collaborate, or keep anything in a library. You do not need one to open a share link someone sent you, or to use the four tools listed in Section 14.
Creating an account is free. The Free plan gives you unlimited tracks, unlimited versions, 10GB of storage and unlimited collaborators. No credit card required.
It is open to everyone and free to start. Things will change as we go, and the limits below can move.
There are two plans. Collaboration is on both of them: unlimited collaborators, all seven audio tools, and the full version history, whether you pay or not. What you pay for is room.
| Plan | Tracks | Versions | Storage | Collaborators |
|---|---|---|---|---|
| Free | 25 | Unlimited | 10GB | Unlimited |
| Pro | Unlimited | Unlimited | 1TB | Unlimited |
Everything you upload counts toward your own storage: the original track, every version and every stem, no matter whose project or track it went to. If you upload a version to a collaborator's track, that file is on your storage, not theirs.
The person who picks the file is the person who pays for it. It also means nobody can fill up your storage by uploading large files to your project. The one exception is a private session you host, where you choose to cover everything uploaded to it.
On the Free plan you can add up to 100 new tracks in any 24 hours. It counts every new track you upload, whichever project it ends up in: if you upload to someone else's project it counts for you, and if someone uploads to yours it counts for them. Versions and stems never count, and deleting a track doesn't give the slot back. Pro has no daily limit.
Anything uploaded to a private session counts toward the host's storage, not yours, and never toward your daily track limit. See Section 17.
A track with fifty versions is one track. Only the storage adds up.
Once you reach or go over your storage cap, you can't upload anything new, including to someone else's track, until you free up space or upgrade. Everything already uploaded stays exactly where it is.
Pro is $15/month or $134.99/year, in Canadian dollars. Paying yearly works out to 3 months free. Pro also adds private sessions and daily, weekly and monthly analytics.
A private session is a shared space for studio and camp sessions, where everyone uploads into one place. It is a Pro feature. Whoever creates it is the host.
Every track uploaded to a private session is owned by the host, whoever uploaded it. The person who uploaded it stays credited as its creator.
Every track, version and stem uploaded to a session counts toward the host's storage. Uploading to a session never uses your own daily track limit or storage.
People join through a join link and its password, shared as a link or a QR code. If they don't have an account yet, they can sign up on the way in. Everyone who joins through a link comes in as an editor, which means they can upload music to the session.
The host can make any member an admin. Admins help run and moderate the session, and each admin gets their own join link with its own password. You can only see and manage your own link: view its password, reset it or turn it off. If an admin is removed or moved to editor or listener, their link stops working straight away.
The host can change anyone's role, or remove them from the session, whenever they want.
While you are a member, you can upload new versions of the tracks you created, and delete them. If you are moved to listener, your tracks become read only. If you are removed from the session, you lose access to them, including the ability to delete them.
With Editor full access on, which is the default, editors can listen to and comment on every track in the session. The host can turn it off so editors only reach their own tracks and the ones they are added to. Listeners only reach tracks they are added to.
The host, admins and each track's creator (for their own tracks) can always download. With Downloads switched on in Session settings, editors credited on a track can download it too. Hearing a track through Editor full access does not let you download it.
A locked session takes no new uploads and no new joins. Listening and comments keep working. The host or an admin can lock it at any time. It also locks on its own if the host's Pro ends or their storage is full, and unlocks once they renew or free up space.
The host can make a single track in a session public, which gives it a share link like any other public track. The rest of the session stays private.
If a session moves to a new host, every track in it moves with it.
Uploading to a private session puts the track in the host's hands. You stay credited as its creator, but the host decides who can reach it, whether it can be downloaded and whether it is kept.
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.