Contains API calls related to security groups, that is, groups of sub-users with the specified set of rights and privileges.

Security group object structure

${security_group} = {
      "id": 103, //group id, can be null (when creating new security group)
      "label": "Managers", //group label
      "privileges": {
        "rights": [
          "tag_update", "tracker_register" //a set of rights granted to security group (see below)
        "store_period": "1d" // optional, period of viewing history in legacy duration format, e.g. "2h" (2 hours), "3d" (3 days), "5m" (5 months), "1y" (one year)

Default security group

Default (or empty) security group is the group which is effective when sub-users’ “security_group_id” is null. It has empty “rights” array.

Master user’s rights

Master user always has all rights, including exclusive “admin” right.

Security group rights

Absolute majority of read operations does not require any rights (that is, they are available to all sub-users, even with “null” security group). However, some entities may be hidden because they are associated with the trackers unavailable to sub-user.
Most f data-modifying operations, on the contrary, require some rights to be present.

Possible rights are:

  • admin, – master user-only, can not be assigned to security groups
  • tracker_update,
  • tracker_register,
  • tracker_rule_update,
  • tracker_configure,
  • tracker_set_output,
  • tag_update,
  • task_update,
  • zone_update,
  • place_update,
  • employee_update,
  • vehicle_update,
  • payment_create
  • form_template_update,
  • reports;

If you have more questions please contact our support team


USA: +1 858 815 9045

Mexico: +52 334 1642158

UK: +44 808 1641499

Germany: +49 1573 5988250

Russia: +7 495 317 1622

Log in


We use сookies to improve our website, products and related services, analyze site traffic, and serve targeted advertisements. If you continue to use our services, you consent to our use of сookies. Read more