Book a demo Start free

Product

Product overview Agents Automations Apps Code (Beta) Integrations Governed Runtime Security

Where Renly runs

Windows app Android app Inside other AI apps

Solutions

Finance Sales Operations People and HR Marketing Enterprise

Resources

Pricing Docs Academy Blog Compare Support

AI governance and capability

AI governance framework AI governance assessment AI capability maturity AI maturity assessment
Book a demo Sign in
Docs / Renly Apps / Administration

Administration

Organisation owners and admins manage every app from one place: Organisation settings > Governance > Apps. The section has four parts: the Apps inventory, SQL connections, API keys and Webhooks. Every action here is audited.

The Apps inventory

Every app in the organisation, with its owner, workspace, status (active or paused), live version, last publish, number of write rules, pending requests and writes in the last 30 days. Search by app, owner or workspace. Open app lands in the app's own workspace.

ActionWhat it does
Pause appReads continue. Every write path for that app is refused with This app is paused by an administrator.: pages, agents, the REST API, imports and triggers. Held requests stay open. Resume lifts it.
Change ownerApps belong to the organisation, not to the person who built them. When someone leaves, give their apps a new owner; synced sources then need the new owner's consent.
Export definitionDownloads the app's definition as JSON: types, interfaces, views, roles, write rules, data sources and custom blocks. No data and no secrets.

Importing a definition

A definition exported from one organisation can be imported into another through the Apps API (POST /api/organizations/<orgId>/apps/import, up to 2 MB), by an organisation admin or by a maker of any app, who becomes the new app's maker. The import creates a new app whose draft is the definition; nothing goes live until it is published. Automation ids, SQL connection ids and people named as approvers are cleared with warnings, live and synced sources keep their settings with a warning to check them, and record type ids already taken are renamed. Plan caps apply. In this release import is available through the API; export is in the inventory.

SQL connections

The connections apps may read from, with their allowed tables and views. Details in Data, access and sources.

API keys and webhooks

Create, rotate and revoke the keys that read and write records, and manage the webhooks that announce changes, with their delivery history. Secrets appear only once. Details in API and webhooks.

Plan caps

  • Pro Plus: 10 apps and 100,000 records per organisation. Enterprise: unlimited.
  • Publishing or rolling back a version that adds record types past the cap is refused with a clear message. Versions that keep or remove types are never refused for that reason.
  • On Free and Pro, the Apps home shows an upgrade card and the templates gallery to browse.

Agents and the kill switch

  • Pause all agents stops agents and automations from writing to apps. A held request raised by an agent stays open until they resume.
  • The App assistant is listed in the Agents admin with its own autonomy level and action rules. Set it to Analyse only, or say never to running actions, without affecting the Records Manager that builds apps.
  • Agents' writes, API writes, decisions and administrative actions appear in the organisation's audit log (Pro Plus and Enterprise) with entries such as apps.action.run, apps.api.record.created, apps.app.exported, apps.api_key.* and apps.webhook.*.

Space and chat

Space lists apps next to pages, Sites, images and files; opening one goes to the app. The approval cards and record cards agents show in chat and in Teams link back to the app and its requests.

← Apps in TeamsNext: Limits and FAQ →