Skip to main content

GeofenceAssignment

A geofence assignment links a geofence to a specific entity (user, group, project, or entry screen).

When an entry is submitted, the system determines which geofences apply by checking if the user or project matches any assignment for active geofences.

Assignment Target Tables:

  • users - Direct assignment to individual users
  • groups - Assignment to all users in a group (via ACL membership)
  • projects - Assignment to a specific project (including PX tasks)
  • time_guis - Assignment to a time entry screen configuration
  • expense_guis - Assignment to an expense entry screen configuration
  • travel_entry_guis - Assignment to a custom entry screen configuration
target_tablestringrequired

The database table name of the entity type being assigned.

Valid target tables:

  • users - Individual user assignments
  • groups - User group assignments (applies to all group members)
  • projects - Project assignments (including PX tasks, which are projects)
  • time_guis - Time entry screen assignments
  • expense_guis - Expense entry screen assignments
  • travel_entry_guis - Custom entry screen assignments (formerly "Mileage Entry")

Possible values: [users, groups, projects, time_guis, expense_guis, travel_entry_guis]

Example: users
target_idstringrequired

The ID of the entity being assigned. This must be a valid ID from the specified target_table.

When creating or updating assignments, the API validates that all referenced entities exist. If any target entity does not exist, the request will fail with a 400 Bad Request error.

Example: 5CD906A3941C463B9CC98F49DBCC25AA
GeofenceAssignment
{
  "target_table": "users",
  "target_id": "5CD906A3941C463B9CC98F49DBCC25AA"
}