Renly Apps
An App is something your team works in every day: a request tracker, an asset register, a CRM. It is built on your Records data, has pages people use, roles, write rules that the server enforces, and an audit record for every change. Build one from a prompt, a template or the designer.
Apps replaced Records in the left navigation. Records is still the name for the data: the tables, fields and rows an app is built on. Links to /records open the matching app.
What an App is
One App is one versioned definition. Publishing creates an immutable version of all of it; rolling back re-applies all of it.
| Part | What it holds |
|---|---|
| Data model | Record types, their fields and the links between them. The data lives in Records. Data, access and sources. |
| Interfaces | The pages people use, built from components (table, board, form, detail, metric, chart and more) and declared actions. No code and no expressions. Interfaces and components. |
| Views | Saved tables and boards with filters and sorting, published with the app. |
| Roles and access | Roles with capabilities (read, create, update, delete, export, manage the app, manage access), a row scope of all rows or own rows, and field access per role: hidden, masked or read only. Access. |
| Write rules | Rules that hold a change for approval (one person or two), or refuse it, evaluated on the server for people, agents and API keys alike. Write rules and approvals. |
| Data sources | Records by default. Live Dataverse, Salesforce, SharePoint Lists, Excel tables and read-only SQL, or a sync of one of them into Records. Data sources. |
| Automations and plays | Record-change triggers into Automations, actions that run an automation, and the plays an app recommends. Agents in apps. |
Where you use it
- On the web, at
/apps: the apps you may open, and each app at/apps/<name>with its pages as tabs. Makers also see Data (the Records tables) and Design; everyone with a role sees Approvals for the app's write requests. - On Android and on a phone browser: every page is responsive, in a single column under 768 pixels.
- In Microsoft Teams, as a channel or group chat tab, with approvals as cards in Teams. Apps in Teams.
- In Space, where apps are listed next to pages, Sites, images and files.
- In chat, where agents read and update app data under the same rules, and the App Builder builds apps from a brief.
Who does what
| Who | What they can do |
|---|---|
| Organisation owners and admins | Build an app from a prompt, install a template, manage every app in the Apps inventory, create API keys and webhooks, and approve any held change. |
| Makers | Design, preview and publish the app they manage, give people roles, and approve held changes unless a rule names other approvers. |
| Editors, viewers and the roles a template adds | Use the pages their role is allowed to see, within their row scope and field access. A template such as the request tracker adds roles like Handler and Requester. |
| Agents and API keys | Read and write through the same roles, field access and write rules. An agent's write still needs its own approval card unless its autonomy allows it; a matching rule holds the write anyway. |
Plans
Apps are part of Pro Plus and Enterprise, with the same entitlement as Records.
| Plan | Apps |
|---|---|
| Free and Pro | The Apps home shows an upgrade card and the templates gallery to browse. Templates cannot be installed. |
| Pro Plus | Up to 10 apps and 100,000 records per organisation. Includes the Teams channel tab and approvals in Teams. |
| Enterprise | Unlimited apps and records, plus everything in Pro Plus. |
See pricing for the full plan comparison.
Guides
Build an app
From a template, from a prompt with the App Builder, or in the designer. Preview, publish, roll back.
Interfaces and components
Pages, the fifteen components, queries, tokens and declared actions.
Data, access and sources
Record types, roles, row scope, field access, live and synced sources, SQL connections.
Write rules and approvals
Approval, two-person and deny rules; where requests appear; what the evidence records.
Agents in apps
The App Builder, agents under the write rules, the App assistant, Pause all agents.
Custom blocks
Sandboxed HTML with the window.renly bridge, declared operations and no network.
API and webhooks
Keys and scopes, the REST endpoints, OpenAPI, held writes, signed webhooks.
Apps in Teams
The channel tab and approvals as cards in Teams.
Administration
The inventory, pause, owner, export and import, SQL connections, plan caps.
Limits and FAQ
Every documented limit, and what is not there yet.