Knowledge Base

Listing permit compliance in your CRM: what UAE brokerages should automate

Dubai and Abu Dhabi both require a permit before a property advert goes live, and the portals enforce it. Tracking that in a spreadsheet stops working somewhere around fifty listings.

Listing permit compliance is a data problem before it is a legal one. A brokerage knows it needs a permit for every advert. What it usually cannot answer on demand is which of its live listings have one, which are about to expire, and which adverts no longer match the permit they were issued against.

Those three questions are answerable in a CRM and almost unanswerable in a portal dashboard, because the dashboard shows one listing at a time.

Two emirates, two systems

The requirement is similar in shape and different in detail.

Dubai Abu Dhabi
System Trakheesi, operated by the Dubai Land Department under RERA supervision Madhmoun, operated by the Abu Dhabi Real Estate Centre with the Department of Municipalities and Transport
Permit scope Tied to a specific property and advert; the number must appear on the advert Tied to a verified property; issued through ADREC’s platforms
Notable rule Seller appoints brokers through Form A, exclusively or non-exclusively within the limit RERA allows A maximum of three approved brokers may advertise the same property
Portal enforcement Major portals require a valid permit number before the listing goes live Same, with the platform designed to remove unverified or expired listings

Abu Dhabi has moved further towards a central, verified listing model: Madhmoun has been described as the first government-backed multiple listing service in the region, admitting only verified properties. ADGM introduced its own advertising permit service, in collaboration with Madhmoun, covering property within its jurisdiction.

Rules and fees change and differ by emirate. Confirm the current position with the relevant authority before relying on any specific detail — that caveat is not boilerplate here, it is the operating reality.

Why spreadsheets fail at this

A permit tracker in a spreadsheet works while one person maintains it and the listing count is small. It fails predictably:

  • Nobody updates it when a listing is withdrawn, so expiry alerts fire on properties you no longer market
  • It has no connection to the advert, so a price change in the portal creates a mismatch nobody notices
  • It cannot block anything — it is a record of intentions, not a control
  • When the person who maintains it is on leave, it stops

The shift worth making is from tracking to gating. A permit field that records information is useful. A permit field that prevents a non-compliant listing from being published is a control.

How listing permit compliance works in Salesforce

Fields on the Listing record

  • Permit number and issuing authority — the second matters once you operate in more than one emirate
  • Issue date and expiry date
  • Permit status — valid, expiring, expired, missing
  • Advertised price held separately from the price on the permit, so a mismatch is detectable
  • Supporting documents — the paperwork the permit was issued against

The separate price field is the one that prevents the most common avoidable rejection. An agent reduces the asking price, the advert no longer matches the permit, and the listing is pulled. If the CRM holds both numbers, the mismatch is visible the moment it happens.

Three automations that carry the weight

  1. Publication gate. A listing with a missing or expired permit does not enter the outbound feed. This is the single highest-value rule, and it belongs in your system rather than relying on the portal to catch it. See Salesforce listing feeds to UAE property portals.
  2. Expiry alerts. Tasks raised before expiry, assigned to whoever renews permits, not to the listing agent by default.
  3. Mismatch detection. A scheduled check comparing advertised price and key attributes against the permit record.

The audit trail

Keep history on the permit fields. If a question is ever raised about an advert, the useful answer is not “the permit is valid now” but “here is what the permit said, here is what the advert said, on that date”. Field history is inexpensive to enable and impossible to reconstruct after the fact.

The rejections worth designing out

Most permit-related problems come down to a short list, and most are caught only after the advert has been built — which wastes the work twice over.

Problem Where to catch it
No permit number on the advert Required field before publication status can be set to live
Expired permit Scheduled status update plus the publication gate
Advert does not match the permit Mismatch check on price and key attributes
Missing supporting documents Document checklist on the Listing before permit application
Broker limit exceeded on a property Visible on the property record where you operate in Abu Dhabi

Who should own this

Permit renewal usually lands with an administrator, while the consequences land on the agent whose listing disappears. That split is why permits lapse.

A workable arrangement: the administrator owns the renewal task, the listing agent sees permit status on their own listings, and a weekly report of expiring permits goes to the team lead. Three people see it, one person does it, and nobody can claim they did not know.

Worth noting that compliant listings also carry a marketing benefit. Portal quality programmes take permit status into account when assessing listings, so compliance and visibility point in the same direction rather than competing for attention. The Bayut side of this is in integrating Bayut with Salesforce.

Frequently asked questions

Do all UAE property adverts need a permit?

Dubai requires a permit issued through the Land Department’s Trakheesi system, and Abu Dhabi requires one through ADREC’s Madhmoun framework. Major portals check for a valid permit number before a listing goes live. Requirements differ by emirate and change, so confirm the current position with the relevant authority.

Can Salesforce track permit expiry automatically?

Yes. Permit number, issue date and expiry sit on the Listing record, with scheduled updates to a permit status field and tasks raised before expiry rather than after it.

Can a CRM stop a non-compliant listing being published?

Yes, by gating the outbound feed on permit status. A listing with a missing or expired permit never enters the feed, which puts the control in a system you own.

What causes most permit-related listing rejections?

Missing permit numbers, expired permits, mismatches between the advert and the permit such as a changed price, and missing supporting documents. All four are detectable before publication.

How many brokers can advertise the same property?

In Abu Dhabi, a maximum of three approved brokers may advertise the same property. In Dubai, appointments are made through Form A, exclusively or non-exclusively within the limit RERA allows. Confirm the current position before relying on either.

Does a CRM replace the official verification systems?

No. The CRM records your permit data, enforces your own process and surfaces problems early. Permits are issued and verified by the authorities, not by your system.


This article is general information about operational practice, not legal advice. Confirm current requirements with the Dubai Land Department or the Abu Dhabi Real Estate Centre.

About the author. Written by the VinteraTech consulting team. VinteraTech is a Salesforce Select Partner based in Istanbul, building custom Salesforce solutions including portal integrations, payment-plan platforms and ERP connections.

Last updated: 28 September 2026

Talk it through

If permit tracking lives in a spreadsheet, tell us how many listings you run and across which emirates. Get in touch — the first assessment is free.

Let us look at your compliance process

Tell us how permits are tracked today and how many listings you run. We will come back with scope, timeline and an indicative cost — free, and with no obligation.