> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dify.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Settings

> Configure branding, basic access controls, and user experience settings for your published web applications

Web app settings control how your published applications look and behave for end users. Every Dify application automatically generates a web interface that adapts to different devices and screen sizes.

## How Settings Work

Your web app reflects your application's current configuration. When you modify settings and hit "Publish", changes flow immediately to the live web application that users are accessing.

<Info>
  Web apps work without user accounts or logins by default, making them perfect for public tools and demos.
</Info>

## Branding and Appearance

Make your web app look professional and recognizable:

<CardGroup cols={2}>
  <Card title="App Identity" icon="id-card">
    Set your app name, description, and icon to create a clear first impression
  </Card>

  <Card title="Visual Design" icon="palette">
    Choose colors, themes, and layout options that match your brand
  </Card>

  <Card title="Language Settings" icon="globe">
    Configure interface language for your target audience
  </Card>

  <Card title="Legal Pages" icon="scale">
    Add copyright information and privacy policy links for compliance
  </Card>
</CardGroup>

### Essential Branding Elements

**App Icon and Name**

* Your icon appears in browser tabs and when users bookmark your app
* Choose a clear, recognizable name that explains what your app does
* Icons can be images or emojis—pick what fits your app's personality

**Description and Messaging**

* Write a concise description that helps users understand your app's purpose
* This text appears on the app's landing page and in search results
* Keep it under 160 characters for best results

**Visual Consistency**

* Choose colors that align with your brand
* Consider your audience when selecting light or dark themes
* Test your app on different devices to ensure it looks good everywhere

## Access Controls

<Card title="Advanced Access Management" icon="shield-check" href="/en/use-dify/publish/webapp/web-app-access">
  **Enterprise Feature**: Control who can access your apps with authentication, team restrictions, and external user management.
</Card>

**Dify Community**: Web apps are public by default—anyone with the URL can access them. This works great for demos, public tools, and customer-facing applications.

**Privacy and Legal**:

* Add copyright information and privacy policy links
* Configure data handling preferences
* Set terms of service for compliance

## Feature Inheritance

Your web app automatically includes features you've enabled in your application configuration:

**Interactive Features**:

* Conversation openers and suggested follow-ups
* Pre-conversation forms for context gathering
* Voice input and speech-to-text capabilities
* Source citations and reference links
* Feedback collection and rating systems

**Functionality**:

* All workflow steps and AI model configurations
* Knowledge base integrations and tool connections
* Custom prompts and response formatting
* Rate limiting and usage controls

<Warning>
  Disabling features in your app configuration immediately removes them from the published web app.
</Warning>

## App Types and Behavior

Your web app automatically adapts its interface based on your application type:

<Tabs>
  <Tab title="Chat Applications">
    **Interface**: Conversation-style with message history
    **Features**: Persistent sessions, conversation management, real-time responses
    **Best for**: Customer support, consulting tools, interactive assistants
  </Tab>

  <Tab title="Workflow Applications">
    **Interface**: Form-based with result display
    **Features**: Single runs, batch processing, result saving
    **Best for**: Content generation, data processing, analysis tools
  </Tab>
</Tabs>

## Deployment Options

Once published, your web app can be accessed in multiple ways:

<CardGroup cols={2}>
  <Card title="Direct Link" icon="link">
    Share the web app URL for immediate access
  </Card>

  <Card title="Website Embedding" icon="window" href="/en/use-dify/publish/webapp/embedding-in-websites">
    Deploy as chat widgets or iframes on existing websites
  </Card>
</CardGroup>

## Publishing Best Practices

Before sharing your web app:

<Steps>
  <Step title="Test the user experience">
    Try your app on different devices and browsers to ensure it works smoothly.
  </Step>

  <Step title="Configure essential settings">
    Set up your app name, icon, description, and any required legal information.
  </Step>

  <Step title="Review access controls">
    Decide if your app should be public or require authentication.
  </Step>

  <Step title="Choose deployment method">
    Determine whether to share directly or embed on your website.
  </Step>
</Steps>

<Tip>
  Your web app configuration applies everywhere it's deployed. Changes to settings automatically update embedded versions too.
</Tip>