Configure the property module

The property configuration controls fields, status, media specifications, history and portal connections of the tenant.

Where to find it

Open the relevant property area under Administration.

Requirements and permissions

Fields, status, documents, images and history require settings.manage; Portal accesses require portals.read or portals.write.

Prepare changes

1. Collect professional purpose, controllers and data concerned.
2. Check existing objects and exports for dependencies.
3. Test new fields or statuses first with a test object.
4. For portals, check access, connection test, mandatory fields and destination account.
5. Document the change and inform affected users.

Step by step

Manage object fields

1. Open Management → Property fields and create a field.
2. Enter the Name and Type. The target entity is Property; select fields require comma-separated choices.
3. Decide whether the field is required. Consider existing properties that do not yet have a value.
4. Save and open a property for editing. Check input, required-field messages and the saved value.

The type cannot be changed after creation. Use a new field and plan the transfer of existing values if a different type is needed.

Managing documents

1. Open Management → Documents. This list contains existing documents; it is not a template editor.
2. Search for a document. Search can include indexed content; check notices about coverage or degraded search.
3. Open the preview and verify the document. Download it using the download action if needed.
4. Select the required rows for a ZIP download. Check the entire selection before any bulk deletion.

Add new property documents on the relevant property. Distinguish this management list from the shared file area. Missing content results may indicate that indexing is still running.

Managing images

1. Open Management → Images and search for the image.
2. Open the preview to check its content and association before downloading or deleting it.
3. Download a single image or selected images as a ZIP file.
4. Before confirming a deletion, check the selection and whether the images are used in marketing.

This page manages existing image files. Upload images and arrange them on the relevant property, rather than in a general image-type editor.

Check the change history

1. Open Management → History.
2. Search for a relevant term and sort the table, for example by date.
3. Check the person, action and time. Browse further results if needed.

History explains changes; it does not automatically restore earlier property data.

Manage portal accesses

1. Open Management → Real-estate portals and create or edit an account.
2. Select the portal and enter the required account details. Check the username, password and any API key against the correct portal account.
3. Save first. Open the saved account and run the connection test; testing is disabled while changes are unsaved.
4. Check the result and time of the latest test. Resolve errors before publishing properties.
5. If the provider uses webhooks, configure its side with the displayed callback address and secret. After rotating credentials, update the provider and check incoming callbacks again.

A successful connection test does not replace the property's completeness checks. Store account credentials and webhook secrets only in their designated fields.

Manage object status

1. Open Management → Property statuses and create or edit a status.
2. Enter its Title, Color and Order.
3. Check whether the status permits publication; this contributes to the publication eligibility of properties using it.
4. Save and test status selection, filters and affected portal workflows. Changing a status does not publish a property automatically.

Result

Checked configuration values are available in object forms, filters, history and allowed portal processes.

Variations and special cases

Data type changes, deleted status values and changed external IDs can affect existing data or integrations.

Troubleshooting

Check rights, mandatory fields, existing uses, connection testing and external feedback; test changes first with a demo object.

Related tasks

• Manage objects
• Maintain the brokerage log
• Roles and permissions