Home Blog Who can see client data? Role-based access as a DPDP habit
Workplate Journal / Practical guide

Who can see client data? Role-based access as a DPDP habit

Client files travel farther than most firms notice. A return folder shared on WhatsApp. A draft agreement emailed to the whole practice group. A CRM export left on a shared drive “for convenience.” None of that feels reckless in the moment. It becomes hard to explain later—when a client asks who had access, or when a junior leaves with more visibility than the engagement needed.

India’s Digital Personal Data Protection Act (DPDP) has pushed many firms to talk about consent and notices. Access control is quieter, and often more practical. Knowing who can see what—and being able to change that quickly—is a habit worth building before a complaint or an audit forces the conversation.

This is not legal advice. It is a working pattern for professional services teams that handle personal and business data every day.

Start with roles, not with people

Name the jobs that need data, not the individuals who currently hold it. Typical roles in a mid-size firm might include:

  • Partner / engagement lead
  • Delivery associate
  • Reviewer or quality checker
  • Client success / relationship owner
  • Finance or billing
  • Admin / ops

Each role should answer three questions: which clients, which document types, and which actions (view, edit, share, export, delete). When someone joins or leaves, you change the role assignment—not a pile of ad-hoc folder permissions.

Separate “need to know” from “nice to have”

Juniors often get broad access because it is faster to grant than to explain. That habit creates two risks: oversharing of personal data, and noisy workspaces where people cannot find what matters.

A tighter default helps:

  1. Engagement-scoped access — team members see the matters they are assigned to, not the whole book of business.
  2. Stage-based visibility — drafts stay with authors and reviewers until a status change widens the circle.
  3. Export and share as deliberate acts — downloads and external forwards leave a trail, or require a higher role.

You do not need a perfect matrix before you tighten access. You need a default that is narrower than “everyone on the team drive.”

Make access review a calendar event

Permissions drift. People rotate across clients. Contractors finish a project and keep login rights for months. A light quarterly review is enough for many firms under 100 people:

  • List active users and their roles
  • Remove leavers and dormant accounts
  • Confirm who can export client lists or signed documents
  • Check shared WhatsApp groups and drive folders that sit outside the system of record

Document that you did the review. The habit matters as much as the tool.

Align channels with the same rule

Role-based access fails when the official system is locked down and the real work happens in unmanaged channels. Map the usual paths:

| Channel | Typical risk | Habit to install | | --- | --- | --- | | Email | Wrong CC, long threads with attachments | Prefer links with expiry over file dumps | | WhatsApp | Personal devices, group sprawl | Keep summaries in the engagement record | | Shared drives | Forever-open folders | Tie folders to live assignments | | AI assistants | Pasting client text into personal tools | Prefer assistants that stay inside firm context |

DPDP conversations often focus on policies. Delivery teams need the operational counterpart: fewer places where client data can live without a named owner.

Soft compliance language that teams will actually use

Partners do not need a policy binder on every desk. They need short rules that survive busy season:

  • Client personal data stays on assigned engagements
  • Sharing outside the engagement needs a reason and a record
  • When in doubt, ask the engagement lead—not the group chat

Pair those rules with software that enforces roles, so the policy is not only a PDF.

Where Workplate fits

Workplate is modular business software for Indian professional services firms—CA, IT services, law, company secretaries, and agencies. Projects, CRM, and eSign already share one login and one account across live modules, including Invoice and AI Chat, with deeper cross-module automation still maturing.

On access, the useful bar is simple: assign people to work with clear roles, keep client context with the engagement, and avoid building a second shadow store of files “just for the team.” eSign on Workplate covers Aadhaar-based signing for ordinary business documents; it is not a substitute for DSC workflows or MCA filings.

Soft next step

If your firm cannot answer “who can open this client’s files today?” in a few minutes, start with roles and a quarterly access review. Tighten the channels after the system of record is clear. When you are ready to run projects, CRM, and signing under one account with role-aware access, look at Workplate—and keep your DPDP counsel in the loop for formal obligations.

Explore the Workplate platform →

Start with the work that matters most.

Book a focused walkthrough of the module your firm needs first. Bring your workflow and your questions.

Book a Demo →