Records are the live rows inside collections. They are the actual workers, shifts, locations, documents, reimbursements, surveys, applications, tasks, and timesheets your team operates on every day.
Use records as the source of truth. A record should hold enough context for an operator to understand state, history, relationships, and next action.
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.
Act on a matching result
Hover over a result or focus it with your keyboard to reveal the available actions. The person icon starts assignment. The speech bubble opens a message draft.
Example screen with fictional data. Available controls depend on your account and permissions.
This is the vocabulary to use when explaining the concept to a scheduler, payroll lead, client manager, or implementation owner.
1
Identity
The fields that make the record recognizable, such as name, title, facility, date, or shift number.
2
Status
The current operating state, such as Open, Requested, Filled, Late, Approved, or Needs Review.
3
Relationships
Links to related records, such as worker, role, location, documents, tasks, or timesheet.
4
Activity
Updates, submissions, completed tasks, communication, approvals, and workflow events.
5
Detail view
The configured modal, right panel, or full-screen view used to inspect the record.
1
Records should explain the work
A record is not just storage. It is the place where operators understand what is true right now. A shift record should show whether it is assigned, who accepted, whether the worker checked in, whether there is an exception, and what action is available.
Keep primary fields visible near the top.
Use status fields consistently across workflows.
Link related records so operators can navigate context.
Avoid burying the next action under low-value fields.
2
Record detail modal
When a record is opened, Teambridge can show a configurable detail view. It can appear as a full screen, right panel, or centered modal depending on the workflow.
Configure the header image, heading, and subheading.
Choose stacked content rows for the important context.
Show preview fields that help the operator decide quickly.
Include metrics such as created date, last updated date, or key schema values.
3
Records trigger workflows
Many workflows begin when a record changes. A shift is created, a worker submits a request, a reimbursement changes to Approved, a DNR field is updated, or a late count crosses a threshold.
Use status changes as clear workflow triggers.
Keep trigger fields stable and well-named.
Avoid relying on free-text notes when automation needs structure.
Store workflow outcomes back on the record for visibility.
Example: Reimbursement request record
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
Worker submits amount, description, and receipt from mobile.
2
Teambridge creates or updates a reimbursement record.
3
The record links to the worker, shift, location, and approver.
4
Admin reviews the request in a workspace tab.
5
Approved status becomes available for payroll or billing review.