---
title: "Board card views."
canonical: "https://support.appfire.com/space/DLP/298093266/Board%20card%20views."
format: markdown
---
| **Contents:**
> Macro (toc) |
| --- |
In this section, you can configure the Board module's default [card views](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297766986) and inheritance settings of the selected box type.
Keep in mind:
- A box type contains the default settings applicable to multiple boxes (all boxes of a given type). Those settings are adjusted in box type administration.
- Box configuration refers to the settings of a single, individual box. They are dependent on the box type settings.
> ℹ️ Please note that changing the configuration might disable (hide) settings or features in the box configuration (of an individual box) and within different modules.
> ℹ️
> ℹ️ Also, as modules can be renamed or deactivated, the module name in the side menu might change or not be shown at all.
## Security and access
Only a user with the App admin security role can access and manage the box type configuration.
To access this page:
1. Go to the** App Administration** >** Box type **>** choose the box type you want to edit** >** Board** >** Card views**.
## Inheritance mode
> ℹ️ An inheritance mode applies to all boxes of a given type (both existing and newly created).
> ℹ️
> ℹ️ As a result, when the inheritance mode is set to **inherited** or **own with inherited**, the card views from upper-level boxes appear in the **Card view** drop-down in the Board module.
In general, selecting an inheritance determines if an upper-level box imposes the configuration.
### Inheritance mode set to own
The **own** mode provides much more flexibility. When enabled:
- You can define the default card views for all boxes of a given type.
- You can bulk update all existing boxes. The card views added in upper-level boxes are not inherited.
- The default views are set up when a new box is created but can later be adjusted for each box by a box admin (the default configuration can be manually overridden).
### Inheritance mode set to inherited only
The **inherited only** mode doesn't allow for making any changes directly in the sub-box configuration.
- The card views are inherited from an upper-level box.
- The task card views page is not shown in the box configuration.
- Box admins can impact the sub-box by editing the card views directly in the configuration of an upper-level box (if they are also box admins for the upper-level box). As a result, users cannot save the modified card views, and sub-box admins cannot change the views in the box configuration since it is already preconfigured.
### Inheritance mode set to own with inherited
The **own with inherited** mode mixes the two.
- A box admin can create new card views directly in the sub-box configuration.
- The card views are inherited from the upper-level box (those views can only be edited in the upper-level box).
## Default card views
> ℹ️ Changes to the default card views apply to newly created boxes only.
To learn more about card views, see the [Card view creator](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297766986) page.
You can set the default views when the inheritance mode is set to **own** or **own with inherited**. The default card views are automatically set up when you create a new box.
Expand the **Current view** drop-down menu to see the default card views in the Board module.
