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

# Managed Default Views

> Let users set a default view per table that automatically loads when the resource is first opened.

![Default Views](https://advancedtables.com/images/default-views.png)

Advanced Tables now allows your users to manage which view they would like to be their default view for each table. When a view is a default it will be automatically loaded when the resource/table is first opened after logging in.

## Updating to the Managed Default Views Beta

1. Update to the beta

   If you are on version 3.8 and only want to experiment with Managed Default Views, update your `composer.json` file to:

   ```json theme={null}
   "archilex/filament-filter-sets": "~3.9.0-beta.1",
   ```

   If you want to experiment with Managed Default Views, [Multi-Sort](/v3/features/multi-sort), and [Advanced Indicators](/v3/features/advanced-indicators), update your `composer.json` file to:

   ```bash theme={null}
   "archilex/filament-filter-sets": "^3.10@beta",
   ```

2. Publish and run the migrations:

   ```bash theme={null}
   php artisan vendor:publish --tag="advanced-tables-migrations"
   php artisan migrate
   ```

3. If you are using [multi-tenancy](/v3/multi-tenancy/multi-tenancy) run the following command to add the appropriate constraints. If not, you can skip this:

   ```bash theme={null}
   php artisan advanced-tables:add-tenancy
   ```

4. Compile assets

   After updating run `npm run build` and `php artisan filament:upgrade`.

5. Enable Managed Default Views

   Managed Default Views are disabled by default. To enable, add `managedDefaultViewsEnabled()` to your panel provider:

   ```php theme={null}
   AdvancedTablesPlugin::make()
       ->managedDefaultViewsEnabled()
   ```

## Using Managed Default Views

To use Managed Default Views:

1. Open the [View Manager](/v3/features/view-manager).
2. Next to the view you would like to make default, click the action group button then choose, "Set default".
3. You may also remove a view as a default view. If there is a matching developer-defined [default Preset View](/v3/features/preset-views#loading-a-default-preset-view), it will become the new default.

## UX Recommendation

Advanced Tables comes with an basic "Default" view that is automatically added to each table. However, this default view is an internal "view" and does not display in the View Manager. To offer the clearest UX to your end-users and the best compatibility with Managed Default Views, it is recommended to disable this internal default view, and to add a default Preset View to each of your pages. You can accomplish this by:

1. Disable the internal default view:

   ```php theme={null}
   AdvancedTablesPlugin::make()
       ->favoritesBarDefaultView(false)
   ```

2. Add a default Preset View to your list pages:

   ```php theme={null}
   public function getPresetViews(): void
   {
       return [
           'default' => PresetView::make()
               ->default()
               ->favorite()
               ->icon('heroicon-o-bars-4')
       ];
   }

   ```

> Note: Starting in the upcoming v4, the internal default view will be removed in favor of a default Preset View.