Manual or dynamic groups
Select contacts or define groups by company and customer category. They update when the data changes.
Bring guides, requests and updates into a portal with your identity. Customers can find information, open tickets and follow conversations with your team.
From search to resolution
Customers find an answer, submit a request when needed and follow every update from the same branded portal.
Search covers the articles, tutorials, FAQs, glossary entries and downloads published on that portal. Every search is recorded, including the ones that come back empty.
While the customer fills in the form, the portal suggests relevant articles before submission.
Use a form you have built and published, with your fields and attachments, open to everyone or authenticated users only.
Customers see their ticket history, filter by status and priority, read replies and respond without switching to email.
Control and identity
Create contact groups to make knowledge base content and forms available to the right people.
Select contacts or define groups by company and customer category. They update when the data changes.
Content cannot widen access denied by its folder. Rules remain combined when you move or republish it.
Before publishing, check the result for a real contact or an unauthenticated visitor.
Each portal has its own public name, logo, favicon, colors, languages and footer.
Email invitations, explicit statuses, per-portal access and bulk user operations.
On Enterprise, end users sign in through their existing identity provider, without another password.
Multiple portals
Create separate portals for brands, products or customer groups, each with its own identity, content and settings. The same article can appear on several portals or just one.
| Portal | Address | Status | Content published |
|---|---|---|---|
| Customer support | support.example.com | Active · Default | Guides, FAQs, downloads |
| Reseller area | resellers.portal.uppo.io | Active · Private | Price lists, contracts, tutorials |
| New product | beta.portal.uppo.io | Not active | Release notes |
Illustrative example. All portals are configured within the same Uppo company, with the same team and queues.
Create contact groups and use them to make knowledge and web forms available only to the right people. Rules apply to both visibility and submission, not just navigation.
Every portal starts on a portal.uppo.io subdomain. You can also configure a custom domain, depending on your plan.
Select contacts or define groups based on their company and customer tier. Dynamic groups update as the underlying data changes.
Include only selected groups or exclude them. The same model applies to folders, individual content and web forms.
Content cannot broaden access denied by its folder: rules combine and stay protected when content is moved or republished.
Before publishing, check the result for a real contact or an anonymous visitor and inspect the effective rules.
Customise identity, header, layout, navigation, languages, ticketing and footer. You can use a custom domain with a managed certificate, depending on your plan.
Invite customers, decide which portals they get into and revoke access when you need to, from a single list.
Access rules also protect search, attachments and form submissions.
Public name, logo, favicon, colours, languages and footer belong to each portal. Changing one leaves the others alone.
Categories and content are published on the portal that needs them: the same article can sit on several portals, or on just one.
Every portal is configured from the same Uppo account, with the same team, the same queues and the same assignment rules.
A portal can be prepared quietly and switched on when it is ready; switching it off loses neither content nor settings.
From the portal, customers see the history of their tickets, filter by status, priority, topic or date, read the replies and answer without going through email.
Someone without an account opens a single ticket from the link: the one it was generated for, and nothing else belonging to your company. The link gives access without signing in and should be kept confidential. Every visit is recorded, with the date of the last access and the number of openings.
Open the knowledge base to everyone, keep conversations for signed-in customers, or combine the two.
Anyone can read the knowledge base and raise a request without signing up. The right shape when support doubles as a shop window and answers need to be reachable from search engines.
Access is by invitation: end users only see the portals you have granted them.
The knowledge base stays public, while the ticket area requires signing in: open content and private conversations in the same portal.
Those three shapes come out of separate settings you can combine however you need.
On the Enterprise plan, end users sign in with the identity they already have instead of managing another password: authentication goes through your provider, and the user record shows which external identity it is linked to.
SSO, IP restrictions and audit trailInvite customers, decide which portals they get into and revoke access when you need to, from a single list.
You invite someone by email; until they complete the process they stay pending, and the invitation can be sent again.
Active, pending, inactive or revoked. The status shows in the list, can be filtered on, and is changed from the user's record.
Access is granted per portal, not per company: the same person can be let into one and kept out of another. Who granted it and when stays on record.
Grant or revoke access for a group of selected users in one go, instead of opening one record at a time.
With single sign-on the user is created on first login, and the record shows the external identifier they are linked to.
First sign-in, last sign-in and number of sign-ins, so you know who actually uses the portal.
Customise identity, header, layout, navigation, languages, ticketing and footer. You can use a custom domain with a managed certificate, depending on your plan.
Public name and internal name, logo, favicon, and the address the logo links back to.
Title, subtitle and the text inside the search box: the first three lines a customer reads.
Pick one of the available layouts and set the primary, secondary and accent colours.
One default language plus the active ones, portal by portal.
Page titles, permissions for submitting and reading, available filters, personal signature and published forms.
Titles, visibility, author name, comments and article feedback collection.
Text, your own links, legal name, company details and the privacy, cookie and terms addresses.
A portal starts on a portal.uppo.io subdomain. Depending on your plan, you can replace it with your own domain.
Custom domains are available depending on your plan. We handle the certificate: what you need is two DNS records.
Enter the full name, for example support.yoursite.com. Uppo returns the records to create.
One CNAME proves the domain is yours and allows the certificate to be issued; the other routes traffic to the portal.
The domain's status stays visible, with the validation and rollout dates. You can have the records checked again without starting over.
Until your own domain goes live, the portal keeps answering on its original address: there is no moment when it is unreachable.
Analyse searches, missing results and most-read articles to improve self-service continuously.
The words customers actually type, ranked by volume, over the period you choose.
The list of questions the portal could not answer: your content backlog, already prioritised by customers.
Which content carries the traffic, with views over the period and where readers came from.
Content opened often and rated unhelpful, or never opened at all: the pieces to rewrite or retire.
How much demand the knowledge base absorbs and how much still turns into a request.
Turn it on for a portal and customers say whether an article helped, with room to explain why.
These are your portal’s own numbers. A newly published portal fills up with its first visits.
Compare portals, private-portal monthly active users, languages and customisation options.
| Feature | Starter | Growth | Scale | Enterprise |
|---|---|---|---|---|
| Portals you can publish | 1 | 2 | 5 | Scalable |
| Public portal users and views | Unlimited | Unlimited | Unlimited | Unlimited |
| Monthly active private portal users (MAUI) | 25/month | 100/month | 250/month | 1,000/month |
| Knowledge base languages | 1 | 2 | 5 | Scalable |
| Custom domain with managed certificate | — | Included | Included | Included |
| Full white-label | — | — | — | Included |
| SSO and SCIM provisioning for end users | — | — | — | Included |
Logo, favicon and colours can be customised on every plan. A dash marks a feature that is not part of the plan.
Compare plans and pricingAccess, content, domains and managing multiple portals.
Yes. How many depends on the plan: one on Starter, two on Growth, five on Scale, an agreed number on Enterprise. Each portal has its own settings, content and authorised users, and can be switched on or off without touching the others.
Availability depends on your plan. Every portal starts on a portal.uppo.io subdomain; to replace it you add your domain and create two CNAME records at your DNS provider, one so the certificate can be issued and one to route traffic. Until it goes live, the portal keeps answering on its original address.
It depends how you set the portal up. The knowledge base can stay open to everyone, and raising a request can be left open or restricted to signed-in users. Anyone who receives the link to a ticket by email can read it and reply without registering.
Yes. Each piece of content is published on the portals where you want it: the same library feeds a portal open to customers and a private one for resellers, with different catalogues and one editorial team.
Yes. For each portal you pick a default language and the active ones. How many knowledge base languages you get depends on the plan: one on Starter, two on Growth, five on Scale, and an agreed number on Enterprise. Content is shown in the language requested, so translate the sections you want published in that language.
Data is separated per company, and an end user only sees the tickets they are linked to, on the portals you granted them. The link sent by email opens a single ticket without signing in, so it should be kept confidential. Every visit is recorded. For confidential conversations, the recommended path is the signed-in portal.
The visitor stays on the portal and can raise a request from there. The search lands in the list of searches with no results, which you can review by period: the most direct way to learn which content is missing.
How the content your portal publishes is written, organised and translated.
Go to the knowledge baseThe same content and the same form inside your own site, without sending the visitor away.
Go to the widgetCompare portals, languages, custom domains and white-label options across plans.
See the plansTickets, SLAs, automations, workflows, analytics and security: the full picture.
See the featuresIf you serve more than one brand, have an identity provider to connect or your own rules about who sees what, the Enterprise plan is agreed around your numbers.
Public content, private requests: you decide what each audience can see.