Upload or remove an estate-agent profile image
Maintain the company image used in supported views/PDFs.
Exact navigationAdmin Area → Property Operations → Real Estate Agents → open company
Before you begin
- Use an account with real_estate_agent: Edit and confirm the intended record or setting before making a change.
- Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
- Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.
What this guide covers
Maintain the company image used in supported views/PDFs. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Exact step-by-step process
- Open Admin Area → Property Operations → Real Estate Agents → open company.
- Download or inspect the supported template/field requirements before preparing the file.
- Choose the Import or Upload action and select the intended file only.
- Run validation and correct rejected rows, file types or required values.
- Complete the import/upload and review the created records, attachments and any error file.
Fields, choices and supported possibilities
Exact actionUpload or remove an estate-agent profile image
Exact navigationAdmin Area → Property Operations → Real Estate Agents → open company
Module version1.0.0
Access rulereal_estate_agent: Edit
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
Organisation/personName, code, email, phone, website, tax/VAT, address, status and profile image where exposed.
Access and structurePlan, role, administrator flag, departments, staff type/company link, approval-manager and public flags where applicable.
Code-backed validations and workflow rules
- Use the supported upload control and remove-company-profile-image action.
- Company, owner, broker and staff records use different capability groups and ownership checks.
- Email-exists checks prevent duplicate staff/company identities in supported forms.
Expected result and verification
- The supported upload or remove an estate-agent profile image flow completes without bypassing permission or validation checks.
- The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
- Unexpected validation, provider or linked-record errors are investigated before retrying.
Security, privacy and operational checks
- Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
- Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
- Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
- Test settings and automated jobs with controlled records before production-wide use.