See the Same Records as a Table, Calendar, Gallery, or Kanban Board
Save filtered database views and switch the same business records between table, calendar, gallery, and kanban layouts.
Give each workflow the shape it needs without copying data into separate tools.
The practical problem
The same data rarely has one useful shape. Sales wants a pipeline board, operations wants a due-date calendar, managers want a filtered table, and creative teams want visual assets. Copying records into separate tools creates drift and reconciliation work.
InfoLobby views let teams save filtered, sorted ways of working with a table, then choose the layout that fits the job: grid for scanning, calendar for dates, gallery for visual records, and kanban for status-driven work.
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 changes for the team
- Saved views preserve filters, sorting, layout, and layout settings
- Kanban boards turn single-value select fields into workflow lanes
- Calendar layouts show records by date or date-time fields
- Gallery layouts make file-backed visual records easier to review
- Teams use different layouts without splitting the source data
What InfoLobby gives you
- 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
How teams usually start
- 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.
Best fit
- 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
Probably not a fit
- Pure dashboarding where charts and aggregates are the main requirement
- Project management that needs advanced dependency planning or sprint analytics
- Public asset galleries where unauthenticated browsing is the product
- Sales pipeline kanban
- Project deadline calendar
- Creative asset gallery
- Filtered operations queues
FAQ
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.
Need this without adding another fragmented tool?
InfoLobby works best when the data, process, and collaboration belong together. If that is your bottleneck, a trial will show fit faster than another abstract product tour.