See the Same Records as a Table, Calendar, Gallery, or Kanban Board
Look at the same records as a grid, a calendar, a gallery, or a kanban board. Save each one as a view.
Stop exporting the same rows into a spreadsheet, a board and a calendar so everyone can read them.
The same records, four different jobs
Sales wants deals as a pipeline. Operations wants those same records on a calendar, by due date. A manager wants a filtered table they can scan in thirty seconds. None of them is wrong, and none of them wants to look at the other two.
The usual compromise is three exports into three tools, which start drifting apart immediately and have to be reconciled by hand. A view is the alternative: one table, several saved ways of looking at it, all reading the same rows. Move a card in the kanban board and the calendar already knows.
A view should change perspective, not create another source of truth.
The useful shift is not cosmetic. A kanban board helps the team move work by status, a calendar exposes timing risk, a gallery makes visual review faster, and a table stays best for dense scanning. InfoLobby keeps those perspectives tied to the same records, permissions, comments, tasks, history, API, and automations.
- Use kanban when status is the conversation
- Use calendar when dates create risk or urgency
- Use gallery when the record is easier to judge visually
- Use the grid when comparison and density matter most
What a view remembers
- Switch a table between grid, calendar, gallery, and kanban layouts
- Save layout configuration onto a view so teammates can reopen the same workspace
- Use select-field colors on calendar events and kanban lanes
- Fall back to the table when a layout has too many records to display clearly
- Use existing filters to narrow each layout to the records that matter
- Publish a read-only iCal feed so a view's dated records appear in Google, Apple, or Outlook calendars
Setting up views people will reopen
- Start with the table that already holds the work: deals, projects, assets, requests, campaigns, or jobs.
- Create saved views for the questions people ask every week: open deals, upcoming deadlines, assets in review, overdue work, or assigned requests.
- Choose the layout that matches the decision: kanban for status, calendar for dates, gallery for images, grid for dense review.
Where it fits
Use it for
- Teams that need multiple working views over the same operational records
- Sales pipelines, project schedules, asset review, request queues, and approval workflows
- Internal tools where filtered views should be reusable by the whole workspace
Reach for something else when
- Summarising the records rather than working them. That is what a report tile does
- Project management that needs advanced dependency planning or sprint analytics
- Public asset galleries where unauthenticated browsing is the product
Questions people ask
Do layouts duplicate my data?
No. Layouts are different ways to work with the same table records. The saved view stores filters, sort, layout type, and layout configuration.
Which fields power each layout?
Calendar uses date or date-time fields, gallery uses a file field for images, and kanban uses a single-value select field for lanes.
Can a saved view reopen directly as a kanban board or calendar?
Yes. When an admin saves a view, the selected layout and its settings are saved with it so teammates can reopen the same perspective later.
Can people subscribe to my records as a calendar?
Yes. If a table has a date field, an admin can publish an iCal feed from the table's Public tab. Anyone with the link can subscribe in Google Calendar, Apple Calendar, or Outlook and see the view's dated records as read-only events that refresh roughly hourly.
Try it on your own data
Start free and build one working process around this feature, then add the records, views, tasks and automations around it.