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

# Default Configuration

> Set system-wide defaults for homepage and ticket form settings

Default configuration allows administrators to set system-wide defaults for homepage and ticket form settings, with the ability to override these values through user permissions.

## Overview

AGO supports a hierarchical configuration system where:

1. **Global defaults** are defined at the system level in AGO Config
2. **Permission-level overrides** can customize settings for specific user groups
3. **Automatic merging** means users always receive the appropriate configuration

This approach simplifies administration by eliminating the need to duplicate settings across every permission while still allowing customization where needed.

## How It Works

```mermaid theme={null}
flowchart TD
    A[User Request] --> B[Check Permission Configuration]
    B --> C{Has permission-level value?}
    C -->|YES| D[Use permission value]
    C -->|NO| E[Use AGO Config default]
```

### Configuration Fields

| Setting              | Level       | Description                                            |
| -------------------- | ----------- | ------------------------------------------------------ |
| Default Homepage     | System-wide | Homepage configuration applied to all users by default |
| Default Ticket Form  | System-wide | Ticket form used when no override exists               |
| Homepage Override    | Permission  | Custom homepage for users with this permission         |
| Ticket Form Override | Permission  | Custom ticket form for users with this permission      |

### Merge Logic

The system handles configuration resolution as follows:

1. If a value exists in the user's permission, that value is used
2. Otherwise, the AGO Config default is used
3. If neither exists, no value is applied

## Configuration

### Setting Global Defaults

Global defaults are configured via the API. See the [Public API v1 Reference](../api/public-api-v1) for endpoint details.

Available default settings include:

* **Homepage layout** — grid or list display, welcome message, featured agents
* **Welcome video** — optional video shown to new users on their first visit (see [Welcome Video](#welcome-video) below)
* **Default ticket form** — the ticket form used for all users without an override

### Permission-Level Overrides

To override defaults for specific user groups:

1. Navigate to **Settings** → **User Management**
2. Select or create a permission
3. Configure the **Home Page** or **Ticket Form** fields
4. Save changes

Users with this permission will receive the override values instead of global defaults.

***

## Use Cases

### Centralized Defaults

Set global defaults once, and all users receive consistent configuration without needing to configure each permission.

### Department-Specific Configuration

* **Sales team**: Custom homepage with CRM-focused agents
* **Support team**: Different homepage with support agents and ticket form
* **General users**: Global defaults

### Gradual Rollout

1. Configure global defaults for all users
2. Create a test permission with new configuration
3. Assign test permission to pilot users
4. Roll out globally by updating defaults

## Welcome Video

You can configure a welcome video that automatically plays for new users the first time they visit the homepage. After watching (or closing the modal), the video is not shown again automatically. Users can rewatch the video at any time by clicking the link on the homepage.

### Configuration Fields

Configure these fields in the homepage settings:

| Field           | Description                                                                  |
| --------------- | ---------------------------------------------------------------------------- |
| **Video URL**   | URL of the video to embed (supports Vimeo, Guidde, and other providers)      |
| **Link text**   | Text for the rewatch link on the homepage (defaults to "Watch our tutorial") |
| **Video title** | Title displayed above the video in the modal (defaults to "Welcome")         |

### How It Works

1. When a new user visits the homepage for the first time, the welcome video modal opens automatically
2. The user can close the modal at any time — it will not auto-show again
3. A link with a play icon appears on the homepage so users can rewatch the video whenever they want
4. The video URL supports Vimeo and Guidde embeds natively; other video URLs are embedded directly

### Setting Up a Welcome Video

1. Obtain the URL of your welcome video (e.g., a Vimeo link)
2. Configure the video URL in your homepage settings via the API
3. Optionally customize the link text and modal title
4. New users will see the video on their next homepage visit

## Benefits

| Benefit                    | Description                                           |
| -------------------------- | ----------------------------------------------------- |
| **Simplicity**             | No need to duplicate configuration across permissions |
| **Flexibility**            | Override defaults where needed                        |
| **Maintainability**        | Central location for default settings                 |
| **Backward Compatibility** | Existing permissions continue to work                 |

## Troubleshooting

<AccordionGroup>
  <Accordion title="Configuration Not Applying">
    **Problem:** User sees incorrect homepage or ticket form.

    **Solutions:**

    1. Verify the user's permission has the expected configuration
    2. Check if permission-level values are overriding defaults
    3. Clear browser cache and refresh
    4. Verify the configuration by checking the user's effective settings
  </Accordion>

  <Accordion title="Default Not Used">
    **Problem:** Global default is ignored.

    **Solutions:**

    1. Check if user's permission has an override value set
    2. Verify AGO Config has the default configured
    3. Check that the default value is valid (valid JSON, existing ticket form ID)

    ***
  </Accordion>
</AccordionGroup>

## Related Documentation

* [Public API v1 Reference](../api/public-api-v1) - Complete API documentation for default configuration endpoints
* [Organization Management](./organization-management-feature) - Multi-tenant configuration
* [Access Control Rules](../users/access-control-rules) - Permission-based access
* [Agent Permissions](../users/agent-permissions) - Agent access configuration