How it works
It installs into the Nextcloud you already run.
TeamHub is an application from the Nextcloud App Store. It reads the Teams your organisation already has, gives each one a page, and shows the applications that team already uses in the context of that team. There is nothing to migrate and nothing to move.
Huub’s shortcut
Think of TeamHub as a context layer. Your Nextcloud apps keep doing what they already do. TeamHub brings the right parts together around the team responsible for the work.
Step one
A team is described once.
Naming a team and choosing what it is for provisions its chat room, its folder, its calendar, its board and the modules it needs. A rollout that would otherwise stall on forty teams built by hand is one form, or one CSV file with a dry run before anything is created.
Step two
The team gets one page.
Everything that team is responsible for, on one screen, arranged by whoever is looking at it.
- A tab bar across the top, carrying the team's Talk room, its folder, its calendar, its board, its Collective and any other URL somebody adds. Each person orders their own tabs.
- A message stream for announcements, questions and polls that need to persist rather than scroll away.
- Widgets the team chooses: upcoming tasks, recent decisions, presence this week, project health, budget and time.
- An activity timeline covering the last 30 days of files, events, decisions and card movement, scoped to that team. A new member catches up by reading rather than by being briefed.
Step three
The applications you already run stay exactly as they are.
This is the part worth being precise about, because it is the difference between an addition and a migration.
| The application | What stays there | What TeamHub does |
|---|---|---|
| Nextcloud Talk | Every conversation, in full | Shows the team's room in the team, so nobody has to find it |
| Nextcloud Files | Every document and every permission | Shows the team folder in the team, as itself, not as a copy |
| Nextcloud Calendar | Every event | Shows the team calendar, and writes each person's presence into their own |
| RoomVox | Every event | Book and manage rooms for your meetings. |
| Nextcloud Deck | Every card and board | Reads across the boards, shows what is due, and writes changes back to the card |
| Collectives | Every page | Shows the team's Collective alongside its other tabs |
| IntraVox | Every page | Shows the team's pages. |
Follow one Deck card to see the shape of it. A task is created in Deck and lives there. It appears on the responsible team's page, because that team owns the board. It appears in My Work for whoever it is assigned to, because that person needs to act on it. Marking it done in any of those three places changes the card in Deck, because the card in Deck is the only copy.
Step four
What TeamHub adds, because nothing else provides it.
Four things a Nextcloud does not have on its own, each with its own page.
Decisions
A proposal, a category that routes it to the right approver, a recorded reason and an append-only trail. The reasoning survives the people.
How Decisions worksPersonal work
My Work and What’s new: everything waiting on one person, and everything that changed, across every team they belong to.
How personal work worksServices
A catalogue of what the organisation offers, each service naming the team that answers it and the response time to expect.
How Services worksPresence
A working location per half day, collected into a team week and written to each person’s own calendar.
How Presence worksProjects
Phases, the Project Compass, milestones tied to Deck cards, budget and time per workstream, and a live health signal.
How Projects worksEverything else
Custom tabs for any URL, modules enabled per team, bulk creation and export, and an open integration API.
See all featuresWhere the data lives
Inside the Nextcloud you control.
- Team content stays in your Nextcloud. TeamHub stores its own data in your Nextcloud database, alongside everything else on the instance.
- There is no hosted TeamHub. No separate platform to sign up to, and no account with us that your teams depend on.
- The application never contacts us. Not to validate a licence, renew one, count seats or report compliance. An air-gapped deployment is a supported deployment.
- Telemetry is decided by licence state. An unlicensed instance sends one anonymous aggregate a day. Any active licence, including a trial, switches it off. There is no toggle, because the licence already answers the question.
The open-source base is published under AGPL-3.0, so the code can be read and audited independently of any commercial relationship, and it remains available whatever happens to the company.
What telemetry does and does not contain is written out in full, field by field, rather than summarised.
For the technical evaluator
The detail this page deliberately leaves out.
Requirements, installation, configuration, permission boundaries and the integration API belong in the documentation rather than on a page written for somebody deciding whether to look further. Everything is public.
- Requirements. Nextcloud 33 to 35, PHP 8.1 to 8.5.
- Install. From the Nextcloud App Store, like any other application.
- Source and issues. On GitHub, under AGPL-3.0.
- Documentation. Configuration, permissions, the API and the administrator guide are in the docs.
See it against your own setup.
Tell us which Nextcloud applications your teams actually use and how they are organised. We will show you what TeamHub would change and what it would leave alone.