Building a tool in Nyvlo gets you a working app that only you can see. Publishing is the moment you hand it to other people. This article explains what happens when you publish, how your team shares the same live data, and how roles, record ownership, and sign-in gating keep everyone in the right lane.
Publishing to a live link
When a tool is ready, you publish it and get a live link you can share with your team. The link points to the real, working app, not a screenshot or a preview. Anyone you invite opens the same tool in their browser and starts using it right away, with no install and no setup on their side.
You stay in control after you publish. You can keep editing, refine the tool, roll back to an earlier version, or unpublish the link when you want to take it down. Design tweaks, config edits, version rollbacks, and exports are always free.
It becomes a real shared database
A published tool is not a set of separate copies. It is one live database that your whole team reads from and writes to together. When a teammate adds a record, edits a field, or updates a status, everyone with access sees that change on their next view. The tool your team uses on Monday holds everything they entered on Friday.
Because the data is shared and live, the tool behaves like a small internal app rather than a static page. That is the point of publishing: to give your team a single source of truth they can all work in.
Roles owner member and viewer
Every published tool has three roles, and each one is enforced on the server, not just hidden in the interface. That means a person only ever gets the access their role allows, no matter how they reach the tool.
- Owner: you, or whoever you hand ownership to. Owners can edit the tool, publish and unpublish it, manage who has access, and see the data according to the tool rules.
- Member: a teammate who signs in and works inside the tool. Members can add and edit their own records and use the tool the way it was built to be used.
- Viewer: someone who can open and read the tool but cannot change its data. Viewers see what you allow them to see and nothing more.
Server enforcement is the important part. The rules that decide what each role can do run on our side, so a viewer cannot quietly act as a member, and a member cannot reach owner controls, even if they try to work around the screen.
Everyone sees their own records
Many tools are built so each person owns their own records. When record ownership is on, a teammate sees the rows they created, not everyone else's. Two people can use the same published tool at the same time and each keeps their own private set of entries.
This keeps a shared tool from turning into a shared inbox where everyone reads everyone. Owners can still be given a wider view when the tool calls for it, but by default each teammate works in their own space, and that boundary is enforced on the server together with the roles above.
Sign-in gated tools
You can require people to sign in before they use a published tool. When a tool is sign-in gated, a visitor has to authenticate first, and only then does the tool decide what they can see and do based on their role and their own records. This is how a link can be shared widely while the data behind it stays limited to the right people.
Sign-in gating and record ownership work together. Signing in tells the tool who someone is, and record ownership uses that identity to show each person their own data.
Sandboxed and separate by design
Every published tool runs inside its own sandbox. It can read and write its own shared database, and nothing else. A published tool cannot reach into another tool, another account, or another person's session, and it cannot pull data from anywhere it was not given. Each tool is walled off from the rest.
This is why sharing a link is safe. The people you invite get access to that one tool and the data it is meant to hold, and the sandbox makes sure the tool cannot wander beyond its own walls.
A quick recap
- Publishing gives you a live link to the real working tool, and you can unpublish or keep editing at any time.
- Your team shares one live database, so changes show up for everyone.
- Owner, member, and viewer roles are enforced on the server, not just in the interface.
- With record ownership on, each teammate sees only their own records.
- Sign-in gating decides who gets in, and every tool is sandboxed so it cannot reach other sessions.
Questions
Need a hand with publishing or access? Reach us at hello@nyvloai.com.