Share files, deliver transcripts, send review assets. Every one is ready to run, and you can adjust it in plain language.
Email folder owners the locations of matching project files.
You can review marked extra copies and their locations before handing a shared folder to another team.
Create approved project folders by ID and share their links with requesters.
Your team can find new project work in a shared folder named by your rules, with its link on the project row and in the requester's chat.
Give project leads a folder link when a job is awarded.
Your project lead gets a construction project folder and its chat link after an award announcement, with any code or access questions called out.
File shared project files and flag uploads needing a decision.
Your project folders fill with clearly named work files, while unclear uploads stay in intake for your coordinator to review.
Create missing project folders and send coordinators the links.
Your team gets new project folders and required sections, plus a chat update on names or owners that need a decision.
Post linked project files to team channels and confirm each share.
Your team gets the file in the named channel with the requester's note. The requester gets a link or a clear reason it could not be shared.
Set up project folders and flag gaps in handoff details.
Your project handoff task points to a folder with the right Agile or PRINCE2 phases, while your lead sees what details still need attention.
Merge project PDFs and link the packet on its task.
Your reviewer gets a single PDF in the order you set, with the finished packet attached and linked on the project task.
Put checked PDFs on the tasks that hold their HTML drafts.
Your reviewer finds the checked PDF beside the HTML draft on the task, or a note explaining what needs fixing.
Link verified project folders to the delivery schedule.
Your new projects get a standard folder structure and a link on the delivery schedule, or a clear issue for the coordinator to resolve.