1
Base table
The table the workspace is built on, chosen on the Select Workspace Table screen when the page is created.
Concept overview
Concept deep dive
Workspaces and views
Workspaces are the screens teams use to run the operation. They are configured views over collection records, built around the job the operator needs to complete: fill shifts, review exceptions, approve time, manage documents, check attendance, or collaborate with clients. Every workspace is built on one table and lives inside a named section of the left navigation.
Practical rule
Design workspaces around decisions, not database tables. The best workspace helps a person scan, prioritize, act, and verify the result.
Use this page when you need to decide:
what to configure, where the data lives, who should see it, and what the next operational action should be.
Operational visualization
Workspaces organize daily queues around decisions.
Queue
Open
Needs coverage
Queue
Requested
Awaiting approval
State
Filled
Assigned worker
Risk
Late
Exception
Action
No-show
Escalation
Operating view
What does this team need to scan, prioritize, and close today?
Put exception queues before all-record views so teams see risk first.
Definition
The parts operators need to understand
This is the vocabulary to use when explaining the concept to a scheduler, payroll lead, client manager, or implementation owner.
2
Sections
Named groups in the left navigation, such as Team, Schedule, Time Tracking, or Reporting, that organize related workspaces.
3
List workspace
A table-like view with filters, columns, sorting, tabs, and actions.
4
Calendar workspace
A schedule view for shifts grouped by day, week, location, user, or role.
5
Canvas workspace
A flexible content page for instructions, training, guides, or self-serve information.
6
Tabs
Saved filters for recurring queues such as Open, Requested, Filled, Late, No-show, or Overtime Risk.
7
Record detail
The view that opens when an operator needs to inspect or update one record.
1
Start by selecting the workspace table
Every new workspace begins on the Select Workspace Table screen: choose a table to be your workspace, and hover over a table option to see a preview of the view it produces. The table decides which fields, filters, tabs, and actions the page can use, so pick the object the operator actually acts on.
Standard tables include Users, Shifts, Locations, Job Roles, Contacts, Documents, Tasks, Placements, Shift Groups, and Jobs.
Choose Custom Table when the page should run on a customer-specific collection, such as Certifications, Points Tracker, or Daily Time Reports.
One workspace runs on one table. Use tabs for different slices of the same table, and separate workspaces for different objects.
If the page you want mixes several objects, model the missing object as a collection first, then build the workspace on it.
2
Organize workspaces into sections and pages
The left navigation groups workspaces into named sections, and each section holds the pages one team uses for one area of the operation. Name sections after areas of responsibility and pages after the queue or decision inside them, so a new user can find their work without training.
Team: core directory pages such as Users, Locations, Clients, and Job Roles.
Schedule: Master Schedule, per-location or per-division schedules, Upcoming Shifts, and Completed Shifts.
Approvals and Attendance: Shift Releases, policy-violated requests, Late Clock In, Early Clock Out, and No Show queues.
Time Tracking: Time Sheets, Time Change Requests, Missing Clock Outs, and a Needs Attention queue.
Reporting or Dashboards: Call Outs, No Shows, Unfulfilled Shifts, High Risk, and invoicing reports.
Sandbox: a section for drafts and experiments. Move a page into a real section only when the team is ready to use it.
3
List workspaces
List workspaces are strongest when the team needs to scan records and act on exceptions. A documents page can have Expiring This Week, Expiring Next Month, and All Documents. A shifts page can have Open, Requested, Filled, Late, and No-show.
Put exception tabs before all-record tabs.
Show only the fields needed to make the decision.
Use saved filters for repeated queues.
Use row actions where operators need speed.
4
Calendar workspaces
Calendar workspaces make scheduled work easier to understand by time, location, role, or person. They are useful for shift planning, availability review, route-based scheduling, and visual coverage checks.
Choose the grouping that matches the operating question.
Use color for status, role, or coverage state.
Keep shift detail one click away.
Combine calendar views with exception tabs for follow-up.
5
Canvas workspaces
Canvas workspaces are useful when the workflow needs explanation rather than a table. They can hold facility instructions, training, policy guidance, process guides, or mobile-friendly self-serve information.
Use canvas for guidance, not high-volume review.
Scope canvas visibility by access group.
Keep content connected to real operating workflows.
Review it periodically so instructions stay current.
Example: Open shifts workspace
How this shows up in a real Teambridge workflow
Use this as the implementation checklist: each step should produce a visible record, permission, view, or automation.
1
Create a new list workspace and select Shifts on the Select Workspace Table screen.
2
Create a tab where assignee is empty.
3
Add columns for role, location, start time, credential need, and request status.
4
Add related worker recommendations or outreach actions.
5
Use the detail view to assign the accepted worker and close the loop.