SMLock (TTLock) management platform for multi-building portfolios
Vega Access connects to your company’s SMLock cloud account (TTLock account) and turns a flat list of locks into buildings, units and doors your whole team can manage. This page lists what the integration actually does today.
What SMLock is, in one paragraph
SMLock is the platform inside many smart locks sold under different brand names: the electronics, the Bluetooth protocol, the gateways and the cloud. Those locks are set up with the SMLock app (TTLock). The app is made for an owner and a handful of doors. Vega Access uses the same SMLock cloud, through its cloud API, to run those locks at building scale. If you are not sure whether your lock runs on SMLock, the compatible locks page shows how to check in two minutes.
How the connection works
- One SMLock account for your company. We create an SMLock cloud account (TTLock account) for your workspace, or you connect the one you already use. Locks stay in that account; Vega Access works with it on your behalf.
- Locks and gateways are paired. Your installer pairs locks and gateways under that account and links each lock to its gateway. The Vega Access installer app, now rolling out, can also pair a lock over Bluetooth and register it in the same account.
- Import and place. Vega Access reads the account’s locks and gateways and you place each lock on its building, floor, unit or common door, in bulk for larger sites.
- Run it from the panel. From then on, cards, codes, unlocks and history are handled in Vega Access, by the people whose role allows it.
What Vega Access does with each SMLock lock
| Function | What happens |
|---|---|
| Lock and gateway import | Reads every lock and gateway of the account, with lock details and battery level. |
| Cards and fobs | Adds a card to the locks it should open with a start and end date, changes its validity period, and removes it from the lock. |
| PIN codes | Creates permanent or time-limited codes and lists the codes stored on a lock. |
| Phone keys and fingerprints | Lists the phone keys (eKeys) and fingerprints registered on a lock, so you can see every way into a door. |
| Remote unlock and lock | Opens or locks a door through its gateway, after a confirmation, with the actor recorded in the audit log. |
| Door state | Reads whether a lock reports itself locked or unlocked, on models that support it. |
| Entry history | Brings the lock’s unlock records into Vega Access, by door, card or method and time. |
| Gateway health | Shows whether each gateway is online, how many locks it serves and the signal between a lock and its gateways. |
| Battery | Shows battery levels and alerts your technician below the threshold you set per building. |
Available credentials and functions depend on the lock model. Without a gateway, a lock still opens with what it stores, but changes need someone on site with a phone.
What you get that the SMLock app alone does not give you
- Buildings, floors and units instead of one flat list of locks.
- Roles: company admin, building managers and technicians, each limited to their buildings, each with their own sign-in and two-factor authentication.
- One card for several doors: the unit door and the common doors it should open, with lost, broken and disabled statuses kept with their history.
- Tenants: a tenant list per unit, move-in and move-out dates, and app invites by email.
- A portfolio audit trail of every entry and every admin action, searchable and exportable.
- Common doors on WLock in the same panel, through the WLock (UniFi Access) integration.
Gateways: G2, G3 and G3P
Remote functions need an SMLock gateway near the locks. G2 uses Wi-Fi, G3 uses wired Ethernet, and G3P is the wired version powered over Ethernet (PoE). For apartment and office buildings we recommend wired G3P gateways, usually one or more per floor; placement is checked during a site survey. Gateways only need outgoing internet, and a UPS on the PoE switch keeps them online through short power cuts.
Where your data lives
Vega Access is hosted in a Canadian data centre with encrypted daily backups. Locks also talk to the SMLock cloud, which is operated by the lock platform and may be outside Canada. Vega Access keeps its own copy of buildings, tenants, cards and history, so your records do not depend on the lock app.
Who it is for
Property managers with SMLock-based locks in several buildings (property managers), condo syndicates who want control of common doors (condo access control), landlords who change tenants every year (rental buildings), and offices with suites and garages (offices and parking). Plans include a number of SMLock doors; see plans or count your doors with the calculator.
SMLock integration questions
Do we keep using the SMLock app?
Your installer uses it (or the Vega Access installer app as it rolls out) to pair locks. Day-to-day management moves to Vega Access, so your team does not share one app login.
Our locks are in an installer’s SMLock account. Can we still use them?
Locks held in someone else’s account can be transferred or reset and paired again under your company’s account. We walk you through it.
Is Vega Access affiliated with TTLock?
No. Vega Access is independent software that works with the SMLock platform through its cloud API. TTLock is a trademark of its owner.
Related pages
See your buildings in Vega Access
Tell us about your doors and we’ll walk you through Vega Access on a short call — with your own buildings in mind, not a canned slideshow.
- Bring your lock models — we’ll confirm what is SMLock-based and what gateway you need.
- See the real panel — buildings, cards, tenants, remote unlock and the audit log.
- Get a tailored quote — for your doors, buildings and support level.
Prefer the phone? Call +1 (833) 330-8080.
Ready to set up? Request access to a workspace · Already a client? Sign in