Operations in Mapaprop — Complete Guide

PART 1 — User Manual

1. What are Operations?

An operation is the record of a commercial transaction on a property: a reservation, a sale, a rental, a swap, or a fall-through. It is the "what happened, when, with whom and at what price" of every movement of the property.

Concrete example

Your agent María takes a reservation on an apartment for USD 130,000 with a USD 5,000 deposit. A week later, the buyer signs the agreement and the sale closes at USD 128,000 (they negotiated USD 2,000 less). Mapaprop keeps a single operation that went through two states: first Reserved, then Sold. That operation is recorded with: listing price (USD 139,000), buyer's offer (USD 130,000), deposit (USD 5,000), closing price (USD 128,000), buyer, owner, responsible agent, branch, dates. All of that feeds your management reports and your commercial history.

2. What is it for?

The Basic mode only changes the property state: reserved, sold, rented. Operations expand that gesture: the same action now leaves the complete record of the transaction —with whom, at what price, with what commission and on what date—. With that you can:

3. How an operation is composed

Each operation has 4 pieces of information:

3.1 State

Indicates at which point of the cycle the operation is. It can only be one of these:

⚠️ A closed operation (Sold / Rented / etc.) CANNOT be reverted. If the operation later falls through, you must create a new operation with the Fallen through state. The closed one remains as history.

3.2 Type

Indicates which type of transaction it is. It is automatically derived from the operation type of the property that is loaded (Sale, Rental, Temporary, Swap).

3.3 Economic data

3.4 Participants

• Seller / Owner: who owned the property (from your contacts list).
• Buyer / Tenant: who made the operation (from your contacts list).
• Responsible agent: the Mapaprop user who opened the operation.
• Branch: the branch the operation belongs to (inherited from the property).

4. Two modes to record an operation: Basic and Business

When you close an operation from a property's record, the "Operation Closing" window opens. There you can choose between 2 ways to record it:

4.1 Basic Mode

• What does it do? It only changes the property's state (Reserved / Sold / Rented / Suspended) and optionally records a closing price.
• What does it NOT do? It does not save contacts, commission, or detailed history. It does not generate an operation trackable in the reports.
• Who uses it? Small agencies that only need to mark their properties' state without worrying about management reports.
• Required plan: any (Free, Plus, Pro+, Business).

4.2 Business Mode (recommended)

• What does it do? It creates a complete operation with all the data: contacts, offer, deposit, closing, commission, comments. It then appears in all the reports.
• Required plan: Business or Business Manager (plans 56 and 57).

4.3 Comparison table

💡 Recommendation: if you have the Business plan, always use Business mode. It is the only way to take advantage of the management reports.

4.4 Decision by plan

5. How to record an operation step by step

5.1 Create a reservation

1. Go to the property's record → "Operation Closing" button.
2. The window opens. Choose "Reserved" among the state options.
3. If you have Business, you go to the step-by-step wizard:

• State: you already chose Reserved.
• Operation type (appears only when reserving on your own properties): you choose how the operation is composed — Single side (you represent one party), Double side (you bring both seller AND buyer) or Co-brokering (the buyer was brought by another broker from your office or your network in Mapaprop). In Double side and Co-brokering the system creates 2 linked operations (see §7.12). There is also an "External operation" option that takes you to Operations to record an operation on a property that is not in Mapaprop (see §7.10).
• Amounts: enter the buyer's offer. If there was a deposit, check the checkbox and enter the amount.
• Participants: link seller and buyer from your contacts. You can choose one already linked to the property, search for it or create it on the spot. Any contact you link here also gets linked to the property — you will see it later on the record, in the Contacts tab (the seller as Owner, the buyer as Interested).
• Comments: optional, to leave internal context.

4. Click Save Operation.

The property is marked as Reserved and a red "Operation in progress" chip appears on its record.

5.2 Close the operation (Sold / Rented / etc.)

There are 2 ways to reach the closing:

Option A — From the property's record:

1. Click on "Manage Operation" (red button). It takes you to the detail of the reserved operation.
2. There you choose the target state: Close as Sold / Close as Rented / etc.
3. The window asks you for the Closing price and the Commission — both fields are mandatory when closing (the other sections stay collapsed because you already had the data loaded).
4. Click Update Operation.

