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

# Change board settings

> Change each board's name and description, group links, Google Drive folder, status labels, the defaults used when you create cards, email intake, and chat notifications.

Board settings let you set labels and defaults that apply only to that board. The board inherits the team-wide settings, and only the items you change on the board override them.

Who can do this: Owner, Manager, Member (Guests can't change them)

## Open the settings

Open **Board settings** in either of these ways.

* On the board screen, click the board name or description at the top
* In the board list, open the menu at the left end of the row and choose **Board settings**

After making changes, click **Save changes**. To undo them, click **Discard changes**.

## What you can change

The settings are split into tabs.

| Tab | What you can change |
| - | - |
| **Basics** | Board name and description, groups, Google Drive folder, custom fields |
| **Status labels** | The display names of statuses |
| **Card defaults** | The starting values used when you create a card on this board |
| **Email** | The address for creating cards by email ([Create cards by email](https://help.zarms.cloud/en/boards/email-to-card.md)) |
| **Notifications** | Google Chat and Slack notifications (shown only to Owners and Managers) |

The **Basics** tab has these items.

| Item | What it does |
| - | - |
| Board name / Description | If you change the board name, the name of the board's Google Drive folder changes too |
| Groups | Links the board to groups. Used when the left nav shows boards for "My groups" |
| Google Drive folder | The parent folder where the board's folder is kept. You usually don't need to change it |
| Custom fields | If your team has created fields for boards, enter their values here |

### Status labels

On the **Status labels** tab, you can change just the display names of statuses to fit the board, such as renaming "In progress" to "Working on it" or "In review" to "Under review." The stages themselves (the six from Draft through Done and Cancelled) don't change. Any status you leave blank uses the team's label.

This doesn't affect cards on My Board that don't belong to a board.

### Card create defaults

On the **Card defaults** tab, set the values filled in from the start when you create a card on this board. You can set the initial card name, status, priority, Hours (planned), and the start date and due date (how many days from today, and at what time). Turn on **Set the processor, reviewer, and receiver to the creator** to make the person who creates the card the Processor, Reviewer, and Receiver too.

Fields you leave blank use the team's defaults. Admins change the team-wide defaults in the [admin console](https://help.zarms.cloud/en/admin/admin-console.md).

### Google Drive folder

Normally, the board's folder is created automatically inside the team's `ZARMS ボード` (ZARMS boards) folder. Choose a parent folder only when you want to keep the files somewhere else, for example to separate the files of a board you invite Guests to from your other boards. To remove the folder you chose, click **Clear selection**.

Changing the parent folder doesn't move any existing Google Drive folders or files. For details, see [Google Drive structure and permissions](https://help.zarms.cloud/en/admin/google-drive.md).

### Google Chat and Slack notifications

Owners and Managers also see the **Notifications** tab, which posts the board's activity to a Google Chat space or a Slack channel. For how to set it up, see [Post board activity to Google Chat or Slack](https://help.zarms.cloud/en/notifications/chat.md).

## Other actions from the settings screen

At the bottom of Board settings, there are also **Duplicate board** and **Archived** buttons. For how to use them, see [Duplicate and archive a board](https://help.zarms.cloud/en/boards/duplicate-and-archive.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.