This article explains the company-wide rules on Configuration > Attendance > Settings. Only users with PDKS Admin open this page. The settings apply to every branch and every employee at once.

Before you start

You have PDKS Admin.
Changes are not applied until you press Save Settings; an Unsaved changes notice appears on top and Discard throws them away. Actions on the Integration & API tab apply immediately without saving.

Step by step

In the left menu go to Configuration > Attendance > Settings. The page has six tabs: General, Location & Security, QR Configuration, Notifications, Late Policy, Integration & API.
Make the change on the relevant tab and click Save Settings.

General

Setting	Description	Default
PDKS module active	When off, nobody can scan and no manual record can be entered in this module; the absence, auto checkout and daily summary jobs stop. The time it was off does not count as absence after it is turned back on.	On
Timezone	Scan times, lateness, absence, auto checkout and the 19:00 daily summary follow this time.	Europe/Istanbul
Early leave tolerance	A check-out this many minutes before the planned end is not an early leave (0–120).	15 min
Early entry block	A check-in can be scanned at most this long before the shift starts (0–240).	30 min
Auto checkout (forget prevention)	When on, if there is still no check-out 2 hours after the planned end, the planned end is written as the check-out. When off, the missing check-out reaches the manager as a discrepancy.	Off
Check out on leaving the area (automatic check-in)	Employees with automatic check-in on in the mobile app are checked out when they leave the location's area. Leaving within 10 min of checking in is recorded, at the time they left, if they are still away when the 10 min are over; leaving an area other than the one checked in at, or during a break, is ignored. When off, employees check out themselves (Checking in by location and automatic check-in).	On
Duplicate scan prevention	The same movement repeated within this time is ignored; 0 turns it off (0–600 s).	60 s
Break tracking required	Break scans must follow the order; no check-out while a break is open.	Off
Long break threshold	A break longer than this opens a long break discrepancy at break end. If 0, planned break + break tolerance is used.	90 min
Break tolerance	Used only when the long break threshold is 0.	10 min
Planned break duration	The unpaid break deducted from each shift in the weekly plan.	60 min

Location & Security

Setting	Description	Default
Fake location (fake GPS) detection	A scan from a device reporting a fake location is rejected (see the note below).	On
Root / Jailbreak detection	A scan from a rooted or jailbroken device is rejected (see the note below).	On
Extra location radius	Extra distance added to every location's radius (0–200 m).	0 m
Scan attempt limit	The most attempts an employee can make per minute (1–60). Location-far rejections do not count.	6 /min
Auto quarantine	A device reported as faking its location or rooted is quarantined immediately.	On
Device binding	The employee is bound to the device of their first successful scan; another device needs manager approval. In a browser the device id belongs to that browser.	Off
Photo verification	A front-camera photo is required on every scan. The offline queue cannot be used while it is on. Photos are stored encrypted.	Off
Photo Retention	Expired photos are deleted every night; the scan record stays (1–730 days).	90 days
Hybrid Wi-Fi verification / Company Wi-Fi name	When GPS is weak, the area is widened a limited amount for a device on the company Wi-Fi. Only works with clients that report the network name (see the note below).	Off
BLE beacon support	Bluetooth beacon proximity widens the area a limited amount when GPS is weak. Only works with clients that report beacons (see the note below).	Off
IP restriction / Allowed IP addresses	Scans only from allowed IP addresses. Full address (88.245.10.4), CIDR (10.0.0.0/24) or wildcard range (88.245.11.*). Employees on mobile data cannot scan.	Off

Note: Fake location, root/jailbreak, Wi-Fi network name and beacon checks only take effect when the scanning client reports this information (e.g. a native client or an API integration). The Teamso web Scan QR screen and the current mobile app, which opens that screen as a web view, do not report it; the descriptions on the screen say so too. So Fake location (fake GPS) detection, Root / Jailbreak detection, Hybrid Wi-Fi verification, BLE beacon support and the location's WiFi SSID (Hybrid) field currently do not affect whether a scan is accepted. Scans are secured by the location area, dynamic QR codes, Device binding, Photo verification and IP restriction.

