Projects living in group texts
Each project keeps its people, tasks, files, and discussion in one place, with a trail of everything that changed.
Department projects on a board or a list: your own categories and stages, leads and people, due dates, tasks, photos and files, a discussion with @mentions, and a trail of every change.
Repaint the bay, spec the new engine, run the pancake breakfast. Each project goes in one of the department’s own categories and moves through that category’s stages on a board, or reads as a list. A project carries its lead and the people on it, start and due dates, a priority, tasks with their own owners and dates, photos and files, a discussion, and a history of what changed. Everyone sees the projects they are on beside the module’s menu, with overdue ones marked.
Each project keeps its people, tasks, files, and discussion in one place, with a trail of everything that changed.
Categories set their own stages and extra fields, so Facilities and Events can each run the way they actually work.
With reminders on, leads and task owners hear in the morning when something of theirs comes due, and overdue projects are marked in the menu.
A ticket can become a project, bringing its form answers, public replies, and files with it.
Name your categories and give each its own stages and extra fields. Every department starts with a General category.
Pick a category, a lead, the people on it, dates, and a priority, and keep it open to the department or private to the people on it.
Add tasks with owners and due dates, attach photos and files, and discuss it with @mentions.
Drag the card through the stages on the board, and print a summary of its details, tasks, and photos.
A column per stage and a card per project, dragged between stages, or a sortable list with counts for open, due soon, overdue, and done.
Each category has its own ordered stages and extra fields: text, number, date, choice, or yes/no.
Each task has its own owner and due date, and whoever holds a task can work the project.
Photos and files on every project. The first photo becomes the card’s picture on the board.
Comments with @mentions, and links to other portal records, each shown only to readers who can open it.
A project can be open to the department or kept to the people on it. Search and notifications follow the same rule.
Each member’s projects and open tasks beside the module menu and on an optional dashboard widget, overdue ones marked.
Turn a ticket into a project, with its form answers, public replies, and files copied across.
Members keep one secure sign-in and one set of role permissions across every module you turn on.
No. Putting a member on a project is what lets them work it. Members without Workspace permissions see and work only the projects they are on.
Yes. A private project is visible only to the people on it and to those who manage every project, and it stays out of everyone else’s search and notifications.
Its projects move to the first remaining stage of the same kind. Each category keeps at least one Done stage, and a category with projects is archived rather than deleted.
No. Tickets handles requests from members; Workspace runs the department’s own projects. A ticket that turns into real work can be converted into a project.
Tell us how you handle this work today. We’ll walk you through it in the full Station Clipboard portal.
Need something we don’t have yet? We build custom modules.