For Internal Tools

The internal tools your team stopped asking IT for

Guided intake, mass edits, and team consoles your admins build in a Screen Flow instead of rebuilding the same forms by hand every quarter.

Explore Flow Screen Components Request a Demo

70+

Flow Screen components

No code

configured in Flow

85+

across the suite

Avonni Map in step 2 of a Salesforce screen flow: a roof outline drawn as a polygon on OpenStreetMap tiles, with drawing tools and a Save survey button

Screen FlowsSite surveyA technician traces the roof on a live map, in step 2 of a screen flow, and the shape is saved on the work order.

Avonni Date/Time Picker on step 2 of a Salesforce flow: a week of thirty minute dental slots with lunch, booked slots and the weekend greyed out, Tuesday 10:30 selected

Screen FlowsBook the next visitOne week of slots, lunch and taken slots greyed out, one tap to pick. No calendar app, no back and forth.

Avonni Pen Input on the last screen of a Salesforce flow: a handwritten signature in blue ink on a signature pad, a reduced toolbar and a Save signature button

Screen FlowsCustomer sign-offThe customer signs on the last screen of the flow, and the signature lands on the work order as a file.

What you build

The tools your team actually needs

Real screens from real orgs: the approvals, edits and updates your team does every day, each one configured, not rebuilt.

Avonni Data Table Group By in a Lightning Web Component: expense lines grouped by employee with counts, status badges, three checked rows and an Approve selected button

An approval cockpit. Fourteen lines grouped by employee, select three, approve them from the header.

3

surfaces, one suite

Flows, Lightning pages and portals: the same components wherever the work happens.

Avonni Data Table on the Northwind Partner Hub, a live Experience Cloud site: the distributor's orders with a quantity edited inline, purchase order PDFs, delivery rings and status badges

A mass edit table. Quantities edited in the cell, purchase orders dropped into the row, from the partner site.

Avonni Kanban on a Lightning page: real estate listings grouped by stage, one swimlane per agent, photo on each card and a dollar total per column

A board that updates the record. Drag a listing to its next stage, the record follows.

See them in real orgs

Where to build it

Two ways to ship a tool

For internal tools

Guided, step by step

Flow Screen Components

70+ components for capture and review inside a Screen Flow: inputs, tables, pickers, and confirmations, wired to your objects.

Always-on consoles

Dynamic Components

Build the standing dashboards and record pages your team returns to every day, no Flow required.

The building blocks

Capture it, then show it back

25+Inputs

Everything for capturing clean data in a Flow.

Input TextText AreaComboboxDual ListboxCounterDate RangeTime RangeInput PenColor PickerIcon PickerSlider+14 more

20+Displays

Everything for showing that data back to the team.

Data TableKanbanListTimelineMetricChartFormatted ValueProgress IndicatorTreeMap+10 more

Mass editing

Edit the whole list, not one record at a time

1 screen

Avonni mass edit

Filter, edit inline, and save the whole set from a single table.

vs

1 by 1

Record by record

Open, edit, save, go back, repeat for every record on the list.

Same data, same permissions. The difference is how many clicks it takes your team to get through it.

From a Salesforce team

The flexibility is unparalleled. We considered building our own components, but Avonni was the clear top choice.

Tyler Teachman

Hitachi High-Tech America

FAQ

Questions about internal tools

Do I need a developer to build these tools?

No. Admins build guided Flows and consoles with clicks. The components handle the parts that would otherwise need custom code.

Does mass editing respect our permissions?

Yes. Edits run through your Salesforce sharing rules and field-level security, the same as any standard record update.

Can I use these components in a Screen Flow and on a page?

The Flow Screen components live in Screen Flows. For standing pages and consoles, the same suite includes Dynamic Components.

What kinds of input can I capture?

Text, numbers, dates, choices, signatures, and more, with validation built in so bad data does not make it through.

How is it licensed?

Every plan includes all three packages. You can start free with 10 licenses and scale as your team grows.

Build the tool instead of the ticket

Give your team guided intake, mass editing, and consoles they configure themselves, on the platform your data already lives on.

Explore Flow Screen Components Request a Demo