Security and control, built into the helpdesk

Manage identities and permissions, restrict access to approved networks, track activity, and scan attachments before they reach your team.

  • Identity, access and content protection controls
  • Data hosted in the European Union, isolated by company
  • SSO, IP restrictions and audit trail from Scale
Security and control, built into the helpdesk

Layered protection

Controls for identities, access and attachments

Manage authentication, authorisation, network access, traceability and data protection from one platform.

Identity and access

Two-factor authentication for everyone, single sign-on from Scale and SCIM provisioning for Enterprise organisations.

Roles and permissions

Configure roles and permissions for tickets, contacts, content, settings and reports.

Approved networks

IP address and CIDR range restrictions across the application and APIs.

Audit trail

A searchable record of actions performed by agents and administrators.

Data protection

Isolation per company, encrypted traffic, EU-hosted data, and masking in logs and exports.

Protected attachments

Manage attachment quarantine, malware scans and their results.

Identity and access

Connect Uppo to your company identity system

Centralise agent access on the identity provider your organisation already uses, and add a second factor for anyone signing in with Uppo credentials.

  • Two-factor authentication on every plan
  • SAML 2.0, OIDC and LDAP Single Sign-On from Scale
  • SCIM 2.0 provisioning with your company directory on Enterprise
  • Map identity-provider groups to Uppo roles
  • Disable a person in the directory to revoke access
  • Verified sending domains with TXT and DKIM records

Identity providers

SAML 2.0
Single Sign-On · Scale
OIDC
Single Sign-On · Scale
LDAP
Single Sign-On · Scale
SCIM 2.0
Provisioning · Enterprise
2FA
Two-factor, on every plan

Attachments

Quarantine and scanning for widget attachments

From Scale, you can enable scanning with the Uppo team for files sent when a ticket is opened through the widget. Administrators can review the results.

  1. 01

    Received

    The file arrives with a new request from the widget.

  2. 02

    Quarantined

    It is held aside: not downloadable and not served to anyone, agents included.

  3. 03

    Malware scan

    The contents of the file are analysed, not the name and not the extension.

  4. 04

    Result

    Clean, blocked, or to be retried when the scan does not reach a conclusion.

  5. 05

    Release

    A clean result makes the file downloadable. A blocked one keeps it in quarantine.

  6. 06

    Rescan

    An administrator can queue a file again, for instance after the engine's signatures have been updated.

Network control and audit

Restrict access and trace activity

Limit access to the app and APIs to your organization’s networks and review the activity log for your workspace.

Application and APIs

Restrictions are enforced on API requests as well, not only in the interface.

One list per company

Single addresses or ranges in CIDR notation, which administrators can update at any time.

Approved networks only

Access is allowed only from the networks on the list: requests arriving from anywhere else are refused.

Action, author, timestamp

Every action on company resources is recorded with who performed it, when, and on which object.

Search filters

Filter the log by period, person and resource type.

Configured retention

The retention period is set on your account: you will find it in the settings and in your contract.

Redaction example
credit_card
•••• •••• •••• 4242
tax_id
RSS••• •••• ••00A
iban
IT•• •••• •••• ••89
email
m••••@example.org
phone
+39 ••• ••• 4521

Masking sensitive data

Protect sensitive data in logs and exports

Mask sensitive data in logs and exports with predefined classes, selected fields and rules you write yourself. Included from the Scale plan.

  • Built-in classes or custom rules
  • Choose which fields to cover: values disappear from the outgoing copy
  • Exports and logs leave already redacted, rather than being cleaned later
  • The original ticket remains available to people with permission to view it

Data and integrations

EU-hosted data, isolated access, controlled integrations

Manage identities, data access and integration credentials in the same workspace.

  • Service infrastructure hosted in the European Union
  • Encrypted traffic: application, public portals and APIs over HTTPS
  • Company isolation: resources served only in their owning context
  • Signed webhooks and Basic or Bearer authentication for outgoing calls
  • Dedicated credentials with permitted operations defined on API keys
  • Export your content whenever you need it

Availability by plan

Which controls does your plan include?

Features that vary by plan. Compare prices and limits on the plans page.

FeatureStarterGrowthScaleEnterpriseWhat you need to use it
Single sign-on (SAML 2.0, OIDC, LDAP)Starter: —Growth: —Scale: IncludedEnterprise: IncludedYour identity provider and its federation metadata.
SCIM 2.0 provisioningStarter: —Growth: —Scale: —Enterprise: IncludedA connection to your directory and a group-to-role map.
IP and CIDR restrictionsStarter: —Growth: —Scale: IncludedEnterprise: IncludedThe list of allowed addresses.
Extended audit trailStarter: —Growth: —Scale: IncludedEnterprise: IncludedAccording to the plan and account configuration.
Data masking in logs and exportsStarter: —Growth: —Scale: IncludedEnterprise: IncludedPredefined classes are active; your own rules are added on top.
Widget attachment quarantine and scanningStarter: —Growth: —Scale: IncludedEnterprise: IncludedActivation and scan verification with the Uppo team.
Retention of blocked attachmentsStarter: —Growth: —Scale: IncludedEnterprise: IncludedAsk the Uppo team about applicable retention.

