Skip to main content

Livo Integration

Native integration with the Livo application for managing visitors and residents in residential complexes.

Concept​

Livo is a mobile application that allows:

  • Residents to schedule visitors
  • Front desk to manage accesses
  • Visitors to receive digital invitations
  • Full integration with ACCELERO

Configuration​

Path: Advanced > System > Integrations - Livo

General Settings​

FieldDescription
OperatorOperator responsible in the system logs
Livo authentication token (condToken)Unique token provided by Livo
Include vehicle plate in the fieldCustom field to store the plate
Default category for new residentsCategory when importing residents
Event typesEvent types for regular/recurring visits
Default status of recurring eventsEnabled or disabled
Schedule timeNormal or extended

Authentication Token​

Unique token for each installation, provided by Livo.

Obtaining

Request the token directly from the Livo team.

Vehicle Plate​

When the visitor enters a plate in Livo:

  • One-off visit: Plate associated with a Custom Field of the Event
  • Recurring visit: Plate associated with a Custom Field of the Visitor

Recommendation: Configure the field to be associable with people AND events.

See Custom Fields for configuration.

Schedule Time​

Defines the start/end times of the visits created by Livo:

OptionBehavior
Normal timeExactly the times indicated by the resident
Extended timeAllows early arrivals/delays according to Livo

Unit Binding​

Tab: Units

Relates units registered in Livo with companies in ACCELERO.

Process:

  1. Click on "Update units"
  2. The system fetches all units registered in Livo
  3. Perform the relationship in the table:
    • Livo Unit ↔ ACCELERO Company
  4. Save settings
Deployment

Perform the unit binding at least once during system deployment.

How it works​

Visit Scheduling​

Resident in the Livo app:

  1. The resident schedules a visitor
  2. Enters the data (name, document, plate, time)
  3. Livo sends the data to ACCELERO
  4. ACCELERO creates an event with the configured status:
    • Pre-registered: No automatic authorization
    • Authorized: With automatic authorization

Status by company:

  • It is possible to configure different rules per unit/company
  • Operational flexibility

Resident Import​

The system automatically imports residents from Livo:

Process:

  1. Livo sends resident data
  2. ACCELERO imports them disabled
  3. Residents are automatically associated:
    • With the corresponding company (according to the binding)
    • With the configured default category
  4. Residents appear in "Livo Pending" (dashboard)
  5. The operator validates or rejects each resident

Livo Pending screen:

  • Accessible via dashboard/home screen
  • Shows imported residents awaiting validation
  • The operator can enable (validate) or keep disabled (reject)

Requirements to Function​

For scheduling to work:

  1. Identical document: Person in Livo and ACCELERO with the same document
  2. Association with the company: Person associated with the relevant company in ACCELERO

Visit Types​

Regular Visits​

Single/scheduled visits.

Configuration:

  • Defines the corresponding ACCELERO event type

Example:

Livo regular visit → Event type "ONE-OFF VISIT" in ACCELERO

Recurring Visits​

Visits that repeat on multiple dates.

Configuration:

  • Defines the corresponding ACCELERO event type
  • Defines the default status (enabled/disabled)

Disabled status:

  • Created events require operator authorization
  • Greater control

Enabled status:

  • Created events come already authorized
  • More autonomy for residents

Operational Flow​

Scenario 1: One-off Visit​

1. Resident schedules a visit in Livo
2. Livo → ACCELERO (creates event)
3. Status: According to the company configuration
4. Visitor receives a digital invitation
5. Visitor presents the QRCode at the front desk
6. ACCELERO validates and grants access

Scenario 2: New Resident​

1. Resident registered in Livo
2. Livo → ACCELERO (imports resident)
3. Resident appears in "Livo Pending"
4. Operator validates the data
5. Operator enables the resident
6. Resident can schedule visitors

Scenario 3: Recurring Visit​

1. Resident creates a recurring visit (e.g., housekeeper)
2. Livo → ACCELERO (creates multiple events)
3. Status: According to the configuration
4. If disabled → Operator authorizes each event
5. If enabled → Events already authorized
6. Visitor has access on the configured dates

Best Practices​

  1. Configure unit binding: Essential for correct functioning

  2. Define the default category: Facilitates resident import

  3. Validate imported residents: Review "Livo Pending" regularly

  4. Use custom fields: To store the vehicle plate

  5. Test with a pilot unit: Validate before releasing to everyone

  6. Train residents: Teach correct use of the app

  7. Monitor logs: Track event creation via Livo

  8. Define clear rules: Recurring visits enabled or not?

Troubleshooting​

The schedule does not reach ACCELERO​

Causes:

  • Incorrect token
  • Different document between Livo and ACCELERO
  • Unit binding not configured
  • Person not associated with the company

Solution: Check the token, documents, binding, and associations

The resident cannot schedule​

Cause: Resident not validated or disabled

Solution: Check "Livo Pending", enable the resident

The vehicle plate does not appear​

Cause: Custom field not selected

Solution: Configure the field in "Include vehicle plate in the field"

Recurring visits blocked​

Cause: Default status configured as "disabled"

Solution: The operator must authorize manually or change the configuration

Event Segmentation by Company Group​

It is possible to segment events by company group in Livo, allowing each group (tower, block, etc.) to view only the events relevant to its units.

Notification for Visits without a Prior Invitation​

When a visit is registered without a prior invitation (unexpected visitor), the system sends a notification to the visited person informing them about the visit, allowing the resident to authorize or refuse access.

Update of Registration Data​

Livo allows the update of registration data coming from integrations, with emphasis on the data updated by the resident directly in the application.

Next Steps​