Question 1

How does the AttendFlow licensing model work?

Accepted Answer

AttendFlow is provided on an annual per-organization license with RS256 cryptographically signed keys. There are no hidden per-user micro-fees or sudden price hikes. You get access to the complete source code, deployment scripts, and self-hostable server for one transparent annual price.

Question 2

Can we rebrand AttendFlow under our own corporate identity (White-label)?

Accepted Answer

Absolutely. Our Enterprise tier includes complete white-labelling: your company logo, custom app bundle IDs, customized domain (e.g. attendance.yourcompany.com), custom CSS brand colors, and white-labelled mobile builds published directly to Google Play and Apple App Store.

Question 3

Is there a free trial or proof-of-concept (PoC) environment available?

Accepted Answer

Yes! We provide an interactive 14-day sandboxed live demo instance for IT teams and HR executives to test live facial punches, mobile geofencing, multi-branch shifting, and payroll export formats prior to purchase.

Question 4

What infrastructure do I need to self-host AttendFlow?

Accepted Answer

AttendFlow runs seamlessly on any Linux (Ubuntu, Debian, CentOS, RHEL) or Windows server with Docker & Docker Compose, or standard Node.js & PostgreSQL environments. A single 2-core VM with 4GB RAM easily handles 1,000+ active employees.

Question 5

How do software updates work for self-hosted instances?

Accepted Answer

System updates are engineered for zero downtime. Updates are delivered via verified Docker image tags or git pulls with automatic Prisma schema migrations. Your attendance logs, employee rosters, and configuration settings remain completely intact and untouched.

Question 6

How do we configure automated database backups and disaster recovery?

Accepted Answer

AttendFlow includes built-in automated PostgreSQL dump utilities. You can schedule encrypted daily or hourly backups to local disk or automatically push them to AWS S3, Google Cloud Storage, Azure Blob, or an on-premise SFTP/NAS server.

Question 7

Where is our biometric and employee attendance data stored?

Accepted Answer

100% on your own infrastructure. AttendFlow never transmits employee selfies, GPS coordinates, or biometric hashes to any external cloud or third-party servers. You retain total data sovereignty in compliance with GDPR, HIPAA, DPDP, and local statutory labor laws.

Question 8

Are biometric face vectors reversible into original photos?

Accepted Answer

No. AttendFlow converts facial landmarks into one-way 512-dimensional mathematical embeddings stored with AES-256 encryption at rest. It is mathematically and cryptographically impossible to reverse-engineer or reconstruct an employee's original face photo from the stored vector.

Question 9

How does AttendFlow handle GDPR employee consent and right to deletion?

Accepted Answer

AttendFlow includes built-in digital consent opt-in workflows upon initial mobile onboarding and an automated data retention purge policy. With one click, administrators can anonymize or permanently delete biometric vectors while maintaining audit-compliant payroll summaries.

Question 10

Can we integrate AttendFlow with existing biometric hardware or ERPs?

Accepted Answer

Yes. AttendFlow provides high-throughput REST APIs and webhook dispatchers. You can push punch logs directly from ZKTeco, eSSL, Realtime, Suprema, or Anviz biometric devices, and automatically sync payroll records into SAP, QuickBooks, Zoho Books, Tally, or Workday.

Question 11

Can we synchronize employees automatically with Microsoft Active Directory or Google Workspace?

Accepted Answer

Yes. AttendFlow supports SCIM 2.0 provisioning and SAML 2.0 / OpenID Connect (OIDC) Single Sign-On (SSO). When an employee is onboarded or offboarded in Okta, Azure AD, or Google Workspace, their AttendFlow profile is synchronized automatically.

Question 12

Does AttendFlow provide real-time webhooks for custom internal automations?

Accepted Answer

Yes! AttendFlow dispatches instant HMAC-signed JSON webhooks on key events: punch_created, late_checkin, overtime_exceeded, leave_requested, and geofence_violation. You can listen to these in Slack, Microsoft Teams, Zapier, or your internal HRMS.

Question 13

What platforms are supported for mobile and desktop attendance?

Accepted Answer

AttendFlow provides native Android and iOS mobile applications with selfie verification, offline punch caching, and GPS geofence locking, as well as a Windows and macOS desktop kiosk app for reception desks.

Question 14

How does AttendFlow handle attendance if the internet goes down?

Accepted Answer

Both the mobile app and kiosk client feature an encrypted local SQLite punch buffer. Employees can continue punching in and out seamlessly without internet. The moment network connectivity is restored, all cached punches are synced to your self-hosted server with tamper-evident cryptographic timestamps.

Question 15

Can employees cheat attendance with fake GPS apps or printed photos?

Accepted Answer

No. AttendFlow employs multi-layered anti-spoofing defense: real-time optical 3D liveness and micro-expression blink detection, Android mock-location/GPS-spoofer rejection, developer mode detection, and precise Haversine distance geofence boundary verification.

Question 16

How are night shifts, rotational shifts, and overtime calculated?

Accepted Answer

AttendFlow's shift scheduler natively supports cross-midnight shifts (e.g. 10:00 PM to 6:00 AM), rotational weekly rosters, split shifts, configurable grace periods, and automatic calculation of standard versus overtime hours with customizable rate multipliers.

常见问题解答

还有其他疑问？