1
Basic fields
Text, number, phone, date-time, currency, checkbox, select, and multi-select fields.
Concept overview
Concept deep dive
Schemas and field types
Schemas are the fields on a collection. They define what each record can store and what workflows can read. Good schema design turns messy operational knowledge into structured signals Teambridge can filter, automate, permission, and report on.
Practical rule
Use schemas to capture the operational facts that decisions depend on: status, owner, role, location, time, amount, eligibility, approval, or relationship.
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
Schemas turn operational details into structured fields.
Select
Role
LPN, RN, CNA
Configured
Link
Location link
Shift to facility
Configured
Rollup
Late count
Attendance rollup
Configured
Status
Approval status
Pending to approved
Configured
Action
Policy widget
Operator decision
Configured
Field model
Which fields must be captured so a policy, view, or workflow can act on the record?
Field type
Permission
Used by workflow
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
Relationship fields
Link to Object fields that connect records across collections.
3
Computed fields
Formulas and rollups that calculate values from existing data.
4
Action fields
Buttons and widgets that give operators richer in-record actions.
5
Permissioned fields
Fields that some groups can view, update, update only from blank, or not access.
1
Link to Object
Link to Object connects one collection to another. This is one of the most important Teambridge patterns because workforce operations are relational: a shift belongs to a location, a worker has roles, a document has an owner, and a reimbursement belongs to a worker or shift.
Use links instead of copying the same value into many places.
Use single-select links when a record should point to one object.
Use multi-select links when a record can point to many objects.
Examples: User to Locations, Shift to Assignee, User to Employee Tier, Document to Owner.
2
Rollups
Rollups summarize values from linked records. They let an admin see patterns without manually counting. A User can roll up late shifts, no-shows, cancellations, completed tasks, approved reimbursements, or accepted shifts.
Use rollups when a record needs a metric from related records.
Rollups are useful for performance tiers and coaching.
Give rollups time to update before dependent automations run.
Use rollup outputs in dashboards, policies, and workflows.
3
Formulas, widgets, and action fields
Formulas calculate values from fields. Widgets surface richer product experiences inside records, such as policy-driven match lists. Buttons can start actions from the record detail view.
Use formulas for derived values that should stay consistent.
Use widgets when a simple field is not enough for the operator's decision.
Use buttons where the operator needs a clear action from the record.
Keep action fields close to the context where the decision happens.
4
Schema permissions
Schema permissions protect sensitive information without blocking useful work. A manager may need to see role and location, but not payroll fields. A facility may update shift details, but not internal configuration.
Can view allows the field to be visible.
Can update allows a user to edit the field.
Can update only from blank allows first-entry without later changes.
No access hides the field entirely from that group.
Example: Do Not Return field
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
Add a Do Not Return field to Users.
2
Choose Link to Object as the field type.
3
Link it to the Locations collection.
4
Set it to multi-select so one worker can have multiple restricted sites.
5
Create a workflow that removes matching locations from the worker's available locations.
6
Test that the mobile app no longer shows shifts from restricted locations.