Client portal for agencies in India: what it is and how to set one up
What a client portal is, what clients should and should not see in it, and how it replaces approval chasing on WhatsApp and email.

A client portal is a private login where your client sees their own work, approves or questions it, and finds their invoices, without asking you for a link. For an agency it replaces the chain of WhatsApp messages, emails and shared-drive folders where approvals usually get lost.
What a good portal shows the client
- Work waiting for their decision, with a clear approve button and a request-changes button.
- A simple progress view for each post, not your internal notes, task names or team members.
- Their invoices and what is paid or due.
- A way to message you that is not a personal chat.
- Your agency's own logo and name, so it feels like part of your service.
What a portal must never do
It must never show one client anything that belongs to another. That sounds obvious, but a portal built on a shared sheet or a shared folder can leak by accident. The safe design is a separate login per client that is limited to that client's data on the server, not just hidden on the screen.

How the portal works in ThodaLogic Ops
In ThodaLogic Ops you invite a client's contact by email and link the login to that client. They see only that client's content, approvals, invoices and messages. When they approve a post or ask for changes with a note, the decision is saved with the time against that post and it moves along the pipeline by itself.
- Add the client and their accounts.
- Create the content items for the month and move them to client review when they are ready.
- Invite the client contact from the Users page and choose the client role.
- Tell the client once: approvals go through the portal, not WhatsApp.
- Watch the decisions arrive, and let a workflow notify the right person when changes are requested.
Getting clients to use it
- Start with one client who likes order.
- Send the first approval together on a short call so they see how little effort it is.
- Keep WhatsApp for quick questions, and keep decisions in the portal.
- Do not move every client at once. Add one each week.
How we know it works
We built ThodaLogic Ops inside Thoda Logic and run our own client work on it. In October 2026 it went through a full end-to-end test pass covering the client login, isolation between clients, approvals and requested changes, and the notifications they trigger.
Quick answers.
A private login where each client sees only their own work, approvals, invoices and messages. It replaces approvals scattered across WhatsApp and email.
No. It is a normal web login.
Not in ThodaLogic Ops. Each client login is limited to that client's data on the server.
No. Clients see a simple progress view, not internal notes or the team members assigned.