How to Manage Team Access on Your Builder Portal on DrawMagic

Two Calls, One Buyer, and a Login Nobody Remembered to Kill

A homebuyer in Whitefield calls the sales number on a Bengaluru project's listing about a 3BHK. Twenty minutes later, a second executive from the same developer calls the same buyer, asking the same qualifying questions, quoting a slightly different price band because the pricing sheet had been updated since the first call. The buyer hangs up more confused than interested, and unsure whether this developer's operations are as put-together as the brochure suggested.

Meanwhile, back at the developer's office, a tele-calling associate who left the outsourced marketing agency three months ago still has an active login to the builder portal. Nobody revoked it because nobody was assigned to revoke it. The associate isn't misusing it — most likely they've simply forgotten it exists — but the exposure exists: an inactive login holding access to consented buyer contact details, projects and dashboards for a developer who no longer has a working relationship with that person.

Neither of these is a technology failure. They're an access-management failure — one that's especially easy to fall into for developer firms scaling from a single flagship project to several bookings running in parallel across cities. As the team around a project grows from "the founder and two sales guys" to "sales executives, a CRM coordinator, a marketing agency and a call-centre partner," the question of who can see what inside the builder portal stops being an afterthought and becomes a genuine operating discipline. This guide walks through how to set that discipline up on DrawMagic — who should get access to what, how to onboard and off-board cleanly, and the specific mistakes that create duplicate outreach, unowned leads and buyer-data exposure.

Why Access Discipline Matters More for Real Estate Sales Teams Than It Looks

It's tempting to treat portal access the way many small teams treat a shared spreadsheet: everyone gets the same login, everyone sees everything, and it's "fine" because everyone is trusted. Two things make that assumption weaker in Indian residential real estate specifically.

First, the data in a builder portal isn't abstract business data — it's a list of named people who have consented to be contacted about a home purchase, along with their phone numbers, budgets, locality preferences and conversation history. That is personal data, and India's evolving data-protection framework under the Digital Personal Data Protection (DPDP) Act puts the onus on the entity holding that data — the developer, in this case — to handle it responsibly. Least-privilege access, where each person can see only the leads and projects they actually need for their job, isn't a compliance checkbox; it's a straightforward way to reduce the number of people who could mishandle or leak consented buyer information, intentionally or not.

Second, developer sales operations in India routinely blend in-house staff with external partners. It's common for a mid-sized developer to run its own sales desk for one project while an outsourced tele-calling agency handles initial qualification for another, and a marketing agency manages digital campaigns and lead capture across all of them. According to IBEF's overview of the Real Estate Industry in India (as of February 2026), real estate is the second-largest employer in the country after agriculture, and the sector's institutional investment and delivery volumes have both been climbing — which in practice means more developers are running more projects with more people touching each one, not fewer. Growth is good; it also means more logins, more handoffs, and more chances for access to drift out of sync with who's actually on the team.

Attrition compounds this. Real-estate sales and tele-calling roles have historically seen high turnover, and a person who exits a role but keeps a live login is a liability that sits quietly until something goes wrong — a call to a buyer who has since withdrawn consent, a competitor hire who still remembers the pipeline, or simply a login that shows up in a security review nobody wanted to explain.

Step by Step: Setting Up and Managing Team Access

DrawMagic's builder tools are built around two connected surfaces: the builder dashboard, which is the shared workspace your team lands in day to day, and builder settings, where you configure who's on the team and what they're allowed to touch. Here's the practical sequence for setting it up correctly.

1. Start from the dashboard, then move to settings. Log in to your builder dashboard as the account owner. This is the view your team will use for daily work — leads, listings, appointments — scoped to whatever access each person has. Team and access configuration itself lives one step over, in builder settings.

2. Invite team members individually. Add each person by their own email address rather than sharing one login across multiple people. Individual logins are what make an access review or an audit trail meaningful — if three people share one login, you can never answer "who did this" with confidence, which defeats the purpose of having roles at all.

3. Assign a role that matches their actual job, not their seniority. A role should describe what someone needs to do, not how important they are in the org chart. A sales executive who only calls leads for one project needs lead access for that project — not settings access, not billing visibility, not other projects' pipelines.

4. Scope access to what's relevant. For multi-project or multi-city firms, scope each person's access to the project or city desk they're actually responsible for. A Pune-desk executive shouldn't be looking at Bengaluru leads by default, and vice versa — not because of distrust, but because a narrower field of view reduces accidental cross-project confusion (the "which price sheet is current" problem from the opening scenario) and keeps lead ownership unambiguous.

5. Set a review cadence, and revoke access the day someone leaves. Access should be revoked from builder settings the same day a person's role ends — whether that's an employee resignation or the end of an agency contract. A calendar reminder for periodic access reviews (quarterly is a reasonable cadence for a growing team) catches anything that slipped through in between.