A dash marks a feature not included in the plan. Two-factor authentication, feature-based roles and permissions, and company isolation are included in every plan.

Frequently asked questions

Questions from security and IT teams

Can’t find your answer? Contact the team
More questions
What does the audit trail record?

Who performed an action, when, and on which resource, for agent and administrator actions on your company's data. The log can be filtered by period, person and resource type, and its availability depends on your plan and configuration. It is an application log protected by permissions: for retention or certification requirements, talk it through with the team.

What happens to a blocked file?

It stays in quarantine and nobody downloads it. Administrators can see its status and request a new scan, for instance after a signature update. Contact the Uppo team about retention for blocked files.

Where is the data hosted?

Service content is hosted in the European Union. The privacy notice and DPA describe the providers and applicable transfers. If you require a specific country, discuss this with our team before subscribing.

Which security features does my plan include?

Configure access and controls for your organisation. Availability of single sign-on, the activity log, IP restrictions, data redaction, quarantine and SCIM depends on your plan and configuration.

Which SSO protocols are supported?

SAML 2.0, OIDC and LDAP. Single sign-on is included from the Scale plan and is configured against the identity provider your organisation already uses.

How does SCIM provisioning work?

Your corporate directory stays the source of truth: when an account is created, changes group or is deactivated, Uppo follows. Groups map onto roles, so people arrive with the right permissions on their first sign-in. SCIM 2.0, Enterprise plan.

Can I restrict access by IP?

Availability depends on your plan and configuration. You list single addresses or CIDR ranges and access is allowed only from approved networks, in the application and on the APIs alike. Before you save the list, include the networks your own team works from.

How is data masked in exports?

Redaction acts on the outgoing copy: exports and logs leave already masked. You use the predefined classes, choose which fields to cover, and add rules for the formats that are specific to your company.

Are attachments scanned by an antivirus?

The feature is available from Scale and requires activation with the Uppo team. With protection enabled, files sent when a ticket is opened through the widget go through quarantine and malware scanning before release.

Configuration and related resources
Documentation and compliance
  • Where data is processed

    Service infrastructure is hosted in the European Union. The Privacy Policy and DPA describe providers, processing locations and applicable safeguards.

  • Encrypted traffic

    The application, public portals and APIs all answer over HTTPS.

  • Separation per company

    Every request carries its company context, and resources are served only inside that context.

  • Signed webhooks

    The incoming webhook verifies a company-specific signature. Outgoing automation calls support configurable Basic or Bearer authentication.

  • Integration credentials

    Use dedicated credentials to connect your systems. Define which operations API keys may perform and consult the reference for supported operations.

  • Export your content

    Your company's content can be exported whenever you need it. Deletion is agreed with the team, in line with your contract.

Administrators keep control

Contact the Uppo team for file limits and retention periods.

Administrators keep control

In the console, you can review the status of files handled by this process and request a new scan.

Identity, access and data redaction
Two-factor, on every plan
Turn on two-factor authentication for the accounts in your workspace, with or without an external identity provider.
Single sign-on
SAML 2.0, OIDC and LDAP for agents: sign in through your organisation’s identity provider, included from Scale. Portal end-user SSO is available on Enterprise.
SCIM 2.0 provisioning
Synchronise account creation, updates and deactivation with your company directory. Included in Enterprise.
Groups already mapped to roles
Map identity provider groups onto Uppo roles: first time someone signs in, they already have their team's permissions.
Revoke in one step
Deactivate someone in the directory and their access to Uppo closes. You can also deactivate them from the console, keeping the history of the tickets they worked on.
Verified sending domains
Replies go out from your own domain once TXT and DKIM records are verified, so recipients can authenticate the sender.
Predefined classes
Apply the predefined classes or configure your own masking rules.
Selected fields
You choose which fields to cover. The value disappears from the copy that leaves, and the record stays readable to whoever is allowed to see it.
Custom rules
For formats specific to your company, a case number or a staff ID, you write the rule and apply it.
Exports and logs already clean
Redaction acts on the outgoing copy: exports and logs leave masked, rather than being cleaned up afterwards.

The original ticket stays intact and readable to whoever is allowed to see it: redaction only changes what leaves the system.

Make it work for your team

Give each person exactly the access they need

Build the roles your organisation needs and grant permissions feature by feature, to people and to teams.

Roles you build yourself

Adapt an existing role to your team’s responsibilities and assign only the permissions they need.

Permissions per feature

Tickets, contacts, knowledge base, settings and reports: assign permissions according to each person’s responsibilities.

Teams and work queues

Assign tickets to people or teams. The queue an agent opens follows the roles and permissions they hold.

Isolation per company

Data, attachments and content stay within the owning organisation's context, on every channel and every request.

Content visibility

On portals and knowledge bases you decide article by article what is public and what requires signing in.

Read more

All the features

Tickets, SLAs, channels, knowledge base and reports: what Uppo does, on one page.

See the features

Plans and limits

What each plan costs and the limits the platform applies to your account.

Compare the plans

Automations

Rules that assign, update and notify, with a log of every run.

See the automations

Evaluate Uppo with your Security and IT teams

Bring us your security questionnaire, your access policies and your data requirements: we will go through how they map onto Uppo together.