Accelero Visitas Integration
The Accelero Visitas integration connects ACCELERO to the Accelero Visitas application, aimed at visit management in residential complexes and companies. Through the app, hosts (residents or employees) register and approve visitors; ACCELERO receives these schedules, creates the visit events, maintains the visitor record, and generates the QR Code used at entry. ACCELERO also returns the visit status to the app (check-in and passes) in real time.
This integration is provided as a plugin (accelerovisitas) and must be installed and enabled by IONGRADE's technical team. Contact support to check compatibility with your version of ACCELERO.
Current plugin version: 1.4.0 — compatible with ACCELERO 2.17.0 or higher.
What the integration does
The plugin establishes a bidirectional channel between ACCELERO and the Accelero Visitas application. The app is responsible for the host's and visitor's experience; ACCELERO remains the source of truth for access control (events, people, cards, and QR Codes).
| Feature | What happens in ACCELERO |
|---|---|
| Visit creation | The app sends a visit and ACCELERO creates the event, performs the upsert of the visitor, and links visitor and visited (unit/company) |
| Recurring visits | The app sends a recurring visit (start date, end date, and days of the week) and ACCELERO records the corresponding recurring event |
| Access QR Code | ACCELERO generates (or reuses) the visitor's dynamic QR Code, valid until the visit's end date |
| Visit status update | The app can update the visit status in ACCELERO; ACCELERO returns check-in, entry, and exit events to the app |
| Departments and approvers | ACCELERO organizes companies into departments and links operators (approvers) to these departments, synchronized with the app |
| App user provisioning | ACCELERO operators can be created or removed as Accelero Visitas users |
| Query of companies and event types | The app queries the companies (units) and the event types enabled for the integration |
Allows residents and employees to manage their own visits from the application, with ACCELERO controlling physical access and the entry QR Code — without manually registering each visitor at the front desk.
Configuration
Navigation path: Settings > Integrations - AcceleroVisitas
The screen has one tab: General.
Configuration screen Settings > Integrations - AcceleroVisitas, General tab, showing the Integration data fields, the Default event type, the Overwrite data of existing people switch, and the Save and Synchronize all buttons.
Integration data
| Field | Description |
|---|---|
| Operator | ACCELERO operator used by the integration as the party responsible for the events created from the app |
| Authentication token (APP > Accelero) | Token that the application uses to authenticate the calls received by ACCELERO |
| Authentication token (Accelero > APP) | Token used by ACCELERO to authenticate the notifications sent to the application |
| AcceleroVisitas URL | Endpoint of the Accelero Visitas service to which ACCELERO sends notifications |
Event type
| Field | Description |
|---|---|
| Default event type | Event type used when creating a visit when the app does not inform a specific type |
Options
| Field | Description |
|---|---|
| Overwrite data of existing people | When active, the visitor's data (name, document, photo, phone, email) sent by the app overwrites the record of an already existing person. When inactive, already registered people do not have their data changed |
Screen buttons
| Button | Function |
|---|---|
| Save | Persists the configuration |
| Synchronize all | Triggers the bulk synchronization of companies, departments, and approvers with Accelero Visitas (see Bulk synchronization) |
The authentication tokens and the Accelero Visitas URL are defined during deployment. Keep them confidential — they authorize the creation of visits and the sending of notifications.
Departments
The plugin adds the Departments entity, used to segment companies (units) and organize which approvers act in each sector. Departments are synchronized with Accelero Visitas.
Navigation path: Settings > Departments
Listing of Departments (Settings > Departments), showing the Code and Department Description columns, the New Department button, and the search.
Department fields
| Field | Description |
|---|---|
| Code | Department identifier code |
| Department Description | Department name/description |
Linking departments to companies
In the editing of a Company, the plugin adds the Departments tab, where departments are associated with that company.
Editing of a Company with the Departments tab open, showing the association of departments to the company (inline addition and listing).
Linking operators to departments
In the editing of an Operator, the plugin adds the Departments tab, where the operator is linked to a company and a department — defining where they act as a visit approver.
Editing of an Operator with the Departments tab open, showing the addition of the Company + Department link and the listing of existing links.
The management of departments and their links is controlled by the Departments - Manage (depManager) permission, assignable to operator profiles.
Fields added to entities
Operator
In addition to the Departments tab, the operator editing gains the Accelero Visitas section, with actions to provision the user in the application:
Accelero Visitas section in the operator editing, showing the Create user in Accelero Visitas and Delete user in Accelero Visitas buttons.
| Action | Effect |
|---|---|
| Create user in Accelero Visitas | Provisions the operator as a user in the application (processed asynchronously) |
| Delete user in Accelero Visitas | Removes the corresponding user in the application (processed asynchronously) |
Company
The company editing receives the Departments tab for associating departments (see Departments).
Event Type
In the editing of an Event Type, the plugin adds the Accelero Visitas section with the option:
Accelero Visitas section in the editing of an Event Type, showing the Do you want to use this event type in the integration? switch.
| Field | Description |
|---|---|
| Do you want to use this event type in the integration? | Marks the event type as available for the integration. Only enabled event types appear as an option in the application |
Integration flows
The flows below are triggered by the Accelero Visitas application through authenticated calls to ACCELERO. There are no dedicated screens for them in ACCELERO — they reflect the plugin's behavior.
Visit creation
Upon receiving a visit from the app, ACCELERO:
- Locates the unit (company) informed as visited;
- Performs the upsert of the visitor (creates the person if it does not exist; updates name, document, document type, phone, email, and photo according to the Overwrite data of existing people option);
- Creates the event with the informed start and end date, using the sent event type or the Default event type;
- Links visitor and visited to the event and triggers, when applicable, the notification to the guest.
Visit creation requires, at minimum: event data (identifier, start date, and end date), visitor data (name, document, phone, and photo), and visited data (unit). Incomplete records are rejected.
Recurring visit
For recurring visits, the app sends, in addition to the event and people data, the days of the week and the period (start date and end date). ACCELERO records the corresponding recurring event. The QR Code is generated from this recurring event, valid until the end date.
Access QR Code
ACCELERO generates a dynamic QR Code for the visitor, valid until the visit's (or recurrence's) end date. If there is already a valid and enabled card/QR Code linked to that visit, it is reused; otherwise, a new one is generated.
Diagram of a visit flow: app creates the visit → ACCELERO creates event and visitor → ACCELERO generates QR Code → visitor presents the QR Code at the front desk → ACCELERO notifies the app (check-in / entry / exit).
Status notifications to the app
ACCELERO returns to Accelero Visitas, in real time, the following visit events:
| Event | When it occurs |
|---|---|
| Check-in | When the guest's check-in is performed |
Entry (entry) | When the visitor passes through an entry channel |
Exit (exit) | When the visitor passes through a channel configured as visit check-out |
Passes through channels configured as check-in do not generate an entry/exit notification for the app.
Status update by the app
The application can update the status of a visit in ACCELERO (for example, cancellation). ACCELERO locates the visit by the app's identifier and applies the new status to the corresponding event-person link.
Bulk synchronization
The Synchronize all button, on the configuration screen, sends to Accelero Visitas the current set of companies, their departments, and the approvers (operators linked to departments).
The synchronization assembles:
- Companies with their associated departments;
- Approvers — operators linked to valid company + department pairs, with name, email, document, and phone.
The synchronization only sends data when there are operator-department links and at least one company with an associated department. Without links, nothing is sent.
Use Synchronize all after creating/changing departments, linking new approvers, or associating departments to companies, to reflect these changes in the application.
Use cases
Enabling the integration
- Request IONGRADE to install the
accelerovisitasplugin. - In
Settings > Integrations - AcceleroVisitas, fill in Operator, the two authentication tokens, the AcceleroVisitas URL, and the Default event type. - Set, in each desired Event Type, the Do you want to use this event type in the integration? option.
- Register Departments and associate them with the companies and the approver operators.
- Click on Synchronize all to send companies, departments, and approvers to the app.
Provisioning an approver in the application
- Edit the Operator who will be the approver.
- In the Departments tab, link the operator to the correct company and department.
- In the Accelero Visitas section, click on Create user in Accelero Visitas.
Receiving a visit scheduled by the app
- The host schedules the visit in the application.
- ACCELERO creates the event and the visitor record automatically.
- The visitor receives/presents the QR Code at the front desk.
- On the pass, ACCELERO notifies the app with the entry event and, on check-out, with the exit event.
Best practices
- Dedicated integration operator: use a specific operator as the party responsible for the events created by the integration, instead of a named account.
- Explicit event types: enable in the integration only the event types actually used for visits by the app.
- Keep links up to date: whenever you change departments or approvers, run Synchronize all.
- Assess data overwrite: use Overwrite data of existing people with caution — it replaces data of already existing records with data coming from the app.
Troubleshooting
App visits are not created in ACCELERO
Possible causes:
- Unit (company) informed by the app does not exist in ACCELERO;
- Required visitor or event data missing;
- Incorrect (APP > Accelero) authentication token.
Solution:
- Confirm that the company/unit exists in the Companies record.
- Check whether the app sends the visitor's name, document, phone, and photo and the event dates.
- Review the Authentication token (APP > Accelero) in the configuration.
Event types do not appear in the app
Possible causes:
- Event type without the Do you want to use this event type in the integration? option checked.
Solution:
- Edit the Event Type and enable the option in the Accelero Visitas section.
App does not receive entry/exit
Possible causes:
- Pass channel configured as check-in (does not notify entry/exit);
- Incorrect AcceleroVisitas URL or (Accelero > APP) token;
- Visit without the integration identifier linked.
Solution:
- Check the controller's channel configuration.
- Review the AcceleroVisitas URL and the Authentication token (Accelero > APP).
Synchronization does not send data
Possible causes:
- No operator-department link registered;
- No company with an associated department.
Solution:
- Register departments, associate them with companies, and link operators to departments.
- Run Synchronize all again.
Integration with other modules
Companies
Companies act as visited units and are segmented by departments. See Companies.
Operators
Operators act as approvers, linked to companies and departments, and can be provisioned as users of the application.
People
Each visitor received from the app generates or updates a record in People.
Events
Visits are recorded as Events (including recurring ones), using the event types enabled for the integration.
Logs and Events
The visitor's physical passes feed the entry/exit notifications sent to the app. See Logs and Monitoring.