Event types in Homelok activity
Overview
The following table lists all the possible event types that can display in the Salto Homelok activity section. It also includes examples of how these events might display and any additional detail about the event, where necessary.
List of events
| Event | Icon | Example | Additional information |
|---|---|---|---|
| Door created | 221 B front door created | Includes information about the manager who created the door. | |
| Door updated | 221 B front door details modified | A detail could refer to a change of opening mode or a change to the door's display name. Includes information about the manager who made the changes. | |
| Door deleted | 221 B front door deleted | Includes information about the manager who deleted the door. | |
| Door unlocked | Sherlock Holmes unlocked 221 B front door with physical key | In other words: access was granted to a user at a specific door using a specific key type. | |
| Door locked | Sherlock Holmes locked 221 B front door with physical key | In other words: a user locked a specific door using a specific key type. | |
| Door forced open | 221 B front door forced open | More info on door forced open events. | |
| Door closed | 221 B front door closed | More info on door closed events. | |
| Access denied | Sherlock Holmes denied access to 221 B front door | Access could be denied for various reasons including: expired key, unactivated key, insufficient access rights, outside permitted schedule, or invalid access code. See also the section on expiration and validity. | |
| Door left open | 221 B front door left open | More info on door left open events. | |
| Access granted | Sherlock Holmes granted access with physical key | Access granted by a controller or device that manages multiple destinations, such as an elevator or multi-door system. | |
| Access created | Access All doors created | Includes information about the manager who created the access. | |
| Access updated | Access All doors details modified | A detail could refer to the schedule associated with the specific access. Includes information about the manager who made the changes. | |
| Access deleted | Access All doors deleted | Includes information about the manager who deleted the access. | |
| Door added to access | Door 221 B front door added to access All doors | Includes information about the manager who added the door to the access. | |
| Doors added to access | 6 doors added to access All doors | Indicates the number of doors added to an access when multiple doors are added at the same time. Includes information about the manager who performed the batch operation. | |
| Door removed from access | Door 221 B front door removed from access All doors | Includes information about the manager who removed the door from the access. | |
| Doors removed from access | 6 doors removed from access All doors | Indicates the number of doors removed from an access when multiple doors are removed at the same time. Includes information about the manager who performed the batch operation. | |
| User created | Sherlock Holmes created | Includes information about the manager who created the user. | |
| User updated | Sherlock Holmes details modified | A detail could be a change of email address or a change to the user's display name. Includes information about the manager who made the changes. | |
| User blocked | Sherlock Holmes blocked | See the section on blocking users for more information. Includes information about the manager who blocked the user. | |
| User unblocked | Sherlock Holmes unblocked | See the section on blocking users for more information. Includes information about the manager who unblocked the user. | |
| User deleted | Sherlock Holmes deleted | Includes information about the manager who deleted the user. | |
| User access created | Sherlock Holmes assigned access All doors | Includes information about the manager who created the user access association. | |
| User access updated | Sherlock Holmes access All doors details modified | A detail could be a change of schedule for that specific access. Includes information about the manager who made the changes. | |
| User access deleted | Access All doors removed from Sherlock Holmes | Includes information about the manager who removed the access from the user. | |
| Physical key assigned | Sherlock Holmes assigned physical key - UID: 12345678901234 | Physical keys like keycards or fobs display the key's UID upon assigning. Includes information about the manager who assigned the key. | |
| Physical key canceled | Sherlock Holmes physical key canceled | Includes information about the manager who canceled the key. | |
| App key assigned | Sherlock Holmes assigned app key | Includes information about the manager who assigned the key. | |
| App key canceled | Sherlock Holmes app key canceled | Includes information about the manager who canceled the key. | |
| Apple Wallet key assigned | Sherlock Holmes assigned Apple Wallet key | Includes information about the manager who assigned the key. | |
| Apple Wallet key canceled | Sherlock Holmes Apple Wallet key canceled | Includes information about the manager who canceled the key. | |
| Unit moved in | Unit 221 B Baker Street moved in | See the section on moving in units. Includes information about the manager who performed the move in. | |
| Unit moved out | Unit 221 B Baker Street moved out | See the section on moving out units. Includes information about the manager who performed the move out. | |
| Unit created | Unit 221 B Baker Street created | Includes information about the manager who created the unit. | |
| Unit updated | Unit 221 B Baker Street details modified | A detail could be a change of the unit's name, for example. Includes information about the manager who made the changes. | |
| Unit deleted | Unit 221 B Baker Street deleted | Includes information about the manager who deleted the unit. | |
| Emergency key created | Emergency key Fire department created | Includes information about the manager who created the emergency key. | |
| Emergency key updated | Emergency key Fire department updated | The name of the key is changed, for example. Includes information about the manager who made the changes. | |
| Emergency key deleted | Emergency key Fire department deleted | Includes information about the manager who deleted the emergency key. | |
| Emergency key unlocked a door | Emergency key Fire department unlocked 221 B front door |
Access denied reasons
When access is denied to a user, the system provides specific reasons to help you understand why the access attempt failed. The following table shows the possible reasons and what they mean:
| Reason | Description |
|---|---|
| Key expired | The user's key has passed its expiration date and is no longer valid. |
| Key not activated | The user's key has not yet reached its activation date and time. |
| Key lacks access rights | The user's key does not have permission to access this door. |
| Outside permitted schedule | Access was attempted on a day when the user's schedule does not allow entry (for example, attempting access on a weekend when only weekday access is permitted). |
| Invalid passcode | The numeric passcode entered on the device keypad was incorrect or does not meet the required format. |
| Insufficient battery | Access was denied because the lock's battery doesn't have enough power to unlock. The lock mechanism cannot operate due to insufficient battery charge. Contact maintenance to replace device batteries. |
| Unspecified | The system was unable to determine a specific reason for the access denial. |
For more information about managing user schedules and key validity periods, see the section on expiration and validity.
Access denial priority
The system evaluates access denial reasons in the following priority order:
Access attempt
↓
┌─────────────────────┐
│ 1. Key validity │ ← Highest priority
│ │
│ Is the key active │
│ and not expired? │
└─────────┬───────────┘
│
├─ NO → Key not activated / Key expired
│
↓ YES
┌─────────────────────┐
│ 2. Door permissions │
│ │
│ Does the key have │
│ access to this door?|
└─────────┬───────────┘
│
├─ NO → Key lacks access rights
│
↓ YES
┌─────────────────────┐
│ 3. Schedule check │
│ │
│ Is access allowed │
│ at this time? │
└─────────┬───────────┘
│
├─ NO → Outside permitted schedule
│
↓ YES
┌─────────────────────┐
│ ✓ Access granted │ ← Lowest priority
└─────────────────────┘