Feature
Being useful in four teams should not mean opening four sets of applications.
The people who carry the most context across an organisation are the ones punished most by tools organised around containers. Every morning is a tour: this board, that folder, those threads, in case something moved.
Why it matters
This is the question underneath the licence decision.
What kills a platform change is rarely licensing or migration. It is that six months later people are not using the replacement, so work quietly leaks back out into private chats, personal cloud folders and a spreadsheet nobody else can see.
An organisation does not buy adoption features. It buys the absence of the risk that nobody adopts the thing. That is what this part of TeamHub is for, and it is why it appears late in the argument rather than first: it is the answer to the objection, not the opening offer.
How it works
The work comes to the person.
Two screens sitting above the teams rather than inside one of them, reading across every team a person belongs to.
- My Work lists everything currently waiting on that person: a decision needing their approval, a file review, a Deck card assigned to them, a service request they raised or one their team has to answer. Each row says which team it came from and why it is on the list.
- What’s new shows what changed since they last looked, across every team at once, so coming back from a week away is one screen rather than six.
- Acting from the row writes back to the source. Approving a decision approves it in Decisions. Completing a task completes the Deck card. Nothing is a copy, so nothing can disagree.
- Ordering by urgency rather than by team, because a person does not experience their week as a set of teams.
Who benefits, and what stays where it is
Who benefits
- People in several teams, which in most organisations is everybody senior enough to be a bottleneck.
- Approvers, who stop being chased because the thing waiting on them is on their own screen.
- Service teams, whose queue reaches the people who answer it rather than sitting on a page nobody opens.
- Anyone coming back from leave, who gets one catch-up instead of six.
What stays where it is
- Deck keeps the card. My Work shows it and writes back to it.
- Files keeps the document. A review points at the file where it lives.
- Decisions keeps the decision. Approving from My Work is the same act as approving on the team page.
The limits
What this is not.
- It is not a personal task manager. There are no private lists, no personal projects and no notes. It shows what other people and other teams are waiting on, which is a narrower and more useful thing.
- It is not a notification centre. Nextcloud already has one. My Work is a queue of things that need doing, not a log of things that happened.
- It does not reach outside Nextcloud. It gathers from TeamHub and the Nextcloud applications it integrates with, not from your e-mail or a third-party tracker.
Community or licensed
My Work and What’s new are licensed modules. They are not part of the free base application, and older material describing the personal layer as free is out of date.
Keep reading
Decisions
The thing most often waiting in My Work, and the reason the queue is worth opening.
How Decisions worksInternal services
Requests that arrive in the requester’s queue and the answering team’s, at the same time.
Read the use casePricing
What Community includes and what a licence adds.
View pricingWorried nobody will use it?
That is the right worry, and it is the one this part of the product exists to answer. Let us show you what a real person’s Monday looks like.