Publish and use

The app is built. The last stage is left — and it is the one that changes the nature of what you made: up to here the Customer Management app was a project inside the platform; from here on it is an application with its own address, its own accounts and users who have never heard of Keplin.

Four steps: version, address, who can do what, accounts.

#Versions — what gets published

While you build, you always work on a working version. A version is a complete portrait of the app: screens, model, APIs, scripts, theme — and its data.

1. At the top of the app's bar, click the Versions selector.
2. Click New version….
3. Give it a name — 1.0, for example — and choose in From the version of origin.
4. Confirm. "Version “1.0” created — you are now working on it."

With versions, the working pattern becomes clear: main is where you develop, 1.0 is what is live, and the Selective merge brings into the published version only the changes that are already ready.

#Publishing at an address

1. Open the App settings (the gear icon at the top of the bar).
2. In the Application group, choose General.
3. Scroll down to the Publishing section.

The rule is written right there: "Each host serves ONE version of this app (DNS is handled separately). With none, the app only answers at /app/gestao-clientes, with the working version."

4. In the host field, type the address — for example crm.aminhaempresa.pt.
5. In the selector next to it, choose the version that address is going to serve.
6. Click Publish. "Host published."

What this means, in practice:

Situation	Where the app answers	Which version it serves
No hosts published	/app/gestao-clientes	The working version
With one host	That address	The version you tied to it
With two hosts	Both	Each its own — that is how you have a stable crm.empresa.pt and a crm-testes.empresa.pt with the next version

#Who can do what — the roles

Before creating accounts, decide what each kind of person can do. That is done in roles, and not person by person.

1. In the App settings, Users group, choose Permissions.
2. Click New role and give it a name. For our CRM, three are enough.

Role	Description	For whom
equipa	Sales team — full access to the CRM's data	Whoever works the accounts every day. It is the role given by default.
direcao	Management — approves the opportunities above €25,000	Whoever decides.
leitura	Read-only — sees the CRM without being able to change it	Whoever only needs to look.

Inside a role, the work is split across five tabs:

Tab	What it decides
General	Name, description, Full access and Given by default (assigned to whoever is newly created).
Data	For each table API, what is allowed — View, Create, Change, Delete — and the Scope: All records, Only mine or With condition….
Screens	Per screen and per device: Hidden, View (read-only) or Edit.
Menus	What gets hidden from the navigation. Unlike screens, a menu is visible by default.
Actions	The verbs that only exist in this app — aprovar-oportunidade, for example. They are declared here and demanded on the widgets.

For the equipa role, the minimum that makes the CRM work:

1. On the Data tab, check View, Create, Change and Delete on the three APIs (contas, contactos, oportunidades), with the scope All records.
2. On the Screens tab, set the four screens to Edit, on all three devices.
3. On the General tab, turn on Given by default.
4. Save — "Permissions saved."

For the leitura role, the same with one difference: only View on the data, and the screens at View (read-only).

#The accounts of the people who use the app

Here comes the part that separates Keplin's two populations. These accounts are not platform accounts:

1. In the App settings, Users group, choose App users. The notice at the top says it all: "These users belong to the built app — they log in to the app at runtime and have no access whatsoever to the KEPLIN platform."

2. Click New user. The form opens as a page.

3. Fill in:

Field	What to put
Username	Required — letters, numbers, dot, hyphen, _ and @. E.g. bruno.dias.
Name	The person's name; it is what appears in the user menu inside the app.
Email	Optional, but needed for password recovery.
Password	The initial password — "the user can change it in the app".
Active	On. Off, the account exists but cannot get in.
Roles	The person's roles. A new account comes with the roles that are given by default pre-checked.

4. Save — "User created."

Repeat for the whole team. When there are many people, the list works for you: select several accounts and use Grant role, Revoke role, Enable or Disable in one go.

#Entering the app

Everything is in place. Open the published address — or /app/gestao-clientes, if you have not published any host yet — in a normal browser window.

What appears is the Login screen: the Username and Password fields, the Sign in button and the Forgot my password link. It is one of the app's System screens — it comes ready-made and painted with the theme you chose in the previous stage.

Sign in with one of the accounts you created. The app opens on the Initial menu you defined: the dashboard, with the indicators computed over the real data, the menu with your logo and your brand's colors.

Walk through what you built, from the point of view of whoever is going to use this every day:

1. Início — the four indicators, the pipeline chart and the upcoming closes table.
2. Contas — the list; click a row and you land on that account's form, with its contacts alongside.
3. Change a field and click Save — the notice appears and you return to the list, with the change already in it.
4. Click Nova conta — the same form, now blank. Fill it in and save: the record is created.
5. Oportunidades — drag a card from Proposta to Negociação. The stage is saved on the spot; go back to Início and the chart has already changed.

#The guide is over. Now what?

You have a working business application, built end to end. From here, each piece has a chapter that goes far deeper than this guide could:

If you want…	Go to
Richer screens — more widgets, events, layouts per device	Screen builder
Connecting the app to databases that already exist	Datasources
Exposing the data to outside systems	APIs & GraphQL and API keys
More automation — dependencies, files, the full SDK	Scripts
Fine-tuning everything that is the app's — notifications, storage, retention	App settings
Taking this app to another installation	Import and export

#Why doesn't…?

• Why doesn't my address open the app? The host is registered on the platform, but that address's DNS has to point at the server. Until that is done, use /app/gestao-clientes.
• Why does the address serve the wrong version? Each host serves ONE version, chosen at the moment of publishing. Unpublish and publish again with the right version.
• Why does the user sign in and see nothing? They have no role, or their role has no Data rules. Confirm on the list of users (the amber warning) and then on the role's Data tab.
• Why does the user see the menu but the screen says they have no access? The screen is Hidden for their role, on the Screens tab — and per device: it can be open on web and hidden on the phone.
• Why don't the data I created while testing appear on the published version? Because versions do not share data. You created them on the working version; the host is serving another.
• Why won't my platform account sign in to the app? Because they are different populations. To enter the app you need an App users account, even if you are the one who built it.