Concept deep dive
Teambridge platform concepts
Teambridge is built from repeatable concepts. Once teams understand these building blocks, they can reason about almost every workflow in the platform.
Platform model
Turn messy operations into records, views, rules, and actions.
Every Teambridge rollout is easier to understand when the team can separate what the business stores, where operators see it, who is allowed to act, and what should happen automatically.
Object
Collections define the workforce object: shifts, users, locations, documents, requests.
Structure
Schemas define the fields, relationships, formulas, status, and evidence needed.
Surface
Workspaces and mobile sections show the right record to the right person.
Action
Access groups, policies, and workflows decide what can happen next.
Read this first
Use concepts to debug implementation decisions.
How the platform fits together
A practical path from raw data to controlled operations.
Collections
What exists
Schemas
What fields matter
Records
What happened
Workspaces
Where teams work
Access groups
Who can act
Workflows
What happens next
Collections store the objects, schemas define the fields, records hold the live data, workspaces make the work visible, access groups decide who can act, and workflows automate the next step.
Collections
Collections are Teambridge databases. They hold records and define the objects a business operates with, such as Shifts, Timesheets, Users, Locations, Roles, Documents, Jobs, Applications, Employee Tiers, callback adjustments, facility surveys, or reimbursement requests.
Schemas and field types
Schemas are the fields on each collection. They can store text, numbers, dates, currency, signatures, ratings, checkboxes, formulas, rollups, widgets, and links to other objects.
Records and record detail views
Records are the live rows inside collections. A worker is a User record, a scheduled assignment is a Shift record, a hospital is a Location record, and a reimbursement request can be its own custom record.
Workspaces and record views
Workspaces are configured views over records. Teams can use list views, calendars, canvases, dashboards, approval queues, and record detail modals to run daily work.
Access groups
Access groups control what admins, managers, clients, facilities, and workers can see and do. They govern product visibility, workspaces, collections, schemas, mobile sections, and actions.
Workflows, policies, and AI specialists
Workflows orchestrate triggers, conditions, waits, actions, messages, approvals, and specialist steps. Policies evaluate rules such as overtime, tier access, credentials, location access, or matching preferences.
Mobile app experience
The mobile app exposes only the sections, actions, shifts, tasks, content, and communication relevant to each worker's access group and policy rules.
Implementation order
When a workflow is unclear, walk it through the concepts in order.
Object
What collection stores the thing?
Fields
Which schema fields describe state and rules?
View
Where does the operator review it?
Action
Who can act, and what workflow runs next?
Next