Articles on: General

Understanding Users in Unloc


This guide explains how users are represented and managed within the Unloc Platform, including the distinction between App Users and Managed Users, and how they interact with Keys and Projects.


User Types in Unloc


The Unloc platform uses two different user representations:


  • App Users represent individuals logged into the Unloc mobile app with their personal profile
  • Managed Users represent how administrators define and track users within their Projects
  • Both representations refer to the same individual with the same mobile phone number
  • The same person can have multiple Managed User profiles across different Projects


App Users vs. Managed Users


The Unloc platform distinguishes between two user representations: App Users and Managed Users. While both represent the same individual with the same mobile number, they serve different purposes in the system.



App Users


An App User refers to a user logged into the Unloc app. This is the user's personal identity within the app.


Characteristics:


  • The app displays the name and image that the user has personally set in their profile
  • This is the user's self-defined identity
  • App Users control their own profile information
  • One App User account per mobile phone number


Managed Users


A Managed User represents how you (the administrator) define and track a user within your Project. This allows you to assign custom names and metadata relevant to your specific organizational needs.


Characteristics:


  • Created and managed by Project or Subproject administrators
  • Can have custom names assigned by administrators
  • Can include custom metadata relevant to your organization
  • Separate Managed User profiles can exist for the same individual across different Projects




How Users Relate to Projects


Multiple Projects, Multiple Managed Users


Important: If you create Keys for the same user (same mobile phone number) across multiple Projects, you will create a separate Managed User for each Project.


Example:


Sarah Johnson has the mobile number +1-555-0123. She works as a maintenance contractor for two different property management companies:


  • Company A's Project: Creates a Managed User named "Sarah - Maintenance" with metadata indicating her contractor ID
  • Company B's Project: Creates a Managed User named "S. Johnson" with different metadata for their tracking system


Both Managed Users are associated with the same mobile number (+1-555-0123), but each Project can track and label her differently. When Sarah logs into the Unloc App, she sees all Keys from both Projects, regardless of how each administrator has named her Managed User profile.


Creating Keys for Users


Keys are associated with mobile phone numbers and do not require the user to exist in the app at the time of creation.


Key Creation Process:


  1. Administrator creates a Key for a specific Lock
  2. Key is assigned to a mobile phone number
  3. A Managed User is created (if one doesn't already exist for that number in the Project)
  4. The Key becomes available to the user as soon as they log into the Unloc App


Important: Users don't need to have the Unloc app installed before you create Keys for them. Once they install the app and log in with their mobile number, all Keys created for that number will automatically appear.




User Management in Subprojects


Within Subprojects, user management follows the same principles but with scoped visibility:


Subproject Administrator Capabilities


  • Create Managed Users within their Subproject
  • Assign Keys to users for Locks within their Subproject
  • View only the Managed Users within their own Subproject
  • Update and manage user metadata within their Subproject scope


User Isolation Between Subprojects


Critical security feature: If the same mobile phone number has Keys in multiple Subprojects within the same parent Project:


  • Each Subproject maintains its own Managed User profile for that number
  • Subproject A's administrator cannot see Subproject B's Managed User information
  • The user (in the app) sees all Keys from all Subprojects seamlessly


Example:


Building Manager creates two Subprojects:

  • Subproject: North Wing managed by Alice
  • Subproject: South Wing managed by Bob


They both create Keys for the same maintenance worker (mobile: +1-555-0100):

  • Alice creates a Managed User: "John - HVAC Tech"
  • Bob creates a Managed User: "J. Smith - Maintenance"


Alice cannot see Bob's Managed User profile, and vice versa. The maintenance worker sees all Keys from both wings in their app.


Updated on: 23/01/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!