Basestack Docs
User Guide

General Settings

General Settings control the core behavior of your form, including its name, status, data retention, spam protection, and webhook configuration.

Accessing General Settings

Navigate to any form, click "Settings" in the navigation menu, then select "General". You'll see all general settings organized in cards.

Some settings require specific permissions. Contact the form owner if you don't see certain options.

Form Name

Change your form's display name at any time. This name appears:

  • In the dashboard form list
  • In navigation menus
  • In email notifications
  • In submission exports

Use descriptive names that clearly indicate the form's purpose. This helps team members identify forms quickly.

Form Owner

View the form owner's information. The owner has full control over the form and can:

  • Delete the form
  • Manage team members
  • Change all settings

Form ownership cannot be transferred through the UI. Contact support if you need to transfer ownership.

Form Endpoint & Key

View your form's endpoint URL and API key. These are essential for integration:

  • Endpoint: The URL where form submissions are sent
  • Key: Your form's unique identifier

Enable/Disable Form

Control whether your form accepts new submissions:

  • Enabled: Form accepts and processes submissions
  • Disabled: Form rejects all submission attempts

When disabled, all submission attempts will fail. Use this to temporarily stop accepting submissions without deleting the form.

Data Retention

Control whether submissions are stored in your dashboard:

  • Enabled: Submissions are stored and visible in the dashboard
  • Disabled: Submissions are processed but not stored

Data retention must be enabled for submissions to appear in your dashboard. This setting works in conjunction with spam protection and webhooks.

If data retention is disabled, you won't be able to view submissions in the dashboard, even if they were successfully processed.

Spam Protection

Enable AI-powered spam detection:

  • Enabled: Submissions are automatically analyzed for spam
  • Disabled: All submissions are accepted without spam filtering

Spam protection requires data retention to be enabled. Spam submissions are marked but not deleted, allowing you to review false positives.

Spam protection uses AI models to detect spam. While highly effective, some spam may still get through. Use additional security measures like IP blocking for better protection.

Webhook URL

Configure a webhook to receive real-time notifications when submissions are received:

  • Webhook URL: The endpoint where submission data will be sent
  • Format: JSON payload with all submission data

Webhooks are only triggered when the form is enabled. The webhook receives a POST request with the submission data in JSON format.

Use webhooks to integrate with external systems, trigger automated workflows, or send custom notifications.

Deleting a Form

Permanently delete a form and all its data:

  • Warning: This action cannot be undone
  • Impact: All submissions, settings, and team members will be permanently removed

Deleting a form is permanent and irreversible. Make sure you have exported any important data before deleting.

Settings Dependencies

Some settings depend on others:

  • Spam Protection requires Data Retention to be enabled
  • Webhooks only work when the form is Enabled
  • Submissions require both Enabled and Data Retention to be active

The settings interface will show warnings when dependencies aren't met. Follow the prompts to enable required settings.

Best Practices

  1. Enable Data Retention: Keep it enabled unless you have a specific reason to disable it
  2. Use Spam Protection: Enable spam protection to reduce manual filtering
  3. Configure Webhooks: Set up webhooks for real-time integration needs
  4. Regular Review: Periodically review settings to ensure they match your current needs
  5. Backup Data: Export submissions before making significant changes

Next Steps