Skip to main content

Pode Subir Integration

Native integration with the Pode Subir application for managing visitors and deliveries in residential complexes.

Concept​

Pode Subir is a mobile application focused on:

  • Visitor and delivery management
  • Scheduling by residents
  • Real-time notifications
  • Simple integration with ACCELERO

Configuration​

Path: Advanced > System > Integrations - Podesubir

Required Settings​

FieldDescription
OperatorOperator that appears as responsible in the logs
Authentication tokenUnique token generated together with Podesubir
Event typeEvent type for visits created by the app

Operator​

Operator that will appear in the system logs as responsible for creating the schedules.

Recommendation: Create a specific operator such as "System - Podesubir" to facilitate auditing.

Authentication Token​

Unique token for each installation.

Obtaining: Generated together with the Podesubir team during deployment.

Confidentiality

Keep the token secure. Do not share it publicly.

Event Type​

Defines which ACCELERO event type will be used for visits created by Podesubir.

Example:

Configured event type: "PODESUBIR VISIT"

Resident schedules a visit in the app
→ ACCELERO creates an event of type "PODESUBIR VISIT"
→ Visitor receives a QRCode

See Events for event type configuration.

How it works​

Visit Scheduling​

Flow:

  1. Resident schedules a visit in the Podesubir app
  2. Podesubir sends the data to ACCELERO via API
  3. ACCELERO creates an event with the configured status:
    • Pre-registered: No automatic authorization
    • Authorized: With automatic authorization
  4. Visitor receives a notification/QRCode
  5. Visitor presents the QRCode at the front desk
  6. ACCELERO validates and grants access

Event Status​

The status of the created events is defined by company/unit:

"Pre-registered" status:

  • Visit created but not authorized
  • Operator or authorizer must approve
  • Greater control

"Authorized" status:

  • Visit created already automatically authorized
  • Visitor can already access
  • More autonomy for residents
Flexibility

Different companies/units can have different rules. Configure according to the needs of each one.

Use Scenarios​

Scenario 1: Simple Visit​

1. Resident João schedules a visit for Maria
2. Podesubir → ACCELERO (creates event)
3. Maria receives a QRCode by email/SMS
4. Maria arrives and presents the QRCode
5. ACCELERO validates and grants access
6. Log records entry via Podesubir

Scenario 2: Delivery​

1. Resident schedules a delivery (Amazon, Correios)
2. Podesubir → ACCELERO (creates delivery event)
3. Courier presents identification
4. Front desk validates in the system
5. Delivery is authorized
6. Complete log of the event

Scenario 3: Service Provider​

1. Resident schedules a technician/provider
2. Sets the arrival time
3. Podesubir → ACCELERO
4. Provider receives a QRCode
5. Access during the scheduled time
6. Full control of entry/exit

Integration with Check-in​

When integrated with Visitor Check-in:

  1. Visitor arrives before authorization
  2. Performs check-in at the front desk
  3. Resident receives a notification
  4. Resident authorizes via the app
  5. Visitor is granted access

A more agile and secure process.

Best Practices​

  1. Configure a specific event type: Facilitates identification in reports

  2. Define rules per company: Use the appropriate status for each unit

  3. Integrate with check-in: Improves the visitor experience

  4. Train residents: Teach correct use of the app

  5. Monitor logs: Track events created via Podesubir

  6. Configure notifications: Ensure visitors receive the QRCode

  7. Test before releasing: Validate the complete flow with a pilot unit

Troubleshooting​

The schedule does not reach ACCELERO​

Causes:

  • Incorrect authentication token
  • Connectivity issue
  • Event type not configured

Solution: Check the token, connectivity, and configuration

The visitor does not receive the QRCode​

Causes:

  • Incorrect email/phone
  • SMTP server not configured
  • Notifications disabled

Solution: Check the contact data and Email Server

Status always pre-registered​

Cause: Company configuration to not authorize automatically

Solution: Adjust the company configuration if you want automatic authorization

Logs do not show the correct operator​

Cause: Operator not configured in the integration

Solution: Configure the "Operator" field on the integration screen

Next Steps​

  • Events - Configure event types
  • Check-in - Integrate with visitor check-in
  • Companies - Configure rules per company
  • Reports - Analyze Podesubir visitors