Overview
Once you have built an app by asking your AI assistant, three things decide who sees it and who can change it: a release, a list of maintainers, and - if you run more than one tenant - a share.
Every change you make lands as a draft. Your colleagues keep seeing the last released version until you release the new one deliberately, so an unfinished edit never reaches them.
Where to find it
Open /apps on your tenant to reach the App directory. It lists every app available to you, with a details page for each, the most-used and trending charts, and a What’s new section built from release notes.
Apps you receive from another tenant carry a shared label in the list and a note on their details page.
Prerequisites
Your AI assistant is connected to Luminovo. See Connect your AI assistant to Luminovo with the MCP.
You are a member of the tenant the app belongs to.
For anything that changes an app, you are one of its maintainers. Building an app makes you its first maintainer.
Step-by-step guide
Preview a draft and release it
Ask your assistant to make the change. It lands as a draft.
Preview it by adding ?lumi_draft=true to your app’s URL. Only you see the draft version.
When you are happy with it, ask your assistant to release the app, and give it release notes. The release reaches everyone in the tenant, and the notes appear under What’s new in the App directory.
To undo a release, release an earlier version again.
See who maintains an app
Ask your assistant which apps you maintain. If you try to change an app you do not maintain, the refusal names the people who do, so you know whom to ask.
An app’s creator is its first maintainer, and maintainers can add others. For apps that existed before this rule, the creator became the sole maintainer — so an app a colleague built is closed to you until they add you.
Share an app into another tenant
Ask your assistant to share the app into the tenant you have in mind. You need to be a member of both tenants. You can name several tenants at once, and each one gets its own result, so one refusal leaves the rest unaffected.
The receiving tenant opens the app at its own address and always gets your current release. Ship a new release and every tenant that receives the app has it straight away.
Ask your assistant to unshare it to undo this, from either side.
Let one app work across several tenants
Sharing gives each tenant its own copy of an app. This is different: one app reads and writes across several tenants at once, so a single page can show every site and a button can move work between them. It suits customers who run one Luminovo tenant per site or country.
The app keeps a home tenant, where it is created and lives, and reaches the others from there.
Ask your assistant to build or extend the app and name the tenants it should reach, for example your German, Chinese and Mexican sites. The assistant declares those tenants in the app.
Get the pairing approved. Every app-and-tenant pairing is approved by Luminovo once; until then that tenant is simply off for the app. Anyone with a Luminovo email address can approve it, so you can ask your assistant to approve it or ask a colleague.
Run the app. At run time it checks which of its tenants it can reach right now and skips the rest, telling you why.
Every call runs as the person who pressed the button, with their own permissions and roles in each tenant, and is audited there. A colleague who cannot access a tenant sees nothing from it. Workflows and app backends get the same reach.
What everyone can do
Maintainers control changes only. Everyone else in your tenant can still open the app, run its workflows, and read its description exactly as before.
On the receiving side of a share, people can use the app and stop receiving it. Changing it, reading its code and passing it on stay with the owning tenant.
Good to know
An app runs with the permissions and integrations of whoever opens it, so a shared app shows the receiving tenant’s own data.
An app declares every endpoint and external service it uses, and a call it has not declared fails. If a working app starts failing after an edit, that declaration is worth checking first.
Luminovo staff have no way around the maintainer rule, on the internal connection either.
If the only maintainer of an app has left your company, contact us and we will reopen it.
Getting help
Email us at [email protected], or use the chat button in the bottom-right corner of your workspace.