Skip to main content
The activity log records every location check. It is called Recent checks and it is the screen you read for a week before you switch a rule on. Go to Settings → Location rules → Recent checks.

​
What it is

The page describes itself as: “What each person’s device reported, and what we did about it. Read a week of these before switching a rule from watching to enforcing.” One row per check. Newest first.

​
Why it exists

A rule that looks right on paper stops half your team on day one, because of a network range nobody mentioned or a circle drawn 50 metres too small. The log turns that from a Monday morning outage into a week of quiet reading. While a rule is Watching it records everything and stops nobody.

​
The table

The card is titled Checks: “Newest first. Locations are what each person’s device reported.”

​
Outcomes

“Couldn’t check” never counts as a pass. A rule with no networks listed returns “Couldn’t check” for everyone, which is why an empty rule cannot be switched on.

​
Reasons

The Why column names the exact cause:
Read the Why column, not just the outcome. “Not on an office network” is a missing range. “Location too vague to tell” is someone on a laptop. Those need completely different fixes.

​
Filtering

The filter above the table has four options: Away from work is the one you want during a watching week. Every row in it is either a rule doing its job or a range you forgot.

​
Warning badges

Some rows carry an extra badge about the position that was reported.
Moved impossibly fast fires for a real flight as well as for a faked one. It is a reason to ask a question, not an answer to it.

​
What is recorded

For each check:
  • Who was checked, and when.
  • The internet address their connection came from.
  • The position their device reported – kept even when it was discarded, so you can see what was thrown away and why.
  • Which rule applied, the outcome and the reason.
  • Whether the network matched, whether a place matched, which place, and how far away they were.
  • Whether the check came from the web app or the mobile app.

​
Empty state

Before anything has been recorded:
Nothing recorded yet. Checks appear here once a rule applies to someone and they open the app.
If you see that after assigning a rule, nobody covered by it has opened TimeTracker yet.

​
How to use it before enforcing

1

Leave the rule Watching for a week

A full week catches people who only come in on certain days.
2

Filter to Away from work

Every day. This is the short list that matters.
3

Ask about each name you did not expect

Someone in the office showing “Not on an office network” usually means a second internet connection or an IPv6 address you did not add.
4

Filter to Couldn't check

A pile of these is normally desktop users failing a place check. Add a network range and set the rule to Either the network or the place.
5

Read the enforce dialog

When you click Start enforcing, it tells you how many covered people would have been stopped in the last 7 days. That number should be the people you intended.

​
Example

Northwind Studio runs Studio in Watching for a week. Two of the four rows were bugs in the rule, not people breaking it. That is a normal first week, and it is exactly why you watch first.

​
Permissions

An auditor with audit.read can read the log without being able to change any rule.

​
Retention

Checks are kept. There is no automatic purge, so the log builds over time.

​
Rate limiting

A person’s device is limited to 30 checks a minute. Beyond that they see: “We’re checking your location too often. Wait a moment and try again – nothing you’ve tracked is affected.” You will not hit this in normal use.

​
Common questions

About a week. That covers people who are only in on certain days, and catches the weekly patterns a single day misses.
Nobody covered by a rule has opened TimeTracker yet. Checks are recorded when people use the app, not on a schedule.
No. It records what would have happened and refuses nothing.
The filter is by outcome. Filter to Away from work and read down the Person column.
Not enough information to decide. A discarded position, a missing address, or a rule with nothing configured. The Why column names which.
Yes, deliberately. Otherwise a “Location too vague to tell” row would tell you nothing about what actually happened.

​
Troubleshooting

Everything says “Couldn’t check”. Either the rule has no networks or places configured, or your hosting is not passing the real network address through. The Why column distinguishes the two. People in the office show as away. They are on an address you have not listed. IPv6 is the usual culprit. A name appears that should not. Check the Who this affects table on the main settings page. Precedence is person, then group, then role, then everyone. No rows for someone you assigned. They have not opened TimeTracker since the assignment started. Check the assignment’s start date too.

Location rules overview

The concept and what it cannot see.

Create a location rule

Watching, then enforcing, step by step.

IP restrictions

Fixing “Not on an office network”.

GPS restrictions

Fixing “Location too vague to tell”.

Location permissions

Who can read the log.

Roles and capabilities

location.manage and audit.read.