Easyteam Embedded
GuidesAPIWhite-Label UIs
GuidesAPIWhite-Label UIs
  1. Embedded Workforce Management
  • Getting Started
    • Introduction
    • Why Choose Easyteam Embedded
  • Development
    • Overview
    • Authentication
    • Web Integration
    • Mobile SDK Integration
    • Passing Data
    • Using Identifiers
    • Events
    • Error Handling
  • Going Live
    • Data Security
    • Support
  • Embedded Workforce Management
    • Organizations & Locations
    • Employees
    • Permissions
    • Compliance
  • Embedded Time Tracking
    • Overview
    • Time Clock
    • Timesheets
    • Breaks
    • Geofencing
    • Timezones
  • Embedded Scheduling
    • Overview
    • Availability & Open Shifts
    • Multi-Location Scheduling
    • Publishing Schedules
    • Working with Time Off in Schedules
    • Notifications on Schedule Actions
    • Calendar Sync (Google / Apple Calendar)
  • Embedded Time Off Management
    • Overview
    • Time Off Policies
    • Requests & Approvals
    • Balance Tracking & Accruals
    • Carryover Rules
    • Time Off and Payroll Sync
  • Embedded Notifications
    • Overview
  • Payroll Integrations
    • Embedded Payroll with Salsa
      • What is Embedded Payroll?
      • Time & Attendance in Payroll
      • Money Movement and Compliance
    • External Providers
      • Embedded Payroll Integrations
  • AI-Native Integrations
    • Integrating an MCP Server with Easyteam
GuidesAPIWhite-Label UIs
GuidesAPIWhite-Label UIs
  1. Embedded Workforce Management

Organizations & Locations

Understanding Easyteam's organization model helps you structure your workforce management implementation for different business types and scales.

Data Model Overview#

Easyteam uses a two-level hierarchy where Organizations contain one or more Locations, and each Location has its own employees. This flexible model adapts to various business structures, from single-location shops to multi-state enterprises.

Understanding Organizations#

An Organization represents the top level of your business structure. For a small business, this might be the business itself. For larger enterprises, it could represent a brand, franchise, or corporate entity. Organizations share common settings, policies, and administrative controls.
Consider a salon chain "Style Co." as an example. The entire brand would be one Organization, allowing for centralized management and reporting across all locations.

Understanding Locations#

Locations represent physical places where employees work. Each Location can have its own specific settings, schedules, and employee roster. This could be a store, office, warehouse, or any distinct workplace.

Single Location Businesses#

For businesses operating in one location, like a local coffee shop, the Organization and Location might represent the same entity. In this case, you'd use the same identifier for both:

Multi-Location Businesses#

For businesses with multiple locations, like a regional restaurant chain, each restaurant would be a separate Location under the main Organization. This enables location-specific management while maintaining centralized control:

Common Business Types and Structure#

Business TypeOrganization StructureLocation StructureTypical Use Case
Small BusinessSingle OrganizationSingle LocationLocal shop or office using the same identifier for both Organization and Location
Regional ChainSingle OrganizationMultiple LocationsRestaurant chain with centralized management but separate scheduling and operations per site
FranchiseOrganization per Owner or Brand as OrganizationLocations per SiteBeauty salon franchise where each owner operates independently or centrally managed franchise system
EnterpriseMultiple OrganizationsMultiple Locations per OrganizationRetail corporation with different brands, each having multiple store locations

Practical Considerations#

Timezone Management#

Each Location can have its own timezone settings, ensuring accurate time tracking across different geographical areas. Reports and timesheets automatically adjust to show the correct local time for each Location.

Permission Scoping#

Access permissions can be scoped at both Organization and Location levels. This allows for flexible management structures where regional managers oversee multiple Locations, while local managers focus on specific sites.

Reporting#

The two-level structure enables powerful reporting capabilities, both on Organization-wide and Location-based metrics.

Cross-Location Employment#

Employees can work across multiple locations within an Organization. A common scenario is retail staff covering shifts at different stores, or service professionals rotating between different sites.
For an employee working at multiple locations, you'll need to generate separate authentication tokens for each location they work at. Each token represents a unique work context for that location:
đź’ˇ
Need help determining the best structure for your business? Our integration team can help you plan the optimal setup for your current needs and future growth.
Modified at 2025-03-22 23:24:42
Previous
Support
Next
Employees