Short answer: Threads or channels for a project record. Put the current file, the decision and the next owner in one channel. Basic is 9 USD per paid account a month, or 86 USD a year, with 25 GiB. The trial is 3 days. The iPhone and iPad app is coming soon. The encryption scope is on the security page.
A thread holds one topic. A channel holds the project. The file should live in the place a new person will open first.
Author: BusyVault ·
A thread is a topic. A channel is the job.
Threads keep one question from flooding the room. They fail when the file, the decision and the next owner end up in three threads. Give the project one channel. Use a thread for a single question that will be resolved this week. Use a subchannel when a delivery needs its own lasting home.
Test it with a person who was away
Ask someone who missed the week to find the approved file without help. If they open the right channel first, the structure works. If they have to search three threads and still ask which file is current, move the file to the channel and leave a pointer. workplace communication guide
Open the channel first
Give the project one channel. Use a thread for a question that will die this week. Use a subchannel when a delivery needs its own file for longer than that. Ask someone who missed the week to find the approved file. If they open the channel first and the file is there, the structure works. If they hunt through threads and still ask which file is current, move the file to the channel and leave a pointer in the thread. A thread is a good place for a question. It is a bad place to be the only home of the decision.
Pointers are allowed. Hiding is not.
A thread can hold the question. The channel has to hold the file and the decision, or a pointer that a new person will see first. If the only copy of the approval is three threads down, move it up and leave the thread as a pointer. Subchannels are for a delivery that will still matter next week, not for every reply. Test with someone who missed the week. Their first click should be the project channel. If their first click is a search box and the third result, the structure is making them do archaeology. Fix that before you add another project. Threads are not a failure. Threads as the archive are.
Worked example for this guide
Use “Threads or channels for a project record” on one project that is already late, not as a policy for the whole company. Write the current file name, the decision and the next owner in the same channel before the day ends. A teammate who was away should find that trio without opening the call recording. If they cannot, the article has not been applied yet. Repeat the check the next morning. Count a written handover as done only when the second person opens the right file first.
Files, history and the next owner
On Threads or channels for a project record, keep the file next to the sentence that approved it. Slack documents a 1 GB cap on one upload and, on the Free plan, 90 days of visible history. Those two limits are the public facts this site already cites.
BusyVault bills storage per paid account: 25 GiB on Basic and 100 GiB on Pro. Extra storage is 0.03 USD per GiB a month after you confirm the charge. Basic is 9 USD a month or 86 USD a year. Pro is 30 USD a month or 288 USD a year. One subscription does not cover the team.
The trial is 3 days and 10 GiB. Use it to upload a real file and to search for a decision, not to announce a company-wide move. If the file does not fit or the old decision cannot be found, say so in the channel before you promise the room is the archive.
Where the app runs
BusyVault runs in the browser and can be installed from Chrome or Edge on Windows, macOS and Linux. The Android app is on Google Play and uses the same account. The iPhone and iPad app is coming soon. Enterprise customers can run BusyVault on their own servers under a separate contract. There is no public installer on this site for that path. This page does not claim SOC 2, ISO 27001 or HIPAA.
A check you can finish this week
For Threads or channels for a project record, finish four lines and stop. Line one is the project name. Line two is the channel name. Line three is where the current file lives. Line four is the next owner. Add one rule for meetings: what must be decided live, and what must be written down the same day.
Ask someone who was not on the call to find the file without help. If they open the right channel first, the structure works. If they search three threads and still ask which version is current, move the file to the channel and leave a pointer. Owners and administrators can export a BusyVault backup from workspace or channel settings. After a restore, check the text, the file references and who can open them. Keep the original files until that check passes. Product questions go to the address on the support page.