Teamwork software brings tasks, dates, knowledge and files together in one place. In teamspace, boards, team calendar, wiki, forum and chat all sit in one application. Every board brings its own wiki, forum and file area, governed by the same user groups.
Three areas
Teamwork bundles the tools a team uses to coordinate its day. Boards hold the work, the calendar the time, wiki and forum the knowledge. All three run in one application, with the same user groups.
Boards
Tasks, tickets, notes and work packages sit as cards on a board and move from column to column by drag and drop.
Team calendar
Appointments, leave, external work and project milestones come together in one calendar, synced with Outlook, Apple and Google.
Wiki & forum
The company wiki versions every page, the forum separates topic areas with their own permissions. Knowledge stays, even when someone leaves the company.
From the Monday stand-up to the Friday review, the week runs through the same areas. No tool switch between appointment, task, documentation and discussion, because everything sits in the same system.
09:00 Team-Stand-Up
Teams-Meeting · versendet
AP 1.2 → In Arbeit
Ticket #4318 angepinnt
Onboarding-Seite ergänzt
Version gespeichert
Frage im Platz „Technik"
2 Antworten · abonniert
Board-Spalte „Fertig"
Dateien · versioniert
Tasks, dates and knowledge interlock, instead of being spread across five apps.
Highlight 1
Board, calendar, wiki, files and forum interlock, instead of being spread across five apps.
Highlight 2
A board comes with its wiki, files and forum. Context sits where the work happens, not elsewhere.
Highlight 3
Who sees what is decided by the permission on the board, the file, the page, not by a tool subscription.
A board is a collection of cards in columns. Which columns it has is decided by the way of working: Kanban for the flow, Scrum for the sprint, pin for the loose collection. The type is not a fixed choice but a column configuration.
Board · Release 2026.2
9 cardsWaiting
In progress
Done
A board in teamspace is more than a column view. In the detail manager, every board carries its own wiki, a forum and a file area. Add to that watchers, permissions and a version history. Knowledge and discussion sit on the board, not in a separate tool.
One view for the whole team: your own appointments, those of colleagues, leave, external work, birthdays and project milestones. Anyone planning a meeting sees the availability of those involved, without having to ask.
Team overview · week 23
5 people
In the wiki the team gathers what otherwise disappears into heads and inboxes: onboarding guides, process instructions, standards. Every page is versioned, every page has its own view and edit rule.
Main topic · onboarding
SearchTarget groups
Teams that switch between chat, storage and calendar today, right across the industries.
Boards for development and support, wiki for documentation, files versioned, alongside project and ticket.
Industry pageMandate boards, shared method knowledge and dates in one place, across locations too.
Industry pageTasks, operations wiki and files bundled per customer, with clear permissions.
Industry pageProject boards, plans and minutes per building project, instead of scattered storage.
Industry pageCampaign boards, briefings and assets in one place, from strategy to production.
Industry pageProject tasks, knowledge and dates bundled, alongside utilisation and billing.
Industry pageCase Study
Hypothetical practical example to illustrate how it works. Concrete figures depend on the starting point, the industry and the implementation and are not guaranteed. A typical migration scenario: an agency with 28 staff, three locations, tasks in a chat app, files in a cloud folder, knowledge in notes, appointments in the email calendar.
Tasks were discussed in a chat app, files sat in a shared cloud folder, processes were written down in private notes, appointments lived in the email calendar. Anyone who wanted to understand the state of a project opened four programs and searched in all four. New staff needed days before they knew where everything was. When people moved on, knowledge left with them.
Boards, calendar, wiki, forum and files sit in one application, governed by the same user groups. Per project, the board carries its wiki, its forum and its file area. Appointments, leave and milestones sit in the team calendar. Anyone still using Microsoft Teams creates Teams meetings straight in the teamspace calendar. Onboarding runs through a wiki main topic that records the first steps in a versioned way.
~3 h/week
less searching across four separate programs
1
login and permission concept for the whole team
stays
knowledge when people move on, in the project wiki rather than in someone's head
All modules
Teamwork belongs to the light edition and is therefore part of every teamspace. Project management, CRM and invoicing build on it, all with the same contacts, staff and permissions.
“Our staff appreciate how simple the system is.”
Scope of functions
The functions of the light layer, grouped by area. All governed by the same user groups.
Comparison
Anyone working today with email, a chat app, a cloud folder and an email calendar knows the gaps between the tools. The table shows what an integrated teamwork layer does differently.
Feature
Email, chat app, cloud folder
teamspace
Intro call
Half an hour is enough to talk through your current tools for tasks, dates and knowledge and to see where the handovers get stuck. You get an honest assessment, not a sales demo.
Permissions
In separate tools, someone maintains their own access for each program: who reads in the cloud folder, who writes in the chat app, who sees the calendar. In teamspace this runs through central user groups, and the permission sits on the individual element.
The permission system is the same as across the whole of teamspace. Once you have set it up for the teamwork areas, you also know it for projects, CRM and documents.
Project context
Boards, forums and files are not islands. They sit on what it is all about: the project, the customer, the record. Anyone opening a project finds the associated board, the project forum and the file directory in the same place.
That is the difference between a collection of separate tools and one application: not the number of functions, but that they sit on the same data. How project management builds on this is set out on the project management page.
Benefits
Boards, calendar and knowledge sit on the same user groups. The figures are scope of functions, not promises.
Kanban, Scrum, pin, plus pin board
Week, month, list, availability
with restore
5 POINT AG, self-funded
When teamwork software has an effect
A teamwork software brings tasks, dates, knowledge and files together in one place. Instead of chat app next to cloud folder next to email calendar, everything sits in one interface, governed by shared user groups.
The need becomes noticeable as soon as a team works dispersed, that is, in the office, the home office and on the move. Then knowledge disappears with the people, because it lives in chat histories or private notes. With growing service businesses, this usually tips between 10 and 25 staff: new colleagues need days before they can take in the scattered tools; when people move on, a gap remains.
teamspace starts here with the light edition. Teamwork is the foundation that can later be extended with project, CRM and invoicing, without data migration between two worlds.
Security
Teamwork data is often sensitive: internal discussions, strategy notes in the wiki, draft contracts in the file area. teamspace processes them in Germany, without management having to worry about the infrastructure.
The contracting party is 5 POINT AG, a German public limited company based in Darmstadt that has been developing teamspace since 1999. With the Microsoft Teams integration activated, meeting data flows into the customer's Microsoft tenant, which we make transparent in the intro call.
Editions
Teamwork belongs to the light edition, the base layer of teamspace. Anyone starting with light has boards, team calendar, wiki, forum and chat right away, plus working time tracking and the HR basics.
The areas grow with you, without the team changing tools: the board where tasks hang today carries the work packages of a project tomorrow. Which edition fits which need is something we clarify in the intro call; the prices are on the pricing page.
Related modules
The light foundation opens the door to the modules that build on it. Three that become important next for growing service businesses.
The board becomes the project plan: Gantt, phases, plan vs actual and contribution margin, up to date daily.
Read moreThe contact becomes the customer record: organisations, records and follow-ups in one place.
Read moreThe task becomes the logged hour: attendance, project time and a digital timesheet with approval.
Read moreGlossary
Terms often used inconsistently, located precisely in the teamspace model.
Intro call
Half an hour to see how your team works together today and where teamspace sensibly brings the scattered tools together. An honest assessment, no sales pressure.
We discuss what your team works with today and whether teamspace sensibly brings tasks, dates and knowledge together. You get an honest first feedback on whether teamspace fits.
