Phone: 0 (552) 380 25 25 | Weekdays 10:00–18:00 · Technical support 24/7
SmartPass is a card access control system built by Digital Bridge. It combines door access control, staff time and attendance, and canteen meal counting in one system: a single card read opens the door, records attendance and, where the person is entitled, deducts a meal. 13.56 MHz RFID cards and time-limited QR codes are read on the same terminal.
On most sites the turnstiles run on one system, the time clock on another, and canteen tickets are counted by hand. At month end three lists are compared and every mismatch is chased individually. In SmartPass all three processes share the same record.
The hardware, software and terminal interface were designed by the Digital Bridge team, and the source code is ours. So your site doesn’t have to bend to the product; the product is adapted to your site. For reader and turnstile options, see our card access control hardware page.
When an employee presents a card, the door opens, attendance is recorded and, if they are entitled, a meal is deducted. All three use the same record, so there is nothing to reconcile between systems at month end.
If the authorisation rule allows it, the door opens. Each decision is stored with the rule behind it, so "why was I refused?" has an answer on screen.
Entries and exits go onto the timesheet against the shift plan. No separate time clock is needed.
The meal allowance is deducted at the moment of the read. No end-of-day ticket counting, no handwritten lists.
13.56 MHz RFID cards and time-limited QR codes are evaluated by the same reader. Staff get a permanent card, visitors a single-use QR — both are subject to the same authorisation rules.
"The production team may enter the Warehouse zone during working hours." Rules are written as plainly as that. If two rules clash, the system shows which one wins, and a rule simulator lets you test a change before applying it.
Every read appears on the monitoring screen as it happens. In an emergency all doors lock with a single action, and you get a zone-by-zone list of who is inside.
Zones are modelled on your own site layout: gatehouse, production, warehouse, offices. Permissions follow the zone tree and can include child zones.
Entry and exit records become timesheets against the shift plan. Reports can be exported to your existing payroll system, so hours aren't retyped.
Each organisation runs on its own subdomain and its own database. Head office receives consolidated reports; sites cannot see one another's records.
An access control system records where a person was and when. Under Turkey’s data protection law (KVKK) you need to show how that data is stored, who can see it and when it is deleted. SmartPass treats this as part of the design, and for organisation-wide processes we also offer data protection compliance consultancy.
Each user sees records only for the zones they are authorised for. Role and zone scope are enforced in the core layer, and no module can bypass them.
Which user changed which field to which value is recorded with both the old and the new value. The auditor role views all records read-only.
Each organisation runs in a separate database. Card numbers are never stored in plain text — only an irreversible digest is kept.
Records past their retention period are irreversibly anonymised. Even if an old card is presented again, it cannot be tied back to an identity.
A shift-based production line and a round-the-clock server room can’t share one rule set. SmartPass rules are set by zone, team and time of day, so each site gets the pattern it needs.
Each item is priced separately, so you can see exactly what you are paying for.
Terminal hardware is purchased outright and ownership passes to your organisation. There is no mandatory lease.
Priced by door count, cabling and mounting work, and finalised after an on-site survey.
The software runs on a per-terminal subscription, monthly or annual. Card design is included; card printing is priced separately.
Let’s count the doors and terminals together, then send you an itemised quote after the survey.
+90 (552) 380 25 25 Book a Site SurveySmartPass is a card access control system built by Digital Bridge. It combines door access control, staff time and attendance, and canteen meal counting in one system: a single card read opens the door, records attendance and, if the person is entitled, deducts a meal. 13.56 MHz RFID cards and time-limited QR codes are read on the same terminal.
No. The card read at the access terminal is also the attendance record. Entries and exits are turned into timesheets against the shift plan, and reports can be exported to your existing payroll system. There are no separate lists for turnstiles, attendance and the canteen, so nothing needs reconciling between systems at month end.
No. Staff get a permanent RFID card and visitors a single-use, time-limited QR code. Both are read on the same terminal and follow the same access rules, so a visitor can only pass into the zones they are allowed, within the time they are allowed. There is no separate visitor system or handwritten log to keep.
Rules are written in plain language, for example "The production team may enter the Warehouse zone during working hours." Zones are arranged in a hierarchy that follows your site, such as gatehouse, production, warehouse and office. When two rules conflict, SmartPass shows clearly which one applies, and the rule simulator lets you test a change before applying it.
A SmartPass quote has three line items: hardware, which you buy and own; installation, priced by the number of doors and the fitting work; and a monthly or annual software subscription per terminal. Card design is included, card printing is priced separately. The final figure is given line by line after a site survey that counts doors and terminals.
Card numbers are never stored in plain text; only an irreversible hash is kept. Records past their retention period are anonymised. An audit trail shows who changed which field, with old and new values, and the auditor role has read-only access. Role and zone scope are enforced in the core layer, and each organisation runs on its own subdomain and database.
Have a different question? Ask Us