QR Configuration

Setting	Description	Default
Default QR type	The type preselected for new QR codes (Dynamic or Static). Existing codes do not change.	Dynamic
Dynamic QR refresh interval	The preset for new dynamic codes. Cannot exceed the Code validity.	60 s
Screenshot prevention	The code is hidden when the tab goes to the background, right click is blocked, dynamic codes cannot be downloaded or printed.	On
Signature algorithm	HMAC-SHA256 or HMAC-SHA512. Changing it does not break existing codes.	HMAC-SHA256
Code validity	How long a rotating code can be scanned after it is generated (30–600 s). Does not apply to static codes.	90 s
QR screen readability mode	The code is shown on a white background with high contrast; supporting browsers keep the screen from dimming.	On

Notifications

In the Notification Matrix each row is an event (e.g. Late arrival, Absence, Excuse submitted, Daily summary, Webhook delivery failed). The columns on the left pick the channel (Push, SMS, E-mail), those on the right the recipient (Admin, Manager, Employee). Clicking a column header turns that column on or off for every event. A row with no channel or recipient says "reaches nobody".

Admin: company administrators and those with PDKS admin permission. Manager: the employee's line manager and the PDKS managers responsible for the employee's branch. Employee: the employee the event belongs to.
The daily summary, the pending excuse reminder and the webhook warning do not belong to a single employee, so on these rows Manager means all managers and Employee all active employees.
Daily summary and Excuse pending approval go out every day at 19:00 (company time).
The employee who sent an excuse is always told about the approval or rejection, even when the Employee column is not ticked.
SMS goes only to people with a mobile phone registered in the system.

Integration & API

This tab lets external software such as accounting, payroll or reporting systems reach PDKS data.

In API Settings click Generate Key (while there is no key yet, the Generate Key button in the table does the same), enter the Key Name and choose the validity (30, 90, 365 days or unlimited ∞). The key is shown only once; store it safely. If you think it leaked, use Renew or Revoke.
The key can only read (records, locations, discrepancies, weekly plan, summary); it cannot add records, change settings or scan QR codes. It is sent in the X-Teamso-Api-Key header. The Endpoint List and Download Postman Collection are meant for whoever builds the integration. The key works only while the company is active and has the PDKS package.
In Webhook Settings use Add Webhook to set the Target URL (must start with https://) and the Subscribed events. The Secret Key is shown only once; change it with Regenerate Secret. Send a trial message with Send test and follow the results in Delivery History.
Failed deliveries are retried after 1 min, 5 min, 30 min, 2 h and 6 h; if all fail, the Webhook delivery failed notification is sent.

Change History

Change History at the top right shows who changed what and when. The Configuration changes and All activity tabs at the top of the window pick the scope and show how many records each holds. Search with the Search person, action, detail box and filter with the Person, Action type and Date chips; Clear all removes the filters. Automatic actions appear as System. The Detail column names the person a record is about (e.g. "Person: Ayşe Yılmaz"); if that person is no longer in the list it shows "Unknown person". The pages are at the bottom of the list; on narrow screens the records are shown as cards.

Result

Saved settings apply to scans made afterwards; past scans are not re-evaluated. The Code validity applies to every rotating code immediately; the default type and refresh interval only preset new codes.

Common issues

Symptom: Save Settings does nothing and "Fix the highlighted fields before saving" appears.
Cause: A field is invalid (e.g. late thresholds out of order, an empty list with IP restriction on, a refresh longer than the code validity).
Solution: Fix the highlighted field.

Symptom: You turned on a fake GPS, root, Wi-Fi or beacon setting but scans did not change.
Cause: The app that scans does not send this information (see the note in Location & Security).
Solution: For security use Device binding, Photo verification, IP restriction and dynamic QR codes.

Symptom: An external system gets 403 with the API key.
Cause: The key can only read (GET), or the company has no PDKS package.
Solution: Actions other than reading need an employee session; check the package status.

Configuring PDKS settings (general, security, QR, notifications, integration)