Product
What Forjwell One does.
Six things, each done properly. Deliverable review, project boards, files, chat, permissions and a client portal — one product, one sign-in.
01 · Review & approvals
Every version kept. Every approval pinned.
A deliverable is sent to the client as a version. The next version sits beside it — nothing is ever overwritten. Comments live on the version they are about, a change request is a normal, expected step, and an approval is recorded against the checksum of the exact file the client saw.
- Versions are never overwritten
- Approvals pinned to a checksum
- Change requests and comments per version
02 · Project boards
Milestones hold cards. Cards hold tasks.
The plan for a project lives on one board. Milestones are the big steps, cards are the pieces of work inside them, and tasks are the things someone actually ticks off. Everyone on the project looks at the same board.
- Milestones → cards → tasks
- One board per project
- Seen by the team and the client alike
03 · Files
Attached to the project. Nowhere else.
Files are attached where the work is — to the project itself, or to a milestone, a card or a task on its board — so they are found by the people on that project and not by anyone else. No shared drive to tidy.
- Attachments scoped to a project
- Found next to the work they belong to
- Visible only to the people on that project
04 · Chat
The conversation, next to the work.
Direct messages, groups, channels and a room for every project. Threads keep a discussion in one place; a mention brings the right person into it. The decision and the deliverable it is about are never in two different tools.
- DMs, groups, channels, project rooms
- Threads and mentions
- One place for the whole project
05 · Permissions
Set per person, not per title.
What someone can see and do is set for that person. A designer who should approve can; a client contact who should only review does. Nobody has to be given more than they need to do their part.
- Per-person permissions
- Review, approve, board and file rights kept separate
- Nobody holds more than they need
06 · Client portal
A client sees their projects. Nothing else.
The team works across every project; a client signs in and sees only theirs. Same product, same board, same versions — with the door to everyone else’s work simply not there.
- Each client sees only their own projects
- Same versions, boards and files as the team
- Accounts created by your project manager