Everyone can build. IT stays in control.
Some of your people are already vibe-coding apps and dashboards with AI. Harriet Sites gives them a place to publish: shared with the people they choose, behind sign-in, and visible to IT.
Book a demoBuild a dashboard of this quarter's pipeline by region from our CRM report.
- Read the CRM pipeline report
- Built the dashboard
- Published version 1
Your dashboard is live at k7m2q9xa4d.harriet.page. It's private to you until you share it.
Share it with Sales leadership.
Shared with the Sales leadership group. They sign in with Harriet to open it, and everyone else is turned away.
Pipeline by region
Q4 · by region
Data updated Monday 08:00
What changes when anyone can build
Anyone can build
Describe the app or dashboard you need. Harriet builds it from your connected systems and publishes it. No git, no hosting, no ticket to IT.
Share with the right people
Choose the people, groups or whole company who can open it. Everyone else is turned away, and one link is all it takes.
What people build
Read-only pages that show a team the figures it works from, kept current on a schedule.
-
Sales
Pipeline by region
Pipeline, win rate and deal size by region for the weekly leadership meeting.
-
Finance
Month-end close status
Which reconciliations are done and which are waiting, refreshed every morning.
-
People
New starter hub
Who to meet, what to set up and which policies to read in the first week.
-
Support
Support queue health
Open tickets, response times and backlog by team, for the daily stand-up.
Illustrative examples.
From a request to a shared app
The person who needs it builds it and decides who sees it. IT gets the record.
Read how sharing worksBuild a dashboard of this quarter's pipeline by region from our CRM report.
Harriet read the report, built the page and published version 1. It is private to you until you share it.
Version 1 · Owned by you
k7m2q9xa4d.harriet.page
- SSam RiveraSales leadership Opens the appAfter signing in with Harriet
- JJordan LeeFinance You don't have access to Pipeline by regionAsk Maya Chen, who owns it, to share it with you.
- Not signed inAnyone with the link Log in to Harriet to see this private site.Then back to the app, if it is shared with them.
What people did, and who signed in.
Illustrative example. The people, company and figures are made up.
Every app in the company, under your rules
Admins get one list of every app in the company: its owner, who it is shared with, when it was last opened and what needs attention. They manage apps from here without being able to open the ones that aren’t shared with them. See how Harriet handles security across the platform.
All sites
Sites someone at your company can open, and sites with no owner. A site shared with nobody isn't listed here.
Needs attention
| Site | Owner | Status | Shared with | Last opened |
|---|---|---|---|---|
| Pipeline by region | Maya Chen | LiveVersion 2 | Viewers: 1 group and 1 person | Today |
| New starter hub | Alex Kim | LiveVersion 4 | Everyone at Meridian | Yesterday |
| Support queue health | Priya Shah | LiveVersion 3 | Everyone at Meridian | 3 days ago |
| Month-end close status | Daniel Cho | Paused: owner leftAn admin needs to assign a new owner. | Viewers: 1 group | 12 days ago |
| Pricing calculator | Jordan Lee | Deploy failedVersion 1 is still live. | Only the owner | Never |
| Office move guide | Lena Fischer | LiveVersion 1 | Viewers: 3 people | 104 days ago |
Showing 6 of 6 sites
Illustrative figures for a made-up organization.
A record of everything
Who created, shared, published and signed in is logged. Filter the audit log by app, person or action, and export it as a CSV.
Private until shared
A new app is visible only to its owner. Nothing is public, and apps shared with nobody stay out of admin lists too.
Someone always owns it
If an owner leaves, their apps pause until an admin chooses a new owner. Reassign one app or all of them at once.
You decide who can create
Let everyone build, or limit creating to one group. Account owners and people with the Manage sites permission manage the rest.
Safe to update
Every publish is a numbered version, and two editors can’t overwrite each other. If a publish fails, the last good version stays live.