Build a board with your own columns and fields.
Start from a template, set your own columns, put your own fields on the cards, and deploy it into the department that owns the work. View it as a kanban, a table, a list, a calendar or a timeline.
Build the board, put your own fields on the cards, and deploy it into the department that owns the work. The items are records, so everything else can see them.
A board you built
Your columns and your fields.
Switch between layouts and you are looking at the same items a different way, not a second board. Cards show the fields you added, including one as a colour stripe down the edge, and the board lives inside the department it belongs to, not in a separate app.
Items on your board work like everything else in NearSync.
Five ways to view one board.
Switching layout shows the same items a different way. There is never a second board to keep up to date.
- Start from a template instead of an empty board
- Name the columns after the stages your work moves through
- Show your own fields on each card as a badge, a metric or a colour stripe
- View the board as a kanban, a table, a list, a calendar or a timeline
Put the board inside the department that owns the work.
The board follows that department's permissions, so there is no second set of access rules to manage.
- Deploy a board into the department that owns the work
- Run an automation when an item moves to a new column
- Use custom fields to decide what each card shows
- Include the board in reports without exporting anything
Access
Who can do what.
Anyone can add items and move them along. Building a board and deploying it into a department shapes what a whole team looks at every morning, so it needs a higher permission.
See a board and the items on it.
Add items and move them between columns.
Build boards, set columns and choose card fields.
Deploy a board into a department.
Admin is the highest role and is not constrained by the permission grid, so it is worth keeping to the smallest group that genuinely needs it.
One board, start to finish
A board built in an afternoon, out of a spreadsheet.
Work that lived in a spreadsheet became a board with its own columns and fields, deployed into Operations. Once it was there, an automation could watch it and the reports included it, with nothing exported by hand.
Real work with no ready-made module for it, so it was living in a spreadsheet.