Understanding Locks and Keys in Unloc

This guide explains how Locks and Keys work within the Unloc Platform, including their relationships to Projects and how they enable physical access control through mobile devices.

What is a Lock?

A Lock is the digital representation of a physical lock in the Unloc system. Locks represent any physical access point that can be operated with a mobile key, including:

• Doors (residential, commercial, office)
• Padlocks
• Mailboxes
• Gates
• Any other physical access point compatible with Unloc

Lock Characteristics

Exclusive Project Membership:

• Each Lock entity belongs to exactly one Project
• A Lock entity cannot belong to multiple Projects simultaneously
• All Keys for a Lock must be created within that Lock's Project

Lock Identity:

• Each Lock has a unique identifier in the system
• Locks maintain connection to their physical hardware through Lock Connections

Physical Hardware vs. Lock Entities

It's important to understand the distinction between the physical lock hardware and the Lock entities in the Unloc system:

Physical Lock Hardware:

• The actual smart lock device installed on a door, gate, or other access point
• Has a unique hardware identifier from the manufacturer
• Exists as a single physical object in the real world

Lock Entities:

• Digital representations of physical hardware in the Unloc Platform
• Each Lock entity belongs to exactly one Project
• Multiple Lock entities can point to the same physical hardware

Locks in Subprojects

While Locks belong exclusively to a parent Project, they can be referenced by multiple Subprojects:

• Subprojects hold references to Locks (not ownership)
• Multiple Subprojects can reference the same Lock
• Each Subproject can create its own Keys for the referenced Locks
• When a Lock is removed from a Subproject, all Keys for that Lock within that Subproject are automatically deleted

What is a Key?

A Key represents a user's ability to lock and unlock a specific Lock. Keys are the core mechanism for granting access in the Unloc Platform.

How Keys Work

Visibility:

• Keys are visible to users in the Unloc mobile app
• Keys appear automatically when a user logs into the app with their mobile number
• Users can see all Keys assigned to their mobile number across all Projects

Key Creation:

• Keys are created within the context of a specific Project or Subproject
• Each Key is associated with one Lock
• Keys are assigned to a mobile phone number
• The user does not need to have the Unloc app installed at the time of Key creation

Key Activation:

• Keys become available to users as soon as they log into the Unloc App
• No additional activation or acceptance step is required
• Keys work immediately upon app login

Key Types and Restrictions

Permanent Keys

Permanent Keys remain active until explicitly revoked by an administrator.

Use cases:

• Residents with ongoing access to their building
• Staff members with continuous access to facilities
• Property managers with long-term access rights

Time-Limited Keys

Time-limited Keys are only active during specific periods.

Validity Period:

• Keys can be set to work only between specific start and end dates
• Example: A contractor needs access from January 1 to January 31

Time Restrictions:

• Keys can be restricted to specific timeframes within each day
• Example: A delivery person has access only between 9 AM and 5 PM on weekdays
• Time restrictions can be combined with date ranges

Use cases:

• Temporary contractors or service personnel
• Delivery services with specific time windows
• Guests with limited-duration access
• Cleaning services with scheduled access times

Keys and Multiple Projects

The same user (same mobile phone number) can have Keys in multiple Projects:

• Each Project creates its own Keys for that user
• The user sees all Keys from all Projects in their app
• Keys from different Projects appear together in the user's app
• Each Project manages its own Keys independently

Example:

Maria works as a building manager for two different property companies:

• Property Company A: Creates Keys for Maria to access 5 buildings they manage
• Property Company B: Creates Keys for Maria to access 3 buildings they manage

Maria logs into the Unloc App once with her mobile number and sees all 8 building Keys together. Each property company can only manage their own Keys and cannot see or revoke Keys created by the other company.

Keys in Subprojects

Subprojects have their own Key management capabilities with scoped permissions:

Subproject Key Creation

• Subproject administrators can create Keys for Locks referenced in their Subproject
• Keys created in a Subproject are isolated from other Subprojects
• Each Subproject maintains its own set of Keys, even for shared Locks

Key Isolation Example

Scenario: A building Project has two Subprojects for different wings:

Subproject: East Wing

• References Lock: "Main Entrance"
• Administrator creates Key for maintenance worker John (+1-555-0100)

Subproject: West Wing

• References Lock: "Main Entrance" (same Lock)
• Administrator creates Key for maintenance worker John (+1-555-0100)

Result:

• John receives two separate Keys for "Main Entrance" in his app
• East Wing administrator can only manage the Key they created
• West Wing administrator can only manage the Key they created
• Each can revoke their own Key independently

Updated on: 23/01/2026