Skip to main content
Apps/Portaliq
Betav0.1.8NL · ENView on GitHub

Portaliq

One portal for your clients and suppliers, on your own Nextcloud. They log in once and see everything you do for them.

Your client logs in once and sees their quotes, invoices, contracts and open requests from every app you run. Your supplier sees their own orders and contracts, never another supplier's. Every message from every app lands in one inbox for them. One login for them, one place for you, and it carries your logo and your colours. Your own staff stay inside Nextcloud. Portaliq is only for the people who are not. Open source, released under EUPL-1.2 and maintained by Conduction.
What it does

What your client sees. What your supplier sees. One front door.

Every app you run can show a piece of itself to the outside world. Portaliq collects those pieces into one portal per organisation, checks on every line who may see it, and delivers what the visitor sends back to the app it belongs to.

Your client logs in once. Their quotes, invoices and requests are there.

Today a client calls to ask where their invoice is, and someone looks it up. Instead, the client opens the portal and sees the invoice with its status, the quotation waiting for their signature, the order it became and the tickets still open. They accept and sign the quotation right there, pay an open invoice, and check their contracts and running projects. From every app you run, on one screen, behind one login. Fewer calls, and the calls you do get start further along.

Your supplier sees their own contracts. Never another supplier's.

A supplier logs in and finds their tenders, their contracts and their invoices. Portaliq checks on every single line that it belongs to the person who is logged in. Someone guessing at another company's number gets nothing, not even a hint that it exists.

Every message from every app in one inbox for them.

A status update from your case handling, a note from sales, a reminder from billing. The visitor sees them in one inbox, newest first, with an unread count on the menu. They mark a message read and you can see that they did. No more "I never got that email".

A request from the portal lands where your team already works.

The visitor submits a request or a complaint, with attachments, from the portal. It arrives in the app your team uses, as a record with the visitor's name already on it. The visitor gets a receipt. If delivery to the app fails, the submission is kept and marked so it can be retried. Nothing sent from the portal is ever lost.

They log in the way they already log in elsewhere.

Residents can log in with DigiD and companies with eHerkenning, through an identity broker your organisation contracts. Business clients can use the login provider you already work with. Portaliq itself never sees a password. Sessions expire, and you can end one from your side at any moment.

Three ways Portaliq earns its place

It works the way you work. And it works for you.

Three things you would normally pay extra for. In Portaliq they are built in.

TriggerStepStepApprovalEnd
Automate

A submission could not be delivered. Someone is already on it.

Today: a complaint sent through a web form vanishes into a mailbox nobody checks on Friday. Instead, set it up once. Every submission from the portal is a record. The moment one fails delivery, a task to retry it lands on the right desk. A message a client has not opened after a week puts a follow-up call on the account manager's list. Every Monday, a list of requests nobody answered. Nothing forgotten, no chasing, no coding.

How automation works
Make it yours

Your logo, your colours, your name on the door.

A visitor should see your organisation, not ours. Set the name, the logo and the colours per organisation, and the portal wears them on the login page and every screen after it. Run more than one portal from the same Nextcloud, each with its own look. Add a page of your own explanations and a glossary of the words your visitors ask about. Choose which apps show up in the menu and in which order.

Read the docs
Talk to it

Ask your assistant how the portal is doing. Visitors never meet it.

Portaliq's assistant serves your own staff, never the portal visitor. Ask "which submissions failed delivery today?" and you get the list, not a report to build. Ask how many clients logged in this month, or which messages are still unread. It reads the same records you are allowed to see and asks before it changes anything. On the visitor side there is no assistant at all, by design.

Meet the assistant
How Portaliq plugs into the workspace

The apps you already run, seen from the outside.

Portaliq shows nothing of its own. Every screen a visitor sees comes from an app your team already works in. Here is what each one shows.

A signed contract, an invoice as PDF, a letter about a case. If your team attached it to the record in Files, the visitor can download it from the portal, after Portaliq has checked that the record is theirs. Where you allow it, they upload a document back onto their own record. Nothing travels as an email attachment.

Read the docs
Partners

Partners shipping Portaliq

Implementation, hosting, and integration partners that deliver Portaliq to their customers. Pick the partner you already work with, or one whose stack matches yours.