NextoraShowing the client the project without giving away the CRM
Status update emails are a tax on delivery. A scoped client portal — a link, an access code, and only the sections you switched on — removes it without exposing budget, risks or anything else internal.
Delivery teams pay a quiet tax: the weekly status email. Someone reads the board, translates it into prose, softens the bad news, and sends it. The client reads it, asks the one question it did not answer, and the thread begins. Multiply by every active project.
The obvious fix — give the client an account in your workspace — is the reason most teams never fix it. Nobody wants a customer one wrong click away from another customer's deal.
A portal is a scoped view, not an account
The Nextora client portal is the outward-facing page of a project. It opens with a link plus an access code, and needs neither an account nor a login. The client sees exactly what you allowed: status, milestones, tasks, files, the board, and a chat with the team. Risks, budget, internal discussion, other projects and the whole CRM stay inside.
The crucial part is what "not enabled" means. A section that is off is not merely hidden from the menu — the server does not hand over its data at all. That distinction is the difference between a permission model and a UI convention, and it is the first thing to check in any tool that offers something similar.
| Section | What the client sees |
|---|---|
| Overview (on) | State — healthy, needs watching, critical — progress, tasks done of total, milestones, phase, target date |
| Chat (on) | The conversation with your team |
| Milestones (on) | The list, with the nearest marked "up next" and overdue dates in red |
| Tasks | Project tasks with open / done filters, statuses and dates |
| Pipeline | The stages as a track: passed ones ticked, the current one labelled |
| Files | Project files with size, date and download |
| Canvas | The project board your team uses, minus the kanban |
Access: a link, a code, and no way around them
You enable the portal from inside the project. Nextora generates a unique link and an access code; you copy both and send them, or use the invite tab and let the email go out by itself. Two properties matter:
- The code is shown only when it is generated. After that its place reads "code set — rotate to reveal a new one". Rotating invalidates the old code that same second. Inconvenient exactly once, and correct forever after.
- The portal page is closed to search engines and cannot be found by the project name. The link together with the code is the only way in.
The sign-in screen asks for the code and the client's name — the name so your team knows who is writing in the chat, which is the small detail that makes shared portals usable for a customer with five people involved.
What to leave off
Budget, risks and internal discussion. Not because clients cannot handle them, but because a portal is a place you can point at without re-reading it first. The moment a section needs curating before every share, it stops being self-service and becomes another status email.
Transparency changes what gets asked
When the client can see milestones and task status, the questions change shape. "Where are we?" disappears — it is on the overview. What arrives instead is "milestone two moved, what happened?", which is a conversation worth having, on a specific object, in the project's own chat rather than in someone's mailbox.
It also changes your own hygiene. A board somebody outside the team looks at gets kept up to date, because the cost of a stale card is now visible. That effect is worth as much as the saved emails.
Where the project came from
A portal is only as good as the project behind it, and the project should be the continuation of the deal you won — the same customer, the same company, the work that was promised. That chain is the subject of the CRM record model: enquiry, person, organisation, money, work, each recorded once.
Then the delivery side does its part: a project keyed with a short code so tasks read MER-14, a scenario that seeds stages and milestones, and an attention view that surfaces what is blocked, overdue, ownerless or has not moved for two weeks. The portal simply shows the honest version of that to the person paying for it.
See the delivery workspace on the projects page.
See it on your own process.
Nextora is in private alpha: CRM, projects, ERP, omnichannel conversations and AI employees on one record model. Bring the process you want to fix and we will shape the workspace around it.