PROJECT MANAGEMENT WITH A CLIENT PORTAL
Project Management With a Client Portal That Keeps Internal Work Internal.
Manage detailed client work, assignments, review and costs inside Bikabo, while clients get a simpler view of what is in progress, what has been delivered, their files and their conversation with your business.
One Project, Two Purpose-Built Views.
The alternative most tools offer is a guest seat on your project board with some columns hidden. That is a permission configuration, and permission configurations get changed by people in a hurry.
Your team sees
Your team keeps the detail
- Assigned, submitted, awaiting review, revision required, approved.
- Who is doing the work and who is reviewing it.
- Every submission, every revision and the reason for each.
- Cost, exposure and margin on the project.
- Internal discussion and working files.
Your client sees
Your client gets clarity
- In Progress, or Completed.
- Files that have actually been delivered to them.
- Their conversation with your business.
- Scheduled work that concerns them.
- Payment information, where you choose to show it.
Internal Status Is Not Client Communication.
Your team needs granular states to run the work. Your client needs to know whether they have it yet. Mapping one onto the other is the whole design problem, and Bikabo answers it the same way every time.
Internally
Assigned, In Progress, Submitted, Awaiting Review, Revision Required, Approved.
Six states your team acts on, each one telling somebody what to do next.
To the client
In Progress. Then Completed, once it has been delivered.
Two states, both honest, neither of them a euphemism.
Completed means delivered, not approved. Work that has passed review but has not gone out is still In Progress as far as the client is concerned, because as far as the client is concerned, it is.
Files the Client Should Have, and Only Those.
A project accumulates working files, drafts, internal references and the actual deliverable. Only the last of those belongs to the client.
Whether a file is client-visible is decided when it is uploaded, and a client can only retrieve one where the file, the Task and the Engagement are all marked visible and the work has actually been delivered. All three are checked on the download itself, so a shared link or a guessed address gets nowhere.
Messaging Without Internal Chat Leaking.
Clients write to your business. Your team talks among itself. These are different kinds of record, not one channel with permissions on it.
A client message can be forwarded internally so the team can answer it, and their answer becomes a draft you edit and send. Nothing reaches the client until somebody on your side sends it, in the words they chose.
Money the Client May See.
Where you enable it, a client can see what they agreed, what they have paid, what is outstanding and their invoices. Internal cost, margin and staff payouts are not part of what a client-facing page is able to return at all.
Access Is a Lifecycle, Not a Switch.
A client record and a client login are separate things, and most clients never need the second. Access is invited, becomes active, can be suspended and reactivated, and can be revoked.
A portal session is its own identity rather than a limited staff account, and visibility is opt-in at both the Engagement and the Task level. A project is not visible to a client because nobody remembered to hide it.
Why One Source of Truth Matters.
The reason most client portals go stale is that they are a second place to update. Somebody has to remember, and in a busy month nobody does.
Here the portal is a projection of the work itself. Deliver a Task and the client sees it as Completed, because it is the same record read through a different, narrower query.
A Client Portal, Not Guest Access.
Guest access takes your internal workspace and hides parts of it. Whether that holds depends on every field, every export and every notification being configured correctly, forever, by everyone.
A purpose-built portal starts from the other end: separate pages, separate sign-in, separate queries that only ever ask for what a client is entitled to. There is no configuration that turns it into a view of your internal operation, because the internal data is not in what it reads.
Who This Suits.
Agencies and service businesses whose clients ask for updates often enough that answering by email is a job in itself, and whose internal delivery process is not something they want to publish.
Two things this page does not claim:
- One portal user per client. Multiple client contacts are planned, not live.
- No custom client branding, client subdomain or client-configurable roles.
Questions About Client Portals
Because a client watching internal statuses learns things that are true but unhelpful: that their work was rejected twice, that it moved between three people, that somebody is behind. It also puts your delivery process, your reviewers and your cost structure one misconfigured permission away from being visible.
Their Engagements, work as In Progress or Completed, files that have been delivered, their message thread with your business, scheduled work that concerns them, and payment information where you have enabled it. Nothing else.
Everything before delivery reads as In Progress: assigned, in progress, submitted, awaiting review, revision required and approved. Once work is delivered, it reads as Completed. Cancelled work is handled separately rather than being flattened into either.
No. Approval is an internal quality decision; delivery is the act of handing the work over. Only delivery moves a client-facing item to Completed.
No, and that is the important part. It is a client-safe view of the same records your team works in. Deliver something internally and the client sees it immediately, because there is nothing to sync.
Never. Internal cost, exposure, margin and staff compensation are not part of what a client-facing page can return. What a client may see about money is what they agreed, what they have paid and what is outstanding, and only where you have turned that on.
Yes. Portal access can be suspended and reactivated, or revoked outright, without touching the client record or any of their history.
Not today. Bikabo supports one portal user per client. More than one contact is a planned capability rather than a current one.