Option B — Straight from the property's record:

1. Click on "Operation Closing".
2. Choose the terminal state directly (e.g., Sold).
3. The window opens with the reservation data pre-loaded. You complete closing and commission.
4. Save.

After closing:

• The operation is left with a terminal state and a closing date.
• The property is marked as Sold (or Rented if it was rent / temp / exchange).
• It is recorded in the property's price history.
• It appears in the "My Operations" report of the agent who closed it.

5.3 Cancel a reservation (Fall-through)

When a reservation does not materialize:

1. From the property's record → "Manage Operation" → Fallen through state.
2. Or from the operation detail → red "Cancel reservation" button.
3. Save.

The operation becomes Fallen through (it cannot be reverted), the property automatically returns to Available, and it is recorded as a fall-through in the reports (contributes to the agent's "fall-through rate").

5.4 Edit while the operation is in progress

While the operation is Reserved you can correct its data without changing the state. There are two paths:

• From the operation detail (/deals/[id]) → "Edit" button: opens a window to adjust offer and currency, deposit, contacts (seller / buyer) and comments. The commission is not touched here — it is loaded only when closing. This button is for account administrators.
• From the property's record → "Manage Operation": the window opens with collapsible sections (State / Amounts / Participants / Comments) to edit what you need.

5.5 Return a property to "Available"

If a property is reserved and the client changed their mind without formalizing a fall-through, you CANNOT send it straight to Available while it has an operation in progress. Mapaprop blocks you with a message:

"There is a reserved operation in progress. To change the property's state you must resolve it from Manage Operation or mark it as Fallen through."

Two paths:

• Click on "Mark as fallen through" from the blocking message → cancels the reservation and frees the property with a single click.
• Click on "Manage Operation" → resolve manually (materialized closing or fall-through).

This prevents orphan operations from remaining (reserved in the system but the property already put up for sale again).

5.6 Change the state of a property already sold/rented

If the property is sold (closed operation) and you want to put it up for sale again, you can:

1. Mark it as Available from the record (this does NOT affect the closed operation — it stays there as history).
2. Create a new operation when another reservation arrives. Your history will show: old deal (sold) + new deal (reserved/closed/fallen through).

6. The operations screens and their three scopes

In the side menu, Operations opens the whole module:

The three scopes

The screens in this module —the listing, the statistics, the gap and the captures— answer the same question over three different universes. You pick the scope with the selectors at the top right:

6.1 Operations (/deals)

This is the working screen for every role. An administrator sees the operations of the whole account; an agent enters the same screen and sees their own. Agents arrive through My Operations and land on this very screen, already scoped to their own deals.

• Date filters, on a single line: four shortcuts (last 14 days, 30 days, 90 days, this year) plus From / To. They apply immediately, with no "Filter" button.
• "More filters" button: opens the rest in a dialog — operation type, state, side (seller/buyer — see §7.9), origin (own/external/deleted — see §7.11), and for administrators also branch and agent. The number next to the button tells you how many are set, so you know the list is narrowed even with the dialog closed.
• The Agent filter appears once you choose a branch, and lists only the agents of that branch.
• Mini-cards on top with 12 live KPIs (see §6.5) that respect the applied filters.
• Table with columns: Id (operation number, e.g., #1234, with a direct link to the detail), Property, Agent / Branch (the responsible agent and their branch), Contact, Type, Side (green badge Seller / purple Buyer / gray Both), Origin (gray badge 🏠 Own / purple 🔗 External / red 🗑️ Deleted), State, Offer, Closing, Commission, Date. A row may also show an alert icon when the operation is part of a linked pair with an anomaly (see §7.12).
• Sort by column: Id, Offer, Closing, Commission and Date sort by clicking the header (a second click reverses it, a third returns to the original order). Amounts are grouped by currency and sorted by amount within each one: nothing is converted, because a commission of ARS 89,000 and one of USD 600,000 cannot be compared by the bare number.
• Three gap cards below the KPIs, and they are clickable: they take you to the full report (§6.4) with the same scope and the same period.
• Active filter chips with an X to remove individually.
• "+ Add operation" button: creates a manual operation without an associated property (see §7.10). Every role sees it.
• "View deleted" button (with counter): only the account administrator.
• Export to CSV for external analysis (respects the filters).
• Pagination of 20 rows when there are more than 20.
• Mobile: cards instead of a table (not paginated: all are listed).
• Who sees it: every role. What changes is the scope, not the screen — see the notice below.

6.2 Deal Statistics (/stats/deals)

The module's analytical report: the same information as the listing, but aggregated and charted so you read trends instead of individual operations.

• Daily evolution: how many deals were opened, closed and fell through each day.
• Closings per month: how many closed in each month. Grouped by the month of the closing, while the period above filters by the opening date — that is why a month later than the selected range can appear.
• Mix by operation type and breakdown by type, with volume and commission per currency. Nothing is converted into a single currency: adding pesos to dollars would produce a meaningless number.
• Agent ranking: ordered by closings, with volume, commission and closing rate. It is not shown to agents, because a one-row ranking with yourself in it tells you nothing.
• Closings in the period: the most recent ones, click to see the deal detail in a modal, without losing your filters.
• The same KPIs you see in "Deals", computed by the same place: there are never two numbers for the same thing.
• It opens on the last 90 days, same as the listing, the gap and the captures.
• The same three scopes as the rest of the module (see above): your account, or the aggregate of a network with drill-down to one office.
• Branch selector for admins. An agent does not see it: the system scopes the report to their own deals server-side.
• Who sees it: requires the Business plan or higher. Agents see it scoped to their own deals.

6.3 Captures (/deals/captations)

Report of properties approved by moderation and pending in the period.

• Approved captures: how many new properties passed the moderation control.
• Pending: how many are waiting for approval.
• Effectiveness: % of captures that ended in a closing (approximate calculation).
• Period closings: for contrast.
• Line chart with two series over the period: requested and approved. The KPIs tell you how much; the line tells you when, and the distance between the two curves is how long moderation takes.
• It opens on the last 90 days.
• The three scopes (see above). In network scope there is also an Office column: without it, the captures of several agencies would read as if they belonged to one.
• Table: detail by property. Clicking a property opens its side panel, without taking you out of the report; from the panel you can go to the full property.
• Who sees it: all roles, each with their own scope. Requires the Business plan or higher.

ℹ️ Note on effectiveness: the calculation is approximate — it divides period closings over period captures without verifying whether the closings actually correspond to the captured properties. It is a guide, not an exact funnel.

6.4 Negotiation Gap (/deals/brecha)

How much the price moved between what you listed, what you were offered and what you finally closed. Four numbers, and the report lets you see where each one comes from, operation by operation.

• Who sees it: all roles, each with their own scope — an agent enters and sees their own gap. Requires the Business plan or higher.
• How to get there: through the Operations → Negotiation Gap menu, or by clicking any of the three gap cards in Operations and in Statistics, which arrive with the scope and the period already set.
• It opens on the last 90 days. The gap is an average: with the closings of a single month the sample is usually two or three operations, and then the number says nothing.
• The three scopes (see above). In network scope, clicking an operation opens its detail in a window instead of navigating: the operation belongs to another account and its direct address would not be yours to open.

The four indicators

On each card, the arrow marks the direction and the text below states it in words.

How they are calculated — three things that explain the numbers you see

The "Complete data only" button solves exactly that: it recalculates the three indicators using only the operations that have listing, offer and closing in the same currency. That way all three come from the same group and are comparable with each other.

The detail, operation by operation

Below the cards there is a table with each operation closed in the period and its three prices. It tells you:

• Which indicator each operation feeds, with the List→Offer, Offer→Close and Total labels — or "Does not feed", with the reason when the currencies do not match.
• The side (selling / buying) and, in network scope, the office that owns the operation.

Click any row and the explanation of that negotiation opens: its three gaps, the price ladder from listing to closing, and how it compares with the period average ("you gave up this much more than the average"). The operation's #number is still a link to its full detail.

If the period brings more than 200 closings, the table shows the first 200 and tells you so. The four indicators above, on the other hand, are always calculated over every operation in the period.

6.5 KPI mini-cards (in all reports)

Above the Operations listing (/deals), in any of its three scopes, there is a grid of 12 mini-cards with live metrics. They all respect the applied filters (period, branch, etc.). Each card has a tooltip on hover with the exact calculation formula.

Below the mini-cards there are three large cards with the negotiation gaps for the period: listing→offer, offer→close and listing→close. They are clickable and take you to the full report (§6.4) with the same scope and the same period.

Row 1 — Volume and counts:

Row 2 — Performance + mix (only appears if there are closed deals):

💡 If the period has no closings, only row 1 is shown.

7. Important rules

7.1 One single reservation per property

Each property can have a single operation in the Reserved state at the same time. If you try to create a second reservation, the system uses the existing one.

7.2 Delete an operation (and why traceability is kept)

The account administrator can delete an operation in any state (reserved or closed). It is a definitive action: it cannot be undone.

How it works, and why you do not lose traceability:

• The operation stops counting in all your reports and listings (KPIs, gap, rankings, etc.) — as if it did not exist for management.
• But nothing is physically deleted: the operation is preserved and it is recorded who deleted it, when and with what reason (the reason is mandatory). That information stays in the operation's Change history, for auditing.
• To see them, in "All operations" there is a "View deleted" button (only for the account administrator) that shows how many there are and lists them with their reason and date. From there you open each one and see the detail marked as deleted.
• If the operation was part of a linked pair (co-brokering or double side), when deleting one side the system offers you to delete the other one too (when it is from your same office). If you leave the pair half-done, the remaining operation shows a mismatch alert.
• If the operation was Reserved, when deleting it the property returns to Available (it is freed and, if it was shared in a network, it reappears in the network searches) — same as with a Fall-through. Deleting an already closed operation (Sold/Rented) does not change the property's state.

When to use it: an operation loaded by mistake, a duplicate or a test. If instead the operation was real but did not materialize, the right thing is to mark it as Fallen through (so it stays in the reports as a fall-through, which is valid management information).

Do not confuse it with a deleted property (§7.4): if you delete the property, its operations are preserved and keep counting in the reports (marked as "(deleted)"). Deleting the operation is another thing: it takes it out of the reports. They are two different actions.

7.3 Terminal states are not reopened

Once an operation moves to Sold / Rented / Fallen through / etc., that state stays fixed. If you need to record a new negotiation on the same property, you create a new operation.

7.4 Deleted properties keep their operations

If you delete a property from the system, the associated operations are not deleted. They remain accessible from the global listing with a snapshot of the property's basic data (address, code, zone) but marked as "(deleted)".

7.5 Negotiation gap: always complete the closing price

For the gap to work well, make sure to always complete the "Closing price" field when closing an operation (it is mandatory in Business mode). The offer price is optional but recommended.

7.6 An operation in progress blocks property state changes

If a property has an active reservation, you cannot change its state to Available or Suspended without first resolving the reservation (closing it as Sold/Rented/etc. or marking it Fallen through). The system warns you with a message and offers to mark it as fallen through with a single click.

7.7 Operation type is derived from the property type

When you create a new operation on a rental property, the operation is born with the "Rental" type automatically. You do not have to choose it. If the property is for sale, it is born as "Sale". This avoids inconsistencies between property type and operation type.

7.8 Every closing is born from a reservation

Rule: you cannot close an operation as Sold / Rented / Swapped / Temporary rental directly on a property that is Available or Suspended. First you must create a Reservation, and close it from there.

Why: the reservation is the moment where the offer, the deposit (if any), the participants (seller + buyer) and the dollar rate at opening are recorded. Without that info the closed operation is left incomplete and traceability for reports is lost (negotiation gap, commissions, captures, etc.).

How it works in the UI:

• In the "Operation Closing" modal on an available or suspended property, the terminal-state cards (Sold / Swapped / etc.) appear disabled in gray.
• You can only click Reserved or Suspended from an available property.
• Once the reservation is created, you go to View Operation (/deals/[id]) and from there you find the "Close as X" button (Sold / Rented / Swapped / Temporary).

Possible exception (under evaluation): temporary rental could allow direct closing in the future because it usually closes quickly without a prior negotiation. For now the rule applies universally. This decision is noted in the product roadmap.

If you need to record a closing on an operation that already happened "outside the system" (e.g., you load a historical sale for reports): create the reservation with minimal data (offer = closing price, deposit 0) and then close it as Sold. The process is 2 clicks.

7.9 Seller side vs buyer side (pd_side)

Each operation has a side field (pd_side) that indicates your agency's role in that transaction:

How it is assigned automatically when creating:

• Modal opened from the record of a property of your account (or of your agent) → the operation is born as seller_side.
• Modal opened as a manual operation without a property (external property) → the operation is born as buyer_side.

The user does not need to choose the side: the system infers it from the context. If in the future you need to record both sides, that flow will become available.

Where you see it in the UI: on the /deals/[id] page there is a chip that shows "Seller side", "Buyer side" or "Both sides" depending on the field's value.

Commission per side (implemented 2026-07-30): when an operation has two brokers (a co-brokering) or when the same office brings both sides (direct double-side pair), the system creates two linked operations — one per side — and each one carries its own commission. The commission is loaded when closing each side (Sold/Rented), never when reserving, and each side is closed separately. In the reports, the pair counts as one operation (the volume is not duplicated), but the two commissions add up. See §7.11.

7.10 Manual operation with an external property

When to use it: when the property you are working on is not loaded in your Mapaprop account. For example:

• You take a buyer to see a property from another agency.
• You work in informal co-brokerage with a colleague and want to keep track of the operation.
• You record a historical sale of a property that was never published on your platform.

How to create a manual operation:

The button opens the same operation modal, but in "manual" mode (without a property from the account linked).

💡 You also get there from a property: if you are recording an operation on one of your properties and in the "Operation type" step you realize that the operation is actually on another property that is not in Mapaprop, choose the "External operation" option. It takes you straight to Operations, where you record it with the "+ Add operation" button. It exists so that option is in sight and you don't have to know in advance where external operations are loaded.

How the modal looks in manual mode:

• Header: purple 🔗 icon + title "External Operation" + purple badge "Buyer side".
• Purple explanatory banner on top: "Operation on a property that is not in Mapaprop. You are the buyer side..."

What the modal asks for — mandatory fields marked with *:

1. Operation type (4 card-type buttons with an icon):

• 🏷️ Sale
• 🔑 Rental
• 📅 Temporary Rental
• 🔄 Swap

The labels and order come from the multi-country system (same selector you see when loading a property). If in the future Mapaprop operates in other countries, the labels are translated automatically.

2. Property address (free text input, max 255 characters). Example: "Av. Cabildo 1234, CABA". It serves to identify the operation in listings and reports — without this the deal is left as "No address recorded".
3. Branch ⚠️ (mandatory since 2026-05-29 for Admin / Main / Manager): which branch of your agency the operation corresponds to. If you don't choose it, the "Next" button stays disabled. For a vendor their branch is assigned automatically and this field does not appear.
4. State (cards): only Reserved and the terminal ones appear (Sold / Rented / etc. depending on the chosen type). The Available and Suspended cards are hidden: they do not apply to external properties.
5. Offer and amounts: same as a normal operation (offer, deposit/reservation, closing, commission). Remember that when closing (Sold/Rented) the commission is mandatory (see §5.2).
6. Participants: contacts selector for Seller/Owner (the counterparty, usually a broker or the direct owner) and Buyer/Tenant (your client). Both optional but recommended for traceability. In external mode the "seller" is loaded as a local contact without being formally linked to a property (there is no property in the system).
7. Comments: free field.

Limitations by role:

Typical use case for the vendor: "I accompanied a buyer to see an apartment from another agency, they got interested, I reserved it informally. I want to keep track so I don't lose the operation." → create a manual Reserved operation from "Operations", with the "+ Add operation" button. When the operation materializes, notify your admin so they close it as Sold or Rented.

Tip: if the counterparty is another agency or a colleague broker, you can load that contact with the "Broker" type (see section 8.5) and link it to the operation's Seller field. This way you have traceability of who you worked the co-brokerage with.

7.11 Operation origin: Own / External / Co-brokering / Double side / Deleted

Each operation has an "Origin" field that classifies it. The Co-brokering and Double side origins mark the buyer side of a linked operation (see §7.12). It allows you to filter and understand at a glance what type of operation you are looking at.

Filter by origin: in /deals the "Origin" dropdown has 4 options: All / Own / External / Deleted. Useful to:

• See only manual operations of the period (External origin) and measure your informal co-brokerage volume.
• Audit orphan operations (Deleted origin) and decide whether to clean them or keep them.
• Filter only internal operations (Own origin) for "clean" reports without manuals or orphans.

Concrete example:

• You took a buyer to a Remax apartment in March. You loaded a manual operation from "Operations" → operation with External origin, Buyer side.
• In April you closed a sale of your property code MP007 with a regular buyer → Own origin, Seller side.
• In May you deleted the property MP007 from the catalog (you decided not to relist it) → the April operation automatically changes to Deleted origin, but keeps the code MP007 as historical data (snapshot).

💡 The origin is assigned by the system automatically. It is not something you load manually.

7.12 Linked operations: co-brokering and double side

Sometimes an operation is not just one: they are two linked operations, one for each side (the seller one and the buyer one). It happens in two cases:

• Co-brokering — the buyer was brought by another broker (from your office or your network in Mapaprop). Each office manages and closes its side, with its commission.
• Direct double-side pair — you (the same office/agent) bring both sides: you represent the seller AND the buyer. Still two linked operations are created, one per side, each with its commission.

In both cases:

• 2 operations are created in /deals, with a "Co-brokering" (green) or "Double side" (blue) badge, joined to each other ("Linked operation" card in the detail).
• The commission of each side is loaded when closing that side (Sold/Rented), never when reserving.
• Each side is closed separately (one may close and the other fall through). The system marks with an alert icon (in the /deals listing and in the /deals/[id] detail) two anomalies of the pair:
• Different states: one side closed and the other fell through.
• Different closing prices: the two sides closed (Sold / Rented) but with different closing prices. Since it is the same property there should be a single sale price — the commission does differ per side, the closing price does not. The alert warns you so you review and correct it.
• When closing or cancelling (fall-through) one side, the system offers you to do the same with the other ("Also close the linked operation?" / "Also cancel the linked operation?"). It is a convenience shortcut, not automatic: you confirm, and each side keeps its own closing with its own commission. It only appears when the other side is from your same office and remains open.
• In the reports, the pair counts as one operation (the volume is not duplicated), but the two commissions add up.

How it is created: when recording a reservation on your property (with Business), the wizard has an "Operation type" step where you choose:

• Double side → you bring both sides (seller + buyer). The system automatically creates the 2 linked operations.
• Co-brokering → the buyer was brought by another broker. You choose the counterparty with a cascading: office → branch → agent selector. You can choose a colleague from your own office or from any other office of your network in Mapaprop (networks with directory and co-brokering), with their branch and their agent. The system creates the 2 linked operations.
• Single side → a single operation is recorded (capture or single side, without a link).

The commission of each side is loaded when closing that side, never when reserving.

Co-brokering between two agents, step by step — one agent reserves on another's property; the agent of the other side receives an email and enters their operation directly. Each one sees and manages only their side:

And when the colleague is from ANOTHER office of your network — the flow is the same, but the counterparty is chosen by cascade (office → branch → agent) and each office sees the property and the operation from its side (the buyer one sees it as a network record):

And the other side: when you are the one who brings the buyer for a property from another office of your network. You enter from the Network Properties catalog, reserve as buyer side (the counterparty —the owner office— is resolved on its own) and that office receives the email to manage its seller side:

7.13 Close an operation jointly with another agency (co-brokering): only within your network (MLS)

Closing an operation jointly with another agency is only possible when both agencies belong to the same real estate network (MLS) in Mapaprop. It is not a setting that gets activated: it is a requirement. If the two agencies do not share a network, the option to choose that other office is not available in co-brokering.

• With a colleague from your own office (your same account) co-brokering is always available.
• With another agency (another office) co-brokering appears only if the two are members of the same network. The counterparty selector (office → branch → agent) only lists the offices of your network.

⚠️ Without a shared network there is no co-brokering between different agencies. The network is the requirement that enables it; it is not something resolved from the operation's configuration.

The network property gets linked to your buyer contact

When you co-broker a property from another office of your network (you bring the buyer side, the property lives in the other office), that network property gets associated with your buyer contact:

• You will see it on the buyer contact's record, identified as a network property, along with the rest of the properties that contact has linked.
• From the record of that network property you can return to your operation: the link works both ways (contact → network property → your operation).

All of this lives within the context of the shared network: without the network, neither co-brokering between different agencies nor these links exist. More detail on how network properties behave in Network Property / MLS.

8. Special cases

8.1 Agent without an assigned branch

If a vendor of the system has no assigned branch, they can access Operations but will see the whole account (the branch filter is not applied). Recommendation: always assign a branch when adding the agent.

8.2 You downgraded from Business plan to Free/Plus

• Your existing operations are not deleted, they stay in the system.
• You lose access to the operations reports and to Business mode.
• You cannot create new operations (you go back to Basic mode, which only changes property state).
• If you go back to Business, you recover full access and all your historical operations.

8.3 An agent from one branch looks at a property from another

This is common in networks with multiple branches. The agent:

• Can see the operations history of any property of the account (cross-branch read).
• Cannot see the detail of operations that are not from their branch (instead they see "🔒 Name of the other branch").
• Cannot create or close operations on properties of other branches.

8.4 Migration of old data without the correct type

If you have operations loaded before April 2026, the "type" field may be as "Sale" even though the property is for rental (it was a bug). There is an SQL script that recalculates the types of old operations based on the property type. If you need it applied to your account, contact support.

8.5 Broker contacts (real estate colleagues)

When you create a new contact from the CRM or from the operation modal, there is a "Contact type" selector with two options:

Use cases of the Broker type:

• A friendly agency that brings you buyers for your properties (co-brokerage).
• A colleague from another Mapaprop account with whom you share operations from time to time.
• The seller counterparty in a manual operation: the property is theirs, you bring the buyer.

How it appears in the CRM: the "Broker" tag appears automatically in the CRM label filter along with the usual tags (Tenant, Owner, Interested, etc.). You can filter all your brokers quickly to see with whom you have active relationships.

The Broker tag does not replace the others. If a broker is also a buyer in some operation, they can have both labels (the Broker one assigned when creating the contact, and the Interested one assigned when linking them to a property).

9. Frequently asked questions

Why can't I see the "Business Closing" button? Your plan does not include Operations. You need Business (service 56) or BusinessManager (service 57).

I am an agent: do "All operations" and "My Operations" show me the same thing? Yes. Both take you to the same screen, and in both you see only your own operations: the scope is applied by the server, not by the link. "My Operations" exists so the name tells you what you are going to find.

So, can an agent see their colleagues' operations? No. The scope is applied by the server: each agent receives only the operations of their branch that they recorded, and the same holds for the mini-card totals. Sharing the screen does not mean sharing the data.

Why does a gap indicator give me 0% or no data? Each indicator is calculated only with the operations that have the prices that indicator needs, in the same currency: "Listing to offer" needs listing + offer; "Offer to closing" needs offer + closing; "Final discount" needs listing + closing. If no operation in the period has that data (or they are in different currencies), that indicator is left without a base. Always load the 3 prices in the same currency so the operations contribute to all three. The "Complete data only" button shows you only those complete operations.

Can I delete an operation loaded by mistake? Yes: the account administrator can delete it (it stops counting in the reports and it is recorded who, when and why — it is definitive, see §7.2). If the operation was real but did not materialize, better mark it Fallen through so it stays in the reports as a fall-through.

I mark a property as Sold without Business mode. Do I lose anything? Yes. The change stays on the property (state and closing price) but does not generate a trackable operation: it does not appear in the reports, it does not contribute to the gap, there is no record of buyer/seller. For real management, use Business mode.

Why does the type of my new operations say "Rental" when I create from a rental property? It is the expected behavior: the operation type is derived from the property type.

Can I see operations of properties I already deleted? Yes. In the global listing they appear with a snapshot of the property data and the note "(deleted)".

When does the automatic "Mark as fallen through" button appear? When you try to change the state of a reserved property to Available or Suspended without closing the operation. The system detects it and offers to resolve it with a click.

What is the "Broker" contact type for? To distinguish your real estate colleagues from your end clients in the CRM. A broker is someone with whom you co-work, not a buyer or owner. By marking them as Broker when creating the contact, the "Broker" label is automatically assigned and they appear in the CRM's label filter.

Can I create an operation if the property is not in my account? Yes. It is the manual operation (see section 7.10). You use it when you work as the buyer side on a property from another agency or that is not published in Mapaprop.

Why does an alert appear on a pair of linked operations? In a co-brokering or double side, the two operations should close at the same price (it is the same property; what differs per side is the commission, not the closing price). If the two sides closed with different closing prices, or were left in different states (one closed and the other fallen through), the system marks the operation with an alert icon in the listing and in the detail so you review it.

In a co-brokering, can I choose an agent from another office of my network? Yes. When building a co-brokering, the counterparty selector cascades down office → branch → agent and lets you choose both a colleague from your own office and from any other office of your network in Mapaprop (networks with directory and co-brokering). Only public data of the other office is shown (name, branch, agent), never its private information.

Can I close an operation jointly with another agency? Yes, but only if the two agencies belong to the same network (MLS) in Mapaprop. It is not a setting: it is a requirement. If they do not share a network, the option to choose that other office in co-brokering is not available. When you co-broker a network property, that property gets linked to your buyer contact (you see it on the contact's record, identified as a network property) and you can return to your operation from the network property's record. See §7.13.

What happens with a network property when I reserve, sell or rent it? When you put in a non-available state (Reserved, Sold, Rented or Suspended) a property you share in an MLS network, that property automatically leaves the network searches: the other members stop finding it when searching. It is not deleted or removed. Whoever already has an open operation on it —for example the other side of a co-brokering— keeps seeing it through its record, with the link they already had. And if the operation falls through and the property becomes Available again, it reappears on its own in the network searches, without you having to share it again. More detail in Network Property / MLS.

PART 2 — Operational Reference (support / account admins)

This part is intended for Mapaprop support, sales, and account admins who need to answer client queries with precision: who can do what, what each plan requires, and how the screens behave depending on the role.

10. System roles

Mapaprop has 4 access profiles, with different scope over the account.

In this doc, "admin" without a prefix means Main Admin or Network Manager (both roles have management permissions over the account). "Mapaprop Admin" is called explicitly when it applies.

11. Permissions matrix by action

Key rules:

• The agent only opens reservations. They do not close or cancel — those decisions are made by the account admin.
• Only the account administrator can delete an operation (definitive and audited — see §7.2). A loading error is deleted; a real operation that did not materialize is marked Fallen through.
• The agent can read the history of any branch but cannot modify deals outside their own.

12. Permissions by screen

"Operations" menu entries

The entries show up on any plan, but clicking without Business triggers the upgrade modal. "Network" additionally requires Business Manager.

/deals (Operations)

/deals/[id] (Detail of an operation)

"Operations" panel on the property record

The agent reads the history of any property of the account, but only modifies deals from their branch.

"Operation Closing" modal

Which entry points open it and who sees them?

What does the modal show depending on plan and role?

Details of the modal's behavior:

• Tags in the header: the modal shows the operation type (Sale/Rental/etc.) and the property type (Apartment/House/etc.) as chips, derived from the property.
• "Reservation offer" + "Reservation amount": when closing an existing reservation, the Amounts section shows these 2 fields (with an amber background) as reference.
• "Buyer Origin": appears inside Amounts when closing an operation. It is optional.
• "Close as X" opens straight into Amounts: when entering from a closing button, the State section stays collapsed (the decision is already made) and it opens directly into Amounts to confirm the closing price.

13. Required plan

13.1 Complete Operations system

Requires Business plan (service 56) or BusinessManager (service 57).

For Free / Plus / Pro+:

• The Operations menu is fully visible, but clicking any of its reports triggers the upgrade modal.
• The "Business Closing" button in the operation modal is blocked with an upgrade modal.
• The backend rejects deals module endpoints.

13.2 Basic Mode of the modal

No plan required — available for everyone. It is the only function of the operations module that is free. It only changes the property's state (Reserved / Sold / Rented / Suspended) and optionally records a closing price. It does not generate a trackable deal, it does not contribute to reports.

13.3 Why the decision

The Operations system exists mainly for professional commercial management: measuring performance, ranking, gap. That justifies the Business plan. Small customers who only need to mark a property as sold have Basic mode.