Getting Started

What is Vince Live – App Builder

App Builder is a capability in Vince Live that helps you create simple business applications using plain-language instructions and the data you already have in Vince, such as workflows and tables. It is designed for users who understand the business process and want to quickly build useful apps such as dashboards, trackers, lists, operational tools, and small process-focused applications without building the frontend manually. App Builder works best when the underlying data and workflows are already meaningful and well structured, because the app is generated based on those resources.

Table of contents:

1. Who should use it (Personas & roles)
2. Key concepts 
   • App
   • Workflow
   • Table
   • Resource
   • Alias
   • Build session
   • Preview
   • Save
   • Publish
   • Version
   • InApp Roles
   • Environments
   • Tenant Prompt
3. Before you start
4. Video walkthrough
5. QuickStartstart: Build your first app
6. Using your tenant prompt
   • Why use it
   • How to use it
   • What you can put in the tenant prompt
   • Examples

Who should use it (Personas & roles)

• Business users who want to create simple apps without coding
• Power users who understand workflows, tables, and business processes
• App owners / administrators who manage app versions, publishing, and access
• Domain users in supply chain and operations who want to turn process knowledge into practical apps such as dashboards, trackers, and portals

Key concepts (Apps, Workflows, Tables, Roles, Environments)

App

An app is the business application you create in App Builder. It is the screen or experience that end users will use, such as a dashboard, tracker, list, portal, or operational tool.

Workflow

A workflow is a process in Vince that gets, sends, transforms, or combines data. App Builder can use workflows as resources when building an app. In simple terms, the workflow does the business-side work, and the app gives users a friendly way to view or use the result.

Table

A table is a structured data source in Vince. App Builder can use tables directly to build apps such as dashboards, search views, lists, or status trackers. Tables are often the easiest starting point because the structure is already clear.

Resource

A resource is any workflow or table that you connect to the app. These resources are the foundation of the app, because they provide the data and business context App Builder works with.

Alias

An alias is a simpler name you give to a resource so it is easier to refer to in prompts. For example, instead of using a long technical name, you can use a business-friendly name like "Invoice Table" or "Supplier Orders".

Build session

A build session is the period where you are actively creating or changing an app. During that session, you prompt App Builder, review the preview, and refine the app step by step until you are ready to save.

Preview

Preview shows the current in-progress version of the app before you save or publish it. It helps you check whether the app is moving in the right direction.

Save

Save stores the changes you accept into the version you are working on. This is how you keep the progress you want.

Publish

Publish makes one version of the app available for end users. Only one version is published at a time, so publishing is the step that turns your draft into the live version people use.

Version

A version is a saved stage of your app. You can create a new version to continue improving the app without changing the currently published version until you are ready.

InApp Roles

InApp Roles are a feature inside the App Builder editor. They let you define app-specific roles (for example "supplier" or "approver") and control what those users can see or do once the app is running. This is different from your Vince Platform role, which controls whether you can use App Builder itself. See Building Apps (UI) for how to set them up.

Environments

Environments are the separate setups (typically dev, test, and production) where your apps run. Each one is configured by your administrator. See Concepts & Architecture for more detail.

Tenant Prompt

The tenant prompt is your organization's standing instructions to App Builder. It applies to every app built in your tenant — things like brand colors, logo, theme, and any rules you want every app to follow automatically. See Using your tenant prompt below.

Before you start

You'll need:

• A Vince Live account with App Builder access. If you don't have it yet, contact support to set it up.
• At least one workflow or table available as a resource. If you don't have one yet, see Workflows or Tables.

▶ Video walkthrough

Quickstart: Build your first app

1. Open App Builder. You'll see the App Library — the list of all apps on your tenant.
2. Create a new app. Give it a name, a short description, and pick the LLM connection.
3. Add your resources. Pick the workflow or table your app will use, and give each one a clear alias.
4. (Optional) Inspect the schema. Looking at the fields ahead of time helps you write better prompts.
5. Write your first prompt. Describe what you want in plain language — keep the first one simple.
6. Wait for the preview. The chat is locked while App Builder generates your app.
7. Iterate. Look at the preview and refine with follow-up prompts if needed.
8. Save. Lock in your progress and end the build session.
9. Publish. Promote your version so end users can run it.
10. Run. Open the app from the App Library or share its link.

Using your tenant prompt

The tenant prompt is your organization's set of standing instructions to App Builder — brand colors, logo, theme, and any conventions you want every app to follow without having to repeat them in every prompt.

Why use it

• Consistency. Every app built in your tenant picks up your visual identity automatically — same colors, same logo, same look and feel.
• Less repetition. You don't have to write "use our brand color, use our logo" in every prompt.
• Easier handoff. Apps built by different people in your organization still feel like they belong together.

How to use it

Your tenant prompt is configured by your tenant administrator. Once it's set, it applies automatically to every app you build — you don't need to do anything in your individual prompts.

What you can put in the tenant prompt:

• Brand — primary and secondary colors, fonts, logo URL, header banner
• Theme — light or dark preference, button styles, spacing conventions
• Naming conventions — how dates should be formatted, how to label common actions
• Standard sections or footers — anything you want included on every app

Examples

Brand and theme

"Use our brand colors (primary #1A73E8, secondary #34A853). Place the company logo at the top-left of every app. Use a clean, professional theme with a light background."

Formatting conventions

"Always format dates as DD/MM/YYYY. Show all quantities with two decimal places. Use 'kg' for weight and 'pcs' for piece counts by default. Display item numbers in the format ITEM-XXXX."

Standard behaviors

"Every app should include a footer with our support email (support@vince.no). Always show a confirmation dialog before any delete or send action. Label primary actions as 'Save' (not 'Submit') and 'Cancel' (not 'Close')."

Domain language

"This is a supply-chain tenant. Use 'warehouse' instead of 'location' where it applies. Group items under their region. When showing suppliers, always include the supplier code in parentheses next to the name."

Talk to your tenant administrator if you want to update or extend the tenant prompt for your organization.