Settings
The application Settings view contains configuration and administrative controls. The sections available to you depend on your role, plan, and enabled features.
Information and data collection
Use Information to review the application identity, SDK connection details, and whether data collection is enabled. Disabling collection stops Bugfender from accepting new logs, crashes, issues, and feedback for the application.
The application key connects an SDK to this application. The symbolication token authorizes symbol uploads. Administrators can regenerate the symbolication token; the previous token then stops working and must be replaced in every build or release integration that uses it.
Treat application keys, symbol-upload tokens, storage connection strings, and webhook URLs as credentials. Store them in secret storage, do not publish them in repositories or support tickets, and redact them from screenshots.
Customize device names
Open Device Name to control how installations are named throughout the dashboard.
You can build a format from literal text and fields such as:
- device model, model name, or model ID;
- the name reported by the SDK;
- device UID, OS, OS version, or language;
- application version or build;
- available custom device data.
Use the preview to check the result. Missing fields are omitted, and an empty result falls back to Unknown. The default format uses the device model.
Enable Hide device names to store and display device names as Unknown for privacy. Review the effect on support workflows before enabling it, especially if teammates currently search by an SDK-provided device name.
Endpoint normalization
When Network Endpoint Normalization is enabled, developers can create, edit, enable, delete, and reorder rules. Viewers with application access can inspect the configuration without changing it.
See Network endpoint normalization for templates, regular expressions, suggestions, priority, previews, and testing.
Application members
On plans with fine-grained permissions, administrators can grant selected members access to this application without giving them access to every application in the team. App-level administrators, developers, and viewers receive different management rights as described in Members and Access.
An app-only member can leave the application from this section. Team-wide access must be changed from Team Settings instead.
Integrations
Only application administrators can manage integrations. The available integrations depend on the plan.
GitHub
Connect a Bugfender account to GitHub and select a repository to create GitHub issues from Bugfender issues and crashes. One of the connected GitHub account's email addresses must match the Bugfender account email.
Review the selected repository and GitHub App permissions before enabling the integration. You can unlink the repository, adjust GitHub App permissions, or disconnect the GitHub account later.
Log archiving
Pro plans can archive logs to external object storage:
- Amazon S3 uses an access key, secret key, bucket, and optional region. Bugfender may offer discovered configuration suggestions.
- Microsoft Azure Blob Storage uses a storage connection string, container, and optional blob prefix.
Disabling an archive integration stops future archiving to that destination. Manage retention and access controls at the storage provider as well as in Bugfender.
Webhooks
Pro plans can send webhooks for New Crash, New Issue, New App, and New User Feedback events. Add a target URL and select one or more events. Existing webhooks can be edited or removed.
Protect the target URL and ensure the receiving service authenticates and safely processes incoming data.
Data protection
Privacy controls can list blocked devices and provide actions for restricting or deleting collected data. Coordinate these actions with your organization's privacy and retention processes.
Danger zone
The danger zone contains application-wide actions.
Change team
An administrator can move an application to another team. An application can be moved to a different team once every 24 hours. During that cooldown, it can still be returned to its original team.
Before moving it, verify member access, plan limits, billing ownership, integrations, and the destination team's data-handling requirements.
Delete the application
Deleting an application and its data is irreversible. Verify the selected application, required exports or archives, and organizational approval before confirming deletion.