Roles and What They Should (and Shouldn't) See

There's no universal role list that fits every developer, but most Indian residential sales operations map onto a handful of recurring roles. Use this as a starting template and adjust scope to your own structure.

The general pattern across every row except Owner: access should map to a job, not to trust level. A trusted senior executive who doesn't need to see three other cities' pipelines still shouldn't have them in view — narrowing the field of view is what prevents accidental disclosure and keeps "who owns this lead" unambiguous, not a judgment about the person's integrity.

A Mini Scenario: Scoping an Outsourced Tele-Calling Agency

Consider a mid-sized developer in Pune running two active projects and using an external tele-calling agency to do first-pass qualification on inbound enquiries for one of them. The developer doesn't want the agency seeing the second project's pipeline at all, and doesn't want the arrangement to become a permanent, forgotten-about access grant.

The practical approach: invite the agency's assigned callers individually (not a single shared login), assign them a role scoped only to the one project's incoming leads, and treat the engagement as time-boxed from the outset — meaning the developer sets a reminder to review or end that access when the qualification sprint or contract period ends, rather than leaving it open indefinitely "in case we need them again." If the engagement is renewed, access is renewed deliberately; it doesn't just persist by default. This is the same discipline that would have prevented the forgotten former-agency login in the opening scenario — the fix isn't a smarter agency, it's a developer-side habit of treating every external grant as expiring unless actively renewed.

Onboarding and Off-Boarding as a Routine, Not an Afterthought

The single highest-leverage habit here is treating team access as a routine with two clear, repeatable halves.

Onboarding: when someone joins — whether an in-house hire or an agency caller — invite them by individual email, assign the narrowest role that lets them do their job, and confirm with them what they can and cannot see before they start working leads. This takes minutes and prevents both over-granting (giving them everything "to be safe") and under-granting (giving them too little and creating support friction on day one).

Off-boarding: the moment someone's role ends — resignation, termination, end of an agency contract, or even a temporary leave where access isn't needed for a while — revoke their access from builder settings that same day. Off-boarding is the step that gets skipped most often, precisely because it isn't triggered by anything visible in the portal itself; it depends on someone in HR or operations remembering to tell whoever manages team settings. Building a habit — off-boarding checklist includes "revoke DrawMagic portal access" as a standing line item — closes that gap for good.

Lead-ownership hygiene follows the same logic. When a lead is reassigned (an executive leaves, a project is handed to a new manager, a city desk changes hands), reassign the lead to a named owner rather than leaving it in a departed person's queue. An unowned or orphaned lead is exactly how a buyer ends up getting no follow-up at all, or — worse — a second, uncoordinated call weeks later from someone who has no context on the earlier conversation.

Pro Tips for Getting Team Access Right

• Default to least privilege. When in doubt about how much access someone needs, grant less and expand later — it's far easier to add access to someone who's missing something than to walk back access that was already over-granted.
• Assign access per project or city desk, not blanket-wide. This keeps pipelines clean and makes it obvious who owns which conversations.
• Make off-boarding a same-day action, not a weekly batch job. A login that outlives the relationship is the most common and most avoidable exposure.
• Review access quarterly, even if nothing has changed. A short, scheduled look at who has what access catches drift before it becomes a problem — and gives you a clean answer if a buyer or regulator ever asks "who had access to my data."
• Treat every external partner grant as time-boxed by default. Agencies and outsourced callers should have an explicit expiry or review point built into the arrangement, not an open-ended login.

Common Mistakes to Avoid

• Shared logins across a team. One login used by three sales executives destroys any hope of a clean audit trail and makes lead ownership genuinely ambiguous.
• Over-granting "to be safe." Giving a junior executive full portal access because it's simpler than scoping properly just increases your exposure without any operational benefit.
• Skipping off-boarding. The single most common gap — access that should have ended the day someone left, but didn't.
• Leaving leads unowned after a reassignment. An orphaned lead in a departed executive's queue is a buyer who won't get followed up on.
• Treating agency access as permanent by default. External partners' access should be reviewed and renewed deliberately, not left running indefinitely because nobody circled back.

How This Fits with the Rest of Your DrawMagic Builder Setup

Team access isn't a standalone setting — it's the layer that determines how safely your whole builder operation runs. The builder dashboard is where your team actually works day to day, so getting access scoped correctly in builder settings directly shapes what each person sees the moment they log in. And as your firm grows and takes on more sales staff or agency partners to manage a larger project pipeline, it's worth revisiting your plan on DrawMagic's pricing page to make sure your account tier matches your team size. If you're a developer exploring the platform for the first time, the builders overview is the right starting point to understand what the portal offers before you start inviting a team into it.

Clean access isn't just a defensive measure — it's what makes fast, accountable lead handling possible in the first place. When every lead has a clear owner and every team member's access matches their actual job, follow-ups happen faster, disputes about "who was working this buyer" disappear, and off-boarding a departing employee takes thirty seconds instead of becoming a lingering question mark.

Key Takeaways

• Treat consented buyer data in your portal as personal data requiring least-privilege access — this is a DPDP-era responsibility resting on the developer, not just good practice.
• Invite team members individually by email; never share one login across multiple people.
• Assign roles based on job function (sales executive, manager, marketing coordinator, external agency) and scope access to the specific project or city desk each person handles.
• Use /builder/dashboard as the daily workspace and /builder/settings to configure who's on the team and what they can see.
• Scope outsourced tele-calling and marketing agency access narrowly and treat it as time-boxed, reviewed and renewed deliberately.
• Revoke access the same day a person's role ends — this is the most commonly skipped and most consequential step.
• Reassign leads to a named owner whenever a team member's role changes, so no enquiry sits unowned.
• Run a quarterly access review even when nothing has visibly changed, to catch drift early.
• Avoid over-granting access "to be safe" — narrower access reduces both accidental disclosure and lead-handling confusion.
• As your team and project pipeline grow, revisit your account plan on /pricing alongside your access setup.

FAQ

Does DrawMagic decide who gets access on my portal? No. DrawMagic provides the settings and controls; the developer's account owner decides who is invited, what role they're assigned, and when access is revoked. DrawMagic does not manage your team's employment relationships or your buyer-data handling policies.

Can I give an outsourced agency access without giving them everything? Yes — that's the purpose of scoped, role-based access in /builder/settings. An agency can be limited to a specific project's lead batch rather than your full portfolio.

What happens to a lead's history if I reassign it to a new executive? The lead's existing conversation and status history stays with the lead record; reassigning it changes who is responsible for following up going forward, so the new owner has full context rather than starting cold.

How often should I review team access? A quarterly review is a reasonable baseline for most growing developer teams, with an immediate review any time someone's role ends or an agency engagement wraps up.