1
Collection
The object type, such as Users, Shifts, Locations, Documents, or Employee Tiers.
Concept overview
Concept deep dive
Collections
Collections are the databases Teambridge runs on. They define the objects your operation cares about: workers, shifts, locations, timesheets, documents, applications, jobs, tiers, reimbursements, surveys, tasks, and any custom object your workflow needs.
Practical rule
Use collections when a business concept needs its own records, permissions, workflows, views, reporting, or audit trail.
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
Collections organize the core objects your operation runs on.
Source
1Users
Workers, admins, clients
Live work
2Shifts
Time, role, location, status
Scope
3Locations
Sites, rules, geofences
Payroll
4Timesheets
Clock-ins and approvals
Custom
5Employee Tiers
Eligibility and priority
Object map
Which object needs records, permissions, views, reporting, or automation?
The answer should become a collection, a field, a view, a permission, or a workflow step.
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
Record
One row inside that collection, such as Alicia M., Shift #4812, North Wing, or Gold Tier.
3
Schema
The fields that can exist on each record.
4
Relationships
Links from one collection to another, such as a Shift linked to a User and Location.
5
Workspaces
The views operators use to work with collection records.
1
Standard collections
Most accounts start with standard workforce objects. These are not generic tables; they represent the operating model Teambridge expects across scheduling, staffing, compliance, payroll, and communication.
Users store workers, admins, managers, clients, and facility users.
Shifts store scheduled work, assignment, status, role, location, and timing.
Timesheets store clock-in, clock-out, approvals, and payroll readiness.
Locations store facilities, client sites, geofences, addresses, and location-specific rules.
Roles store job types, qualifications, and role-based pay or bill logic.
Documents, Jobs, and Applications support onboarding, recruiting, credentialing, and hiring workflows.
2
Custom collections
Create a custom collection when the workflow has an object that should be reusable, filterable, permissioned, linked, and automated. If the object will appear in reports, trigger workflows, or have multiple records, it usually deserves a collection.
Employee Tiers can store Gold, Silver, and Bronze tier records.
Reimbursement Requests can store amount, receipt, status, approver, and worker.
Facility Surveys can store ratings, notes, facility, shift, and follow-up status.
Callback Adjustments can store worker-submitted service counts tied to a shift.
Do Not Return logic can use a field linking Users to restricted Locations.
3
How to decide whether something is a collection
A collection is useful when the team needs structure. A simple field is enough for a one-off value, but a collection is better when the value has its own lifecycle or needs to connect to other workflows.
Use a field for a simple attribute, such as shirt size or preferred language.
Use a collection when the object has multiple fields, status, owners, permissions, or history.
Use a link when one object needs to point to another object, such as a Shift linked to a Location.
Use custom collections for customer-specific operating objects that repeat across the account.
Example: Employee tiers
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 an Employee Tiers collection.
2
Add records for Gold, Silver, and Bronze.
3
Add a User field that links each worker to one tier.
4
Add a Shift field that lists accepted tiers.
5
Use rollups and workflows to move workers between tiers based on attendance signals.
6
Use access filters or policies so workers only see eligible shifts.