Highlight 1
Every card is a real record
Tickets, work packages, invoices or contacts sit on the board as cards, not as a retyped note. Changing the status of a card means changing the record itself.
Boards in teamspace: steer tickets, tasks and invoices on one board.
A board in teamspace is a view on real records, not a second card wall next to the system. Tickets, work packages, invoices and contacts sit on the same board and are steered through freely chosen columns and rows. Private as a personal overview, shared as steering for the team.
At a glance
What sets a teamspace board apart from a card wall.
Three properties that make the difference in daily use.
Highlight 2
Columns and rows freely chosen
Columns map the status, rows the owners, accounts or priorities. You set both axes per board and adjust them later.
Highlight 3
Private or shared per board
A board steers a team or simply serves you as a personal pinboard. Who sees what is governed by the same user groups as in the rest of the system.
Card and record
A card is the record itself, not a copy of it.
A board in teamspace is a view on existing records, not a note tool of its own. A card is almost always a real record: a ticket, a work package, an invoice or a contact. The board only shows where that record currently stands.
- Change the status: whoever drags the card into another column changes the status of the original.
- Attach a file: it hangs on the record itself, not on a separate copy.
- Log hours: on a work package they land where they belong, in the project.
So every record lives once. The board is one of many possible views on it, not a second place where the same information ages apart.
One record, several boards
A record sits on several boards at once.
The same ticket appears on the support team's board, on the customer board and on your personal pinboard. It stays one record; whoever changes the status on one board changes it on all of them.
Ticket #4711 · printer down
one record · lives once
Support team board Column · In progress
Ticket #4711
In progress the support team works it
Customer SLA board Column · open
Ticket #4711
In progress the customer sees the same status
My pinboard Priority · Top
Ticket #4711
In progress the manager keeps an eye on it
One record, on every board. Move the card on one, and the status changes on all.
How a board comes about
From the first record to visible steering.
- 1
Create a board
Name, type (kanban, scrum or pin) and the question of private or shared. A new board takes a few clicks.
- 2
Set columns and rows
Columns map progress, for example Waiting, In progress, Done. Rows group by owners, accounts or priority. Both axes can be adjusted at any time.
- 3
Bring records onto the board
Pick an element from the CRM, service desk or project structure, or fill a board automatically with the open tasks of a project, directory or employee.
- 4
Move and filter cards
Cards travel via drag and drop between columns and rows. Filters by owner, tag or element type switch views on and off, without changing the board.
- 5
Link or archive
A record may sit on several boards. Completed boards can be archived without the records behind them disappearing.
“We mostly work with the budget column.”
The comparison
Card wall or board over the system?
Feature
Classic card wall
teamspace board
Recommended Content of the cards
Own notes, created by hand
Real records: tickets, work packages, invoices, contacts
Data maintenance
Twice, once on the board, once in the system
Once, the board is only the view on the record
One record on several boards
Copy or link by hand
The same record, one status change takes effect everywhere
Private and shared
Mostly shared only
Selectable per board, plus the personal pinboard
Reporting
Count the cards
Distribution by status, relevance or owner as a chart
Link to hours
Separate tools needed
Hours logged on a work package flow into the project as always
Requirements call
Which board fits your records?
You show us your column and row logic and which records belong together, we show how that becomes a board. Afterwards you know whether teamspace fits.
Two axes
Columns and rows, freely combined.
Columns and rows are independent and freely chosen. Whoever has a concrete steering need in mind builds the board for it, instead of bending to the tool.
- Columns as status or phase: Waiting, In progress, For approval, Done, or whatever your workflow needs.
- Rows as swimlanes: owners, accounts, priorities or a custom tag.
- Colours, icons and fields: what appears on the card is up to you per board.
Both axes can be adjusted later without losing cards. A board gains one more column or reorders the swimlanes by a different criterion.
Types and pinboard
Three templates, plus the personal pinboard.
When you create a board you choose a type. It differs mainly in the preset statuses and can be converted into another at any time.
- Kanban for continuous flow: Waiting, In progress, For approval, In test, Done.
- Scrum for fixed sprints: Product backlog, Sprint backlog, In progress, For approval, Done.
- Pin as a free pinboard: None, Info, Open, In progress, Done, Cancelled.
Every employee also has a personal pinboard automatically. Via the pin on an element's profile card you attach it with a relevance level from Low to Top, quickly reachable through the status bar. A quiet overview of what you want to keep in view, without anyone reading along.
How teams build their board.
The same records, three different forms of steering, without a dedicated special tool.
Recruiting board
- Inbound mails become tickets, applicants become contacts
- Columns from inbox through first interview to offer
- Cover letter and CV attached to the record
one board per role
Sales pipeline
- Contacts from the CRM and quotes as cards
- Columns from lead to close, rows per sales rep
- The state is visible without an Excel export
lead to close
Approval for inbound invoices
- Inbound invoices sit on the board as cards
- Columns Inbox, Check, Approval, Booked
- Everyone sees at once what is still waiting
inbox to booked
Context on the board
Every board brings its wiki, forum and files along.
A board is more than its columns. In the detail manager every board brings its own context, in its own tabs.
- Own wiki and forum: procedures and agreements sit on the board, not in some foreign store.
- Files on the board: uploaded via drag and drop and linked to the board.
- Watchers, permissions, versions: who is informed about changes, who may read or write, and every saved state stays reactivatable.
So a board is not just a sorting surface, but the place where a topic sits together with its knowledge, its discussion and its files.
Fixed method
Kanban and Scrum as preconfigured boards.
Kanban board
For continuous task flow with firmly defined statuses.
- Preset columns, ready to use right away
- Cards travel from Waiting to Done
Scrum board
For teams that work in fixed sprint windows.
- Backlog and sprint status preset
- Connected to time logging and project structure
More from Teamwork
What a board borders on in daily use.
Boards are one area of the Teamwork software. These areas border directly on it and share the same user groups.
Task management
Open points with owner, deadline and status as a card source.
Learn moreCompany wiki
What is needed more often sits versioned in the wiki of the board.
Learn moreTeam forum
Topics and polls that belong to a board.
Learn moreTeam chat
Agree quickly and hand the record straight into the conversation.
Learn moreTeam calendar
Appointments, leave and milestones of the team in one view.
Learn moreDocument management
Store shared files versioned on the project and customer.
Learn more
In overview
Boards are one area of Teamwork.
A board sorts the records, the rest of the collaboration sits right beside it: wiki, forum, team calendar and chat. In teamspace they sit in one application, and every board already brings its own wiki, forum and file drawer. How that interacts is set out in the overview of the Teamwork software.
To the Teamwork softwareBackground
What boards typically replace.
In practice boards take in several island tools at once: the separate recruiting tool, the dedicated approval tool for inbound invoices, the spreadsheet pipeline in sales and the personal to-do app. Not because a board covers every special application in every depth, but because the records already live in teamspace and only need a sensibly chosen view.
The state instead of the search. Because a card is the record itself, the board shows the real state, not a retyped snapshot. Nobody asks by email where something stands, and nobody keeps two lists that drift apart the next day.
In the EU, in every edition. Boards belong to the Teamwork layer and are included from the light edition on, with no surcharge for a separate module. The data sits in an ISO-27001-certified data centre in Frankfurt am Main, exclusively inside the EU, in line with the GDPR. The contractual partner is 5 POINT AG from Darmstadt.
Related modules
What is most often steered on a board.
What sits on the board as a card is almost always a project, a customer or a logged hour. Here are the shortest routes there.
Project management
From the work package on the board becomes project work: structure, phases and planned versus actual, up to date.
- Tasks on the work package
- Structure and phases
- Planned versus actual and contribution margin
CRM software
The contact on the board is the customer file: records, history and terms in one place.
- Organisation, contact and record
- Digital customer file as a timeline
- Calls and mails on the contact
Time tracking online
From the record on the board becomes the logged hour: billable or internal, kept apart.
- Log on project or ticket
- Billable or internal, kept apart
- Approvals traceable
Boards as a view across the whole system
A board in teamspace is not what you know from Trello or a classic whiteboard app. There a card is a note that someone creates and maintains by hand. In teamspace a card is almost always an existing record: a ticket, a work package, an invoice or a contact. The board shows where that record currently stands.
From this follows the biggest difference in daily use. Whoever changes the status of a card does not change an entry on the board, but the status of the original. Whoever attaches a file attaches it to the record itself. Whoever logs an hour logs it on the work package behind the card. The record lives once, the board is only one of many possible views.
Freely configurable, freely combinable
Columns and rows are independent and freely chosen. Columns map phases or status, rows are swimlanes for owners, topics, accounts or priorities. Both axes can be adjusted later without losing cards. A board gains one more column or reorders the swimlanes by a different criterion.
What sits on the board is just as flexible. Tickets next to work packages, invoices next to contacts. Whoever has a concrete steering need in mind builds the board for it, instead of bending to the tool.
Private or shared
Boards are not necessarily team tools. Per board the creator decides whether it is visible only to them or shared with a team, an account or the whole organisation. That makes a board also a personal pinboard: a private board onto which own topics, watched tickets or critical projects travel, without anyone reading along. Management and account owners often use this as a quiet overview of things they want to keep in view.
Specialised boards for fixed methods
Whoever works with a fixed methodology like kanban or scrum finds two preconfigured variants under Project management: the kanban board for continuous task flow and the scrum board for teams with fixed sprint windows. Both differ mainly in their preset statuses and use the same boards foundation as the freely configurable boards on this page.
Frequently asked questions about boards in teamspace
What sets a board apart from a task list?
A task list shows one type of entry below one another. A board shows any records in two dimensions, for example status by owner or phase by account. On the board a task becomes a card with owner and due date; tickets, invoices or contacts sit there equally.
Which records can be placed on a board?
Tickets from the service desk, work packages from the work breakdown structure, tasks from task management, contacts from the CRM, invoices and inbound invoices from cost management, as well as own notes without a source record.
What is the personal pinboard?
A board that belongs only to you. Via the pin on an element's profile card you attach it with a relevance level from Low to Top. The pinboard is quickly reachable through the status bar and shows how many elements sit on it and which priority is currently the highest. Nobody else sees it.
How do I configure columns and rows?
Columns and rows are independent and freely chosen. Columns usually map status or phases, rows (swimlanes) group by owner, account, priority, type or group. Colours, icons and the visible fields on the card are set per board and adjusted later, without losing cards.
Can a record sit on several boards?
Yes. A ticket from the service desk can sit on the support team board, on a customer board and at the same time on the management's personal pinboard. It is always the same record; a status change takes effect on all boards instantly.
Does a board bring tasks along automatically?
On request, yes. A board can be filled with the open tasks of a project, a project directory or an employee, automatically or manually. New open tasks then appear on the board by themselves, with the set relevance and in the chosen status.
Are boards linked to hours?
If the card is a record with a project reference, for example a work package, the hours logged on it flow into the project as always, because the card is the record itself. A plain note without a source record has no link to hours.
What does a board's reporting show?
A board shows a statistic of the cards, for example the distribution by status, relevance or owner as a chart. Deeper figures such as logged hours or contribution margin sit on the linked record and in its reports, not on the board itself.
Where is the board data stored?
In an ISO-27001-certified data centre in Frankfurt am Main, processed exclusively inside the EU. The contractual partner is 5 POINT AG from Darmstadt. Data protection and account structure are architecture, not an annex.
Requirements call
See your board on a real example.
We go through your column and row logic and the records to be linked and tell you what is worth it for you and what is not.