Application Settings
Overview
The Settings page provides centralized management for your organization's configuration, user access, and integrations. Access the Settings page from the left navigation bar in the Fiddler UI.
Settings Tabs
The Settings page is organized into the following tabs:
General - Organization information and user details
Access - User and team management
Credentials - Personal access token management
Email Configuration - Email notification settings
PagerDuty Integration - PagerDuty alert configuration
Webhook Integration - Webhook service management
General
The General tab displays your organization's configuration and current user information.
Organization Information
Organization Name - Your organization's display name in Fiddler
Organization ID - Unique identifier for your organization
Version - Current Fiddler platform version
User Information
User Name - Your display name in the system
Email - Email address associated with your account
Access
The Access tab provides centralized management for users and teams within your organization.
Users
The Users sub-tab displays all users who are members of your organization.
This view shows:
User names and email addresses
Organization roles (Org Admin or Org Member)
Account status (Active/Inactive)
Last login information
Note
User invitations are managed through the Fiddler AuthN console:
Email authentication users must be invited by AuthN Org Owners or Org User Managers
SSO users are automatically created upon first login to Fiddler
Teams
The Teams sub-tab displays all teams defined within your organization. Teams provide a way to organize users and manage project-level access controls.
Creating Teams
Create a new team by clicking the plus (+) icon in the top-right corner.
Important
Only users with the Org Admin role can create teams. The plus (
+) icon will not be visible for Org Members.
When creating a team:
Enter a unique team name
Team names may not include spaces, but mixed case alphanumeric characters are valid
Add team members from existing users
Assign appropriate project permissions
Click Create to save the team
Team Synchronization
If your organization uses SSO with group synchronization enabled, teams can be automatically created and managed based on your identity provider groups. See Mapping Identity Provider Groups to Fiddler Teams for configuration details.
Credentials
The Credentials tab manages personal access tokens used for programmatic access to Fiddler through the Fiddler Python client, Fiddler SDKs and REST APIs.
Creating Personal Access Tokens
Both Org Admins and Org Members can create personal access tokens:
Click Create Key to generate a new token
Once you have a token, the Create Key will be removed
To generate a new token, delete your current token and the Create Key will return
Use the token for authentication in the Fiddler Python client, Fiddler SDKs, and REST APIs`
Token Management
Each user can create multiple personal access tokens
Tokens should be rotated regularly for security
Revoke unused or compromised tokens immediately
Personal access tokens inherit the permissions of the user who created them
Security Best Practice
Treat personal access tokens like passwords. Never share them or commit them to version control systems.
Email Configuration
The Email Configuration tab manages the email provider for your organization.
Configure:
Selecting SES or SMTP for email delivery
Fiddler Cloud customers leverage AWS SES
You may choose to use your own SMPT server by entering your own SMTP connection and credentail details
PagerDuty Integration
The PagerDuty Integration tab enables configuration of PagerDuty services for alert escalation.
Setup includes:
PagerDuty service integration keys
Severity mapping for alerts
Escalation policy configuration
Test alert functionality
Webhook Integration
The Webhook Integration tab manages webhook configurations for connecting Fiddler alerts to your notification and communication platforms.
Supported Webhook Types
Fiddler supports three webhook provider types:
Slack - Direct integration with Slack channels
Microsoft Teams - Native Teams channel integration
Other - Custom webhook endpoints for any platform
Creating a Webhook
Click the plus (+) icon to configure a new webhook:
Slack Webhook Configuration
Enter a unique name in the Service Name field
Select Slack from the Provider dropdown
Enter your Slack webhook URL (format:
https://hooks.slack.com/services/...)Click Test to verify the connection
Click Create once the test succeeds
Reference
See Slack's webhook documentation for creating webhook URLs.
Microsoft Teams Webhook Configuration
Enter a unique name in the Service Name field
Select MS Teams from the Provider dropdown
Enter your Teams webhook URL provided by your administrator
Click Test to verify the connection
Click Create once the test succeeds
Reference
See Microsoft Teams webhook documentation for setup instructions.
Custom Webhook Configuration
Enter a unique name in the Service Name field
Select Other from the Provider dropdown
Enter your platform's webhook URL
Click Test to verify the endpoint
Click Create once the test succeeds
Managing Webhooks
Edit or delete existing webhooks using the menu (...) icon for each webhook:
Select the webhook's menu icon
Choose Edit Webhook to modify configuration
Choose Delete Webhook to remove the webhook
Important
You cannot delete webhooks that are currently linked to active alerts. Remove the webhook from all alerts before deletion.
Access Requirements
Different settings require specific permissions:
View General tab
✓
✓
View Access > Users
✓
✓
View Access > Teams
✓
✓
Create/Edit Teams
✓
✗
Create Personal Access Tokens
✓
✓
Configure Email Settings
✓
✗
Configure PagerDuty
✓
✗
Create/Edit Webhooks
✓
✗
Related Documentation
Role-Based Access Control - Understanding user roles and permissions
Single Sign-On Configuration - Setting up SSO authentication
Inviting Users - Adding users through the AuthN console
Alert Configuration - Using webhooks and integrations for alerts
❓ Questions? Talk to a product expert or request a demo.
💡 Need help? Contact us at [email protected].
Last updated
Was this helpful?