Ask visitors to sign in
How to turn a public portal into one that only people with an account can open, and what each of them then sees.
How to turn a public portal into one that only people with an account can open, and what each of them then sees.
A walkthrough from an empty environment to a working app — a table, a screen, a list that came from it, a toolbar and a drawer that writes a record back.
How a maker creates a Studio app, and what one is for.
How a maker draws a screen on the canvas, and what saying what each object is buys you.
How to make your portal's sign-in, sign-up and forgotten-password pages screens you drew, and keep a landing page open to everyone.
How a file somebody picks on a portal screen reaches a record's File column, through the same Custom API everything else goes through.
How a visitor starts a company on your portal, invites colleagues into it, changes what they may do, and leaves — from buttons you draw.
How a portal screen creates, changes and deletes records, and what you have to write for it to be safe.
How a visitor sets up an authenticator app on your portal — one button you draw, and a panel the platform draws behind it.
Give a screen its own state, drive what it says and shows with expressions, and let a control write back to what it reads.
How a drawn screen gets into an app's navigation, and how to make it the first thing people see.
How a maker publishes a drawn app to a web address of its own, for people outside the organisation.
Counted tiles, charts, and a model-driven grid or quick form embedded in a Studio screen.
The My tasks control — the reader's own inbox as a panel on a drawn Studio screen, so an app can open on the day's work.
Make a component once, drop it anywhere, give it states, and let it follow the theme.
A drawn app in the Shell's app list, with no model-driven app around it — and how its screens are addressed.
Paging, a page-size picker and a search box on a drawn screen — one query, and what a Next button has to know.
How to put the platform's own grid on a portal page, and let a view decide its columns.
Draw a component once, place it in as many apps as you like, and change it in one place.