> This page is for The Console. > For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://infonite.dev/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://infonite.dev/_mcp/server. # App settings [*App Settings*](https://www.infonite.tech/console/app-settings/) is where an application is configured, and it is the screen the Console opens on. Five sections down the left; the one you are reading about here is **General**. ![The App Settings screen of the Console: the five sections down the left — General Settings, Security & Keys, Capabilities with a badge, Webhooks and Layout & Aesthetics — and the General section showing the application details, the frozen public name with the widget preview, the redirect URLs and the danger zone](/_fern-files/_img/625960bbfba5b10c6c9f1f4dd28ef6964685234c3a18b54c362a758f33af4a5b.webp)![The App Settings screen of the Console: the five sections down the left — General Settings, Security & Keys, Capabilities with a badge, Webhooks and Layout & Aesthetics — and the General section showing the application details, the frozen public name with the widget preview, the redirect URLs and the danger zone](/_fern-files/_img/8cd873c2302164715d1600db7aeef4c0b426084e987bd4f848c36a880802c529.webp) #### General Names, website and contact, the redirect URLs, the move to production and the danger zone. **This page.** #### [Security & Keys](/console/security-and-keys) The application secret your backend signs in with, and the optional encryption pair. #### [Capabilities](/console/capabilities) What the application may do, how far each thing reaches, and how to ask for more. #### [Webhooks](/console/webhooks) The endpoints we deliver to, the rules that decide what goes where, and the test delivery. **Layout & Aesthetics**, the fifth, is how the widget looks to your end users — colours, logos, the shape of things. It is the section that [freezes when you ask for production](/console/your-first-app#step-1--what-gets-protected). > **Tip** > > Every section carries its own **guided tour** — the book icon in the toolbar replays it — and its own **docs pill**, which opens the page of this documentation that covers it. --- ## Application details ![The Application Details card open for editing: the internal app name, the read-only Application ID with its copy button, the website URL and the contact email, with the frozen public display name below](/_fern-files/_img/607e2e020652fc19061d884ccdd96e3db15e8e5a2d3cd73a95f05311cb1e4450.webp)![The Application Details card open for editing: the internal app name, the read-only Application ID with its copy button, the website URL and the contact email, with the frozen public display name below](/_fern-files/_img/6151ed09606c2745cae158c387a76bdfbd0dff933efc320d788d4ac08c49ca77.webp) The pencil opens the card; **Save** and **Cancel** appear at its foot. | Field | What it is | | ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | | **App name (internal)** | A private label, only your Console shows it. Rename it whenever you like. | | **Application ID** | Not editable: it *is* the application. Your backend sends it on every call and support will ask you for it — hence the copy button. | | **Website URL** | Where your service lives. For us, not for your end users. | | **Contact email** | The mailbox we write to about this application. | | **Actual display name** | The public name, below the fields and deliberately not among them. | > **Note** > > **Why the public name cannot be edited here.** It is what your end users read on the consent screen, and they recognise your service by that exact string — the phone preview beside it shows the sentence they actually see. Changing it is a decision with a reader on the other side, so it goes through us: write to `support@infonite.tech`. --- ## Redirect URLs Where the widget is allowed to send someone back to when they are done. **A URL that is not on this list is not a destination** — that is the whole point of the list, and it is what stops a redirect being pointed somewhere it should not go. > **Note** > > **These are not webhook endpoints, and the two are often confused.** A redirect moves your customer's *browser* when they finish in the widget; it carries no data and does not happen if they close the tab. A [webhook](/console/webhooks) is a call from our servers to yours when the event fires. They are configured on different sections for that reason — [the difference, drawn](/guides/webhooks#synchronous-and-asynchronous). ![The Redirect URLs card open for editing, with two URLs listed, a delete button beside each and the Add URL button below](/_fern-files/_img/f44745f75bf0d9afcd3189cd1b14d077d6c8c657459e728c993c7be1f4a672dc.webp)![The Redirect URLs card open for editing, with two URLs listed, a delete button beside each and the Add URL button below](/_fern-files/_img/7efdfa0bac22f1de5c814c98ab36bd41bb41d5415784611859e91c8d7e3dd4e3.webp) > **Warning** > > **Query parameters are stripped.** Only the base URL and the path are stored, so `…/done?case=A-1029` is kept as `…/done`. Anything you need to carry back is added when you start the session, not here — the flows' own guide covers that in [redirects](/flows/spain-public-administration/redirects). A new application starts with one entry already on the list, `https://infonite.dev/`, so a first test session has somewhere to end before you have configured anything. It is an ordinary entry: remove it whenever you like, and it does not come back. Up to ten per application, added and removed one at a time. The change takes effect as soon as you save — and if saving is the part that does not work, it is worth ruling out [a network policy on your own machine](/console/network-policies) before anything else. --- ## The danger zone ![The danger zone at the foot of the General section: Delete application, with the warning that there is no going back](/_fern-files/_img/b3b3bec5ef9ff99f6dfc86fec9034830c4520a28688b293898df35d51d0d9b69.webp)![The danger zone at the foot of the General section: Delete application, with the warning that there is no going back](/_fern-files/_img/a7a85c163520f51abd6b93c7e9614ee227f0c0843ef8064890dd66def6992326.webp) **Deleting an application cannot be undone**, and it is not a way to pause one. Everything recorded under it goes with it: its secrets, its keys, its webhook endpoints and rules, its executions and sessions, and the credentials it tokenized. Nothing is recoverable afterwards, by you or by us. If what you want is for an application to stop running while keeping everything it has, that is a **lock**, not a deletion — write to `support@infonite.tech`. A locked application stops running and its settings become read-only in the Console; its data and its configuration stay exactly where they are ([what locked means](/console/organizations-and-applications#the-applications)). --- ## Next #### [Your first application](/console/your-first-app) Creating one, what it can do in sandbox, and asking us for production. #### [Capabilities](/console/capabilities) What this application may do, and how to ask for the rest.