Settings
Manage Application name, description, configuration locations, and deletion.
General Settings manages basic information, access summary, and lifecycle actions for one Application.
Most editor setup is managed on dedicated pages. Use General Settings for Application identity, status, and high-risk actions.
Application information
| Field | Description |
|---|---|
| Application Name | Display name shown in the Application switcher and Applications list. |
| Application ID | Unique identifier for the Application. Used with API authentication. |
| Description | Internal note for your team. |
| Website | Optional product or customer website associated with the Application. |
| Environment | Optional label, such as production, staging, or development. |
Changing the Application name does not change the Application ID, API keys, End Users, credits, or usage records.
Access summary
General Settings can show which teammates have access to the Application.
Application access is managed from:
Platform Console -> TeammatesOwners and Admins can access all Applications. Teammates can access only assigned Applications.
Pause or resume an Application
If Application pause is available, pausing an Application can temporarily stop End User access without deleting configuration.
Before pausing an Application, confirm the impact on:
- Editor launch flows.
- API calls.
- Active End User sessions.
- Production users.
Resume the Application when you are ready to allow access again.
Delete an Application
Deleting an Application is permanent.
It can remove:
- API keys
- Push URL configuration
- Embed settings
- Appearance settings
- Domain settings
- Editor controls
- End User mappings
- Credit allocations
- Usage records
- Email records
To delete an Application, follow the confirmation flow and enter the required Application name if prompted.
Warning: Do not delete a production Application unless you have already migrated or stopped all dependent integrations.
Updated 6 days ago