Review licenses, certificates, and NRAs

The Licenses dashboard brings together the data Holidario stores for active short-term rental operations. It is an internal tracking tool: it does not independently query each autonomous community's records or file requests with an authority.

Open and narrow the list#

1. Confirm that you are working in the correct team.
2. Open Licenses from the menu.
3. Choose Certificates, Licenses, or NRAs.
4. Enable only the required filters and check whether more pages exist.
5. Open an operation name to review the source field.

The list excludes disabled operations. A property owner sees only resources they are authorized to access; different totals between users can therefore reflect access scope.

What each tab means#

Certificates#

Shows the certificate code stored on the operation. The counter is the number of operations where the field is empty.

Holidario treats this as one state: populated or unpopulated. If the applicable procedure requires several documents, the product convention is to leave it unpopulated until the organization confirms it holds the complete set.

Licenses#

Shows the tourist license and its internally recorded holder as Agency or Owner. The holder is an operational classification in Holidario; it does not change ownership in an external register.

The product also displays Owner when the internal holder marker is unset. Before using it as an operational fact, confirm the holder on the operation and against your organization's authorized source.

NRAs#

Shows the Rental Registration Number stored on the operation. Populated means only that the field has a value. When the team uses Sede Registradores, also review its validation state and last-check date.

Read the states#

• Populated: a local value exists on the operation.
• Pending: the field is empty and no request marker exists.
• Requested: someone recorded an internal request date and, optionally, a note.
• Also missing...: another identifier is empty on the same operation.

Requested does not send anything, create a case, or confirm that an owner or authority received a request. Its date and note are internal reminders.

The current form accepts a future request date. Enter the date on which the request actually happened; a saved date does not prove that it is correct.

Use the filters#

Under Certificates, you can show:

• unpopulated records;
• certificates not marked as requested;
• operations that also have no license.

Under Licenses, you can show empty fields or records whose internal holder remains the owner. Under NRAs, you can limit the list to empty values.

Filters combine. If the result becomes empty, remove them one by one before concluding that no work remains.

If you find a discrepancy#

1. Open the operation and confirm the expected property, address, and name.
2. Compare the value with your organization's authorized source.
3. Determine whether it is an empty field, a transcription error, or an external state not reflected locally.
4. Record the operation, document type, source, and check date.
5. Escalate to an administrator with update permission.

Do not correct a code because it resembles one from another property. Do not paste full documents or personal data into a short tracking note.

Actions that require permission#

Marking or removing a request and changing the holder require permission to update the operation. On the current screen those controls can remain visible to a read-only account; using one should be rejected by the server with a 403 error. Do not retry or request a broader role: use the dashboard to identify the gap and ask an authorized administrator to make the change.

Expected result#

Every visible operation has an understandable internal state, empty values have a responsible owner, and no local state is presented as proof of external validity.