Skip to content

Product and engineering

What Usivity can and cannot do

A plain-language guide to Usivity’s scope. If you are evaluating Usivity, start here.

Product guide · 5 min read

The core principle

Usivity changes how your product looks and shows data for each user. Not what it does.

Every personalization lives in what users see and how they interact with it. It never touches your database, your APIs, your business logic or your application code. Your product runs exactly as it always has; each user chooses what they see and how it is presented.

What Usivity handles

These are the kinds of change Usivity is built for. Users ask for them in plain language, and Usivity applies them without a ticket, a sprint or a developer.

Layout and display

  • Reordering columns, sections or panels
  • Showing or hiding elements a user doesn’t need
  • Pinning rows, tabs or menu items for faster access
  • Changing label text, date formats or number display
  • Adding visual emphasis to specific rows or values

Data presentation

  • Adding calculated columns derived from existing data
  • Sorting or filtering tables to match a user’s workflow
  • Adding summary KPIs above a table or list
  • Color-coding rows by status or value thresholds
  • Reformatting currency, dates or identifiers to local conventions

Workflow shortcuts

  • Export buttons scoped to a specific view or filter
  • Progress indicators tied to visible data
  • Countdown timers based on displayed date fields
  • Quick-action buttons that work on visible rows
  • Column toggles to show or hide detail on demand

Context

  • Tooltips that explain fields or values in place
  • Banners or callouts that surface important information
  • Live data from approved external sources, shown inline
  • Highlighting values outside a range the user sets
  • Masking or formatting sensitive fields for display

What Usivity does not do

These boundaries are deliberate. They are what make Usivity safe to give to every user without a change-management process.

Database writes

Usivity never creates, updates or deletes records. It changes how data is shown, not the data itself.

Business logic

Workflow rules, calculation engines, approval sequences and backend processing are untouched. Usivity works only on what is rendered on screen.

Security or access policy

Usivity cannot grant access to data a user can’t already see. Your system enforces permissions and roles; Usivity never overrides them.

Navigation and routing

Usivity works within pages, not between them. It doesn’t change your app’s navigation, URLs or page routing.

Edge cases worth knowing

Some requests sit on the boundary. These come up most often in evaluations.

A user wants to pull data from an internal API and show it on a page.

In scope, if your team has approved that endpoint in the Usivity vendor dashboard. You control which endpoints are available.

A user wants to rename a label that also appears in reports or exports.

Usivity changes the label on screen only. Exports that read the rendered text will show the change; exports that read a database field name will not.

A user wants to hide a column that holds required information.

In scope: Usivity can hide any element the user can see. If the column is business-critical, leave that zone out of Usivity’s reach in your configuration.

A user wants to sort a table that updates in real time.

In scope. Usivity re-applies personalizations when the page updates, so the sort holds as data refreshes.

Want to see it in your context? Check whether Usivity fits your product, or read how Usivity integrates.

Your customers get a product that fits. Your roadmap stays yours.

In ten minutes we’ll show you what your customers can change on their own, and what your team never has to build.

Book a 10-minute demo

We reply within one business day.