Pre-Registration (public form)
Pre-Registration provides a public self-service form so that the person themselves (resident, contractor, etc.) fills in their data and sends their photos from the phone, without needing a logged-in operator. Each submission enters a moderation queue inside ACCELERO: an authorized operator reviews and approves (creating or updating the person in the system) or rejects the submission.
The form is accessible by a unique link (with a QR Code), built as a mobile-first wizard in steps, and respects LGPD consent before collecting the data.
This feature is provided as a plugin (precadastro) and must be installed and enabled by the IONGRADE technical team. Contact support to check compatibility with your version of ACCELERO.
Current plugin version: 1.0.1 — compatible with ACCELERO 2.17.0 or higher.
Pre-Registration is one of ACCELERO's self-registration flows. If your goal is to register visitors without moderation, or people with simple approval, see:
What the plugin does
| Feature | What happens in ACCELERO |
|---|---|
| Public self-service form | The person accesses a unique link and fills in their own data in a mobile-first wizard |
| Photo capture from the phone | Facial photo (with face detection), front and back of the document, or file upload when there is no camera |
| Fields per category | Each person category exposes its own set of fields (native and custom) and requires or not each type of photo |
| Vehicle data (optional) | The person can provide the plate, model, and color of the vehicle when the category enables it |
| Moderation queue | Each submission stays pending until an operator approves or rejects it |
| Approval creates/updates the Person | Upon approval, the data becomes a Person registration, linked to the chosen category, with the photos transferred to the standard slots |
| Duplicate detection by CPF | If a person with the same document already exists, the submission is treated as an update of the existing registration |
| Email notification | The person receives an approval or rejection email (with the reason), when configured |
| LGPD consent | The acceptance of the terms is recorded with text, hash, IP, browser, and date/time |
Removes the manual entry of registrations from the operator: the person fills in their own data (with more precision) and sends quality photos straight from the phone. The operator only reviews and approves.
The public form
URL: https://{seu-host}/external/precadastro/form/{token}
The {token} is generated by the plugin and identifies the installation. The link is distributed as the client prefers (QR Code, WhatsApp, email, printed at the gatehouse) — see Public link.
The form is a step wizard, with a Back button on all screens (except the initial and success ones) and no free navigation between steps.
Overview of the public form on the phone, showing the mobile-first layout with ACCELERO's orange visual identity.
Wizard steps
1. Welcome
Displays the configured title and welcome message and a button to start the pre-registration.
Welcome screen with configurable title and message and the start button.
2. Terms and Conditions
Presents the terms text (configurable) in a reading area and a "I have read and accept the terms" checkbox, required to proceed. Upon accepting, the system records the exact text, the text hash, and the date/time of acceptance (see Consent and LGPD).
Terms acceptance screen with the text and the consent checkbox.
3. Category
The person chooses their category among the categories released in the configuration. Each category carries its own set of fields and photo requirements.
Category selection screen, with the available categories in clickable cards.
4. Personal data
The fields are rendered dynamically according to the configuration of the chosen category, with automatic masks for CPF and phone and validation of the required fields. If the provided CPF already exists in the system, the form warns that the data will be updated.
Personal data entry screen with dynamic fields and CPF/phone masks.
5. Vehicle data (optional)
Displayed only when the category enables the vehicle. The person provides the Plate, Model, and Color, or can skip this step.
Vehicle data screen with the Plate, Model, and Color fields and the skip button.
6. Photo capture
Step automatically skipped when the category does not require any photo. Depending on the category configuration, the following may be requested:
- Facial photo — front camera with a guide (silhouette) and automatic face detection; the capture button is only released when the face is detected correctly.
- Document (front and/or back) — rear camera with a rectangular guide, manual capture.
- Fallback without a camera — when the camera is not available or permission is denied, the person uploads an image file (JPG/PNG, up to 5 MB).
Facial capture screen with the guide silhouette and the detected-face indicator.
Document capture screen (front) with the rectangular guide.
7. Summary
Shows all filled-in data and the photo thumbnails for review, with the option to go back and edit. The Submit Pre-Registration button finalizes the submission.
Summary screen with the provided data, photo thumbnails, and the submit button.
8. Success
Displays the configured success message and a reference protocol for the submission. The submission enters the moderation queue with Pending status.
Success screen with the confirmation message and the submission protocol.
Administrative panel
The Pre-Registration administration panel is opened by a floating button (orange, with a clipboard icon) displayed at the bottom of the ACCELERO screens. The button only appears for operators with moderation or configuration permission for the plugin.
Unlike other integrations, Pre-Registration does not add a menu item: the panel opens in a window overlaid from the floating button. Those who do not have any of the plugin's permissions do not see the button.
Pre-Registration floating button at the bottom of an ACCELERO screen and the panel open in overlay.
The panel has three tabs, depending on the operator's permission:
| Tab | Required permission | Function |
|---|---|---|
| Moderation | precadastroManager (Pre-Registration - Moderation) | Review, approve, and reject submissions |
| Configuration | precadastroConfig (Pre-Registration - Configuration) | Define texts, categories, rate limit, and emails |
| Public Link | precadastroConfig (Pre-Registration - Configuration) | Generate/regenerate the link token and QR Code |
Moderation
The Moderation tab lists the received submissions, with status tabs, filters, and actions.
Moderation tab with the status tabs (Pending/Approved/Rejected), the filters, and the submissions table.
Status tabs
| Tab | Content |
|---|---|
| Pending | Submissions awaiting a decision (with a count badge) |
| Approved | Already approved submissions |
| Rejected | Rejected submissions |
Filters
| Filter | Options |
|---|---|
| Search | Search by name, document, or email |
| Category | Filters by one of the system's categories |
| Type | New (unprecedented CPF) or Updates (existing CPF) |
Columns
| Column | Content |
|---|---|
| Photo | Thumbnail of the facial photo (slot 1), when available |
| Name | Provided name; receives the Vehicle label when the submission includes vehicle data |
| Type | New or Update |
| Document | Provided document (CPF) |
| Category | Category chosen by the person |
| Date | Date and time of submission |
| Status | Pending / Approved / Rejected |
Submission detail
When you click a row, the detail opens with the personal data, the submitted photos, and the Approve and Reject buttons. When the CPF already exists, the detail highlights the existing person that will be updated.
Detail of a submission with data, photos, and the Approve / Reject buttons, including the existing-person notice.
Bulk actions
On the Pending tab, you can select several submissions with the checkboxes and use the actions bar:
- Approve selected — approves all marked submissions.
- Reject selected — opens a field to provide the rejection reason, applied to all marked submissions.
- Clear selection — deselects everything.
Bulk actions bar with selected submissions and the bulk rejection reason field.
What happens upon approval or rejection
Approval
Upon approving a submission, ACCELERO:
- Creates or updates the Person — if the CPF is unprecedented, it creates a new registration; if it already exists, it updates only the filled-in fields (does not overwrite existing data with empty values).
- Fills in the native fields (name, email, document, phone, company, notes) and applies the configured enablement default value.
- Records the custom fields in the person's metadata.
- Links the chosen category (Person × Category Link), with an open validity. If the person already has the category, the link is not duplicated.
- Transfers the photos to the person's standard slots: facial photo → slot 1, document front → slot 2, document back → slot 3.
- Records the audit (who approved, when, and which person was created/updated) and removes the base64 photos from the submission to free up space.
- Sends the approval email, when enabled.
The approval saves the person through ACCELERO's normal flow, triggering the core registration events. Plugins that react to these events (controller synchronization, facial templates, etc.) act normally on the created/updated person.
Rejection
Upon rejecting, the operator provides a reason. The submission gets the Rejected status, the base64 photos are removed (privacy), and the personal data is kept only for auditing. When enabled, the person receives the rejection email with the provided reason.
Configuration
The Configuration tab gathers the plugin's texts, categories, limits, and emails.
General configuration tab with the fields for texts, rate limit, and email notifications.
General configuration
| Field | Description |
|---|---|
| Pre-registration enabled | Turns the public form on or off. When disabled, the link does not work |
| Welcome title | Title displayed on the first screen of the form |
| Welcome message | Introductory text on the first screen |
| Terms of use text | Consent text displayed in the terms step |
| Success message | Text displayed after a successful submission |
Rate limit
Protects the public endpoints against abuse, limiting submissions per IP:
| Field | Description |
|---|---|
| Attempts per window | Maximum number of submissions per IP within the window |
| Window (minutes) | Limit counting period |
When the limit is exceeded, new attempts from the same IP are temporarily blocked. The default value is 5 attempts per 60 minutes.
Email notifications
| Field | Description |
|---|---|
| Send approval email | Turns on the email sent when the submission is approved |
| Subject / Body of the approval email | Text of the approval email. Accepts the placeholder {nome} |
| Send rejection email | Turns on the email sent when the submission is rejected |
| Subject / Body of the rejection email | Text of the rejection email. Accepts the placeholders {nome} and {motivo} |
Use {nome} to insert the person's name and {motivo} (only in the rejection) to include the reason provided by the operator.
Categories and fields
The configuration defines which categories are available in the form and, for each one, which fields are displayed and which photos are required.
Each field has a label, input type (text, email, phone, CPF, number, date, selection, text area), whether it is required, and order. Fields can be:
- Native — map directly to fields of the Person entity (e.g., name, document, email, phone, company, notes).
- Custom — extra fields recorded in the person's metadata after approval.
Each category also defines which photos to request: facial, document front, and document back (any combination; if none, the photo step is skipped).
Field editor per category, showing the list of fields (native and custom) and the switches for required photos.
When the operator changes the fields, the already pending submissions keep the data as it was submitted — there is no retroactive revalidation. The moderator evaluates each submission by what was received.
Public link
The Public Link tab generates and manages the form's address.
Public link tab with the form URL, the copy button, the QR Code, and the regenerate token button.
| Element | Description |
|---|---|
| Public form URL | Complete address of the form, with a Copy button |
| QR Code | Image of the link's QR Code, with a Download QR Code option |
| Regenerate Token | Generates a new token; the previous link stops working immediately |
When you regenerate the token, any link or QR Code previously distributed stops working immediately. The already submitted registrations are not affected. Redistribute the new link after regenerating.
If pre-registration is disabled on the Configuration tab, the link does not work, even with a valid token.
Consent and LGPD
The form collects personal data (name, CPF, email, phone, and photos), so the acceptance of the terms is mandatory before collection and is recorded.
For each consent, the plugin stores:
| Recorded data | Purpose |
|---|---|
| Exact terms text | Proof of what was accepted |
| Text hash | Integrity — detects a change in the text |
| Holder's IP | Origin identification |
| Browser (User-Agent) | Technical context |
| Date/time of acceptance | Time record |
After moderation (approval or rejection), the submission's base64 photos are removed. In case of approval, they remain only as the person's photos in ACCELERO; in case of rejection, they are discarded.
The terms text is configurable and should reflect the privacy policy of the condominium/company — which data is collected, the purpose, who will have access, and whether the facial photo will be used for facial recognition on the access devices.
Use cases
Enable pre-registration in a condominium
- Request the installation of the
precadastroplugin from IONGRADE. - On the Configuration tab, define the title, welcome message, terms text, and success message.
- Release the categories that the person will be able to choose (e.g., Resident, Contractor) and configure the fields and photos of each one.
- Check Pre-registration enabled.
- On the Public Link tab, generate the token and download the QR Code to share.
- Follow the Moderation tab as submissions arrive.
Approve a resident
- On the Moderation > Pending tab, open the submission.
- Check the data and photos. If there is an existing person notice, confirm that it is the correct update.
- Click Approve — the person is created/updated and linked to the category, with the photos transferred.
- If configured, the person receives the approval email.
Reject with a reason
- On the submission (or in a bulk selection), click Reject.
- Provide the rejection reason.
- Confirm — the submission is rejected, the photos are discarded and, if configured, the person receives the email with the reason.
Best practices
- Specific categories: release in the form only the categories that make sense for the external audience (e.g., Resident, Contractor). Avoid internal categories.
- Lean fields: ask only for what is necessary in the public form. The fewer fields, the higher the completion rate.
- Appropriate terms: adjust the terms text to the client's privacy policy and the actual use of the photos.
- Visible QR Code: share the QR Code at the gatehouse and on the official channels; regenerate the token if the link leaks.
- Frequent moderation: review the pending queue regularly — submissions do not expire and remain awaiting manual action.
- Be careful when regenerating the token: arrange the redistribution of the new link before invalidating the old one.
Troubleshooting
The public link does not open
Possible causes:
- Pre-registration disabled on the Configuration tab.
- Regenerated token — the distributed link became invalid.
- Incorrect token in the URL.
Solution:
- Confirm Pre-registration enabled on the Configuration tab.
- Get the current URL on the Public Link tab and redistribute it.
The photo step does not appear
Possible cause: the chosen category does not require any photo (facial, document front, and back all turned off).
Solution: in the category configuration, enable the desired photo types.
The person receives "too many attempts"
Possible cause: the rate limit per IP was reached.
Solution: wait for the configured window or adjust Attempts per window / Window (minutes) on the Configuration tab. Remember that multiple accesses through the same network share the IP.
The Pre-Registration floating button does not appear
Possible cause: the operator does not have any of the plugin's permissions.
Solution: grant Pre-Registration - Moderation and/or Pre-Registration - Configuration to the operator's profile.
The person does not receive the approval/rejection email
Possible causes:
- Email notification disabled in the configuration.
- Email not provided in the submission.
- ACCELERO's email server not configured.
Solution:
- On the Configuration tab, confirm that Send approval/rejection email is checked.
- Check whether the submission had an email filled in.
- Confirm ACCELERO's email sending configuration with support.
Integration with other modules
People and Categories
The approval creates or updates a Person and links it to a Category. The form's native fields map directly to the person registration; the custom ones go to the metadata.
Self-registration plugins
Pre-Registration is one of the external registration flows. For visitors without moderation or people with simple approval, see Visitor self-registration and Person self-registration.
Next Steps
- People — Understand the fields and photos that the approval fills in
- Categories — Configure the categories released in the form
- Visitor self-registration — External registration of visitors
- Person self-registration — External registration of people with approval
- Plugins — Learn more about ACCELERO's plugin system