# Moving Boards Between Teamspaces

> This task requires a **YouDesign Admin** role. Regular Editors and Teamspace Admins cannot move boards across teamspace boundaries from the homepage UI.

Within a single teamspace, editors can reorganize boards between folders directly on the homepage. **Moving a board to a different teamspace**, however, is not exposed in the standard UI — it's a backend admin task performed against the YouDesign Models board table in ServiceNow.

## When You Need This

* A board was created in the wrong teamspace
* A teamspace is being consolidated or renamed and its boards should land elsewhere
* Governance requires moving a project's boards into a restricted teamspace

## How to Move a Board

1. In ServiceNow, navigate to the **YouDesign Models board table**: `x_inpi_yd_board`.
2. Locate the board you want to move (you can search by Name, Owner, or Folder).
3. Open the board record in form view.
4. Find the **Folder** reference field — it points at the current parent folder or teamspace.
5. Change the reference to the **target folder or teamspace**.
6. Save the record.
7. **Refresh YouDesign Models** in the browser — the homepage needs a refresh to reflect the new location.

> **🖼 Screenshot needed:** \[ServiceNow board list with the Folder column and one row being edited to point at a different parent] *Show: the `x_inpi_yd_board` list view with the Folder column highlighted and a reference-field editor open, illustrating the edit of the target location.*

## Before You Move

Check these three things first — moving a board doesn't automatically fix sharing or permissions:

1. **The target teamspace exists** and is the correct destination.
2. **The board's owner has access to the target teamspace.** Moving a board to a teamspace the owner can't see effectively hides it from them.
3. **Shared Editors and Viewers still need access.** Sharing is inherited from the teamspace — users who had access via the old teamspace may lose access after the move unless they're also members of the new one.

> **Make sure that the user has access to the teamspace you move the board to!** Otherwise they'll open the homepage and silently not see the board.

## What Moves With the Board

When you reassign the Folder reference, the following move with the board:

* The board's content and all its versions (`x_inpi_yd_board_content`, `x_inpi_yd_board_version`)
* All realtime indicator configuration applied to the board
* Attachments stored against the board

Sharing is **not** automatically updated — you may need to re-share the board to Editors and Viewers in the target teamspace.

## Limits & Gotchas

* **UI-level move is folder-scoped only.** From the homepage, Editors can drag a board between folders *within* the same teamspace. Cross-teamspace moves always require backend access.
* **Folder reference must be valid.** The target must be either a top-level teamspace folder or a subfolder under a teamspace the board is legitimately being moved into.
* **No audit trail on the YouDesign side.** The move shows up as an `Updated` timestamp/user change on the board record. If you need a fuller audit trail, use ServiceNow's record history.
* **Realtime indicators continue to work** as long as the shape-to-table bindings remain valid in the new teamspace.

## Related

* [Teamspaces](/models/work-in-the-app/homepage/teamspaces.md) — end-user teamspace management
* [Folders](/models/work-in-the-app/homepage/folders.md) — folder hierarchy within a teamspace
* [Access Rights and Roles](/models/admin/access-rights-and-roles.md) — who can do what
* [Sharing & Members](/models/work-in-the-app/homepage/sharing-and-members.md) — reassign sharing after a move


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ins-pi.com/models/admin/moving-boards.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.