diff --git a/pages/changelogs/2024-03-11-sub-to-boards.mdx b/pages/changelogs/2024-03-11-sub-to-boards.mdx
index 79ff57bac0..ee733b1c75 100644
--- a/pages/changelogs/2024-03-11-sub-to-boards.mdx
+++ b/pages/changelogs/2024-03-11-sub-to-boards.mdx
@@ -9,7 +9,7 @@ thumbnail: "/changelog/subscribetoboards.png"
---
Boards are a useful tool to collect a series of reports in one place, but they shouldn't be a set and forget experience. It's important to stay in the loop with how these key metrics are moving.
-To keep you and your team up to date on how much progress you're making towards your metrics, you can [Subscribe to a Board](/docs/boards/advanced#board-subscriptions).
+To keep you and your team up to date on how much progress you're making towards your metrics, you can [Subscribe to a Board](/docs/boards#board-subscriptions).
All it takes is setting the schedule of how often you want to receive this information and selecting where you want to read it (email or Slack).
Teams that are collectively informed on their data can stay on the same page, and using Subscribe to Boards can help them get there.
diff --git a/pages/docs/boards.mdx b/pages/docs/boards.mdx
index 852484bad9..5da11d7680 100644
--- a/pages/docs/boards.mdx
+++ b/pages/docs/boards.mdx
@@ -54,7 +54,7 @@ There are a few ways to add an existing report to a board. You can either start
- Starting from an existing report, adding the report to a board can be done via the board breadcrumb dropdown at the top left of the report, next to the report's title. Click into the dropdown, then select "Add to another Board." Choose your board, and a copy of the report will be added to it.
- Starting from another board, select the overflow menu of a report you'd like to add. Select "Make a Copy" and then choose the board you would like to add it to.
-Note that adding an existing report always creates a [linked copy](/docs/boards/advanced#what-is-a-linked-report).
+Note that adding an existing report always creates a [linked copy](/docs/boards/sharing-and-permission#linked-reports).
Text cards support rich text formatting. After highlighting the text in a text card, you'll see a menu pop up where you can apply the following:
@@ -114,3 +114,52 @@ Row heights can now be adjusted to either show more report content, or hide empt
A row's height is initially determined by the tallest card within that row. Text cards can be very short if they contain only one line of text, or very tall if they contain many lines. Meanwhile, reports always start at their minimum height, but may warrant expansion in order to show more data (more bars on a bar chart, for example).
A row will start life at the minimum possible height.
+
+### Step 5: Board-wide Date Ranges and Filters
+
+Boards allow you to alter some aspects of the queries within each of the reports on that board, making it simple to ensure every report is showing results from a consistent set of data. Both date ranges and filters can be added by clicking "Add Filter" at the top right of the board. This will open a row, shown below, where the date range can be selected, and filters can be applied.
+
+
+
+By default, date ranges and filters are temporary, allowing you to explore the data without overwriting the board. But, if you wish to save the date range and filter selections you've made to the board, so they'll appear for other users as well, click "Save to Board."
+
+**Note** Applying date ranges and filters on a board does not change the queries saved in each individual report; instead, it only changes the data displayed when you view those reports in the current board. If you click into a report from the board, however, Mixpanel will maintain the date range and filters to ensure you see data consistent between the board and report. Navigate to the report on its own, though, and you'll see the report's original saved date range and filters.
+
+
+## Board Subscriptions
+
+Board Subscriptions allow you to receive a snapshot of a board sent as an email or a slack message. Subscriptions allow members to share recent data with both project members and external audiences, providing quick and meaningful insight into a Mixpanel project.
+
+You must be a Project Owner, Admin, or Analyst to create a subscription.
+
+Subscriptions will send the board on a recurring schedule. You can choose a daily, weekly or monthly interval. Note that subscriptions only show the 8 reports that are on the top of a board.
+
+To create a Subscription:
+
+1. Select **Subscribe** from the header at the top right of the board. You can see a list of existing subscriptions for the board here as well. Select "Create New".
+ 
+
+2. Fill out the resulting form, selecting the desired email recipients or Slack channel, as well as the sending frequency (daily, weekly, or monthly).
+ 
+ - Any email address will receive the email, whether or not they are internal or external to your organization
+ - Private Slack Channels are not available at this time
+3. Click "Subscribe".
+
+### Seeing All Subscriptions
+
+
+You can access this by clicking the "Subscribe" button at the top right of the board. Then select "View All".
+This gives you a view of all subscriptions across all users.
+
+### Subscriptions for Private Boards
+
+It is possible to subscribe to a private board. However, there are some restrictions to what will be visible or accessible.
+
+1. If you convert a regular board with subscriptions into a private board, existing subscriptions will still work with existing recipients. However, if they click **View Board**, they will not be able to access your private board. Creating new subscriptions or editing existing subscriptions within the private board will force you to limit recipients to yourself.
+2. You cannot edit subscriptions of someone else’s private board without selecting a different board that you have access to (regardless of your permissions or role). You can still delete the subscription or select a different board.
+
+## TV Mode
+
+The **Enter TV Mode** option enables displaying a Board on a big screen (such as a TV in the office) where top-level company metrics / KPIs can be constantly monitored. The Board will auto-refresh every 10 minutes when in TV mode.
+
+
\ No newline at end of file
diff --git a/pages/docs/boards/_meta.ts b/pages/docs/boards/_meta.ts
index 31fe195a20..125544e50d 100644
--- a/pages/docs/boards/_meta.ts
+++ b/pages/docs/boards/_meta.ts
@@ -1,6 +1,7 @@
export default {
+ "sharing-and-permission": "Sharing and Permission",
"templates": "Templates",
"boards-on-boards": "Boards on Boards",
"public-boards": "Public Boards",
- "advanced": "Advanced"
+ "move-boards": "Move Boards"
}
diff --git a/pages/docs/boards/advanced.mdx b/pages/docs/boards/advanced.mdx
deleted file mode 100644
index f30eb98428..0000000000
--- a/pages/docs/boards/advanced.mdx
+++ /dev/null
@@ -1,202 +0,0 @@
-import { Callout } from 'nextra/components'
-
-# Advanced
-
-## Board-wide Date Ranges and Filters
-
-Boards allow you to alter some aspects of the queries within each of the reports on that board, making it simple to ensure every report is showing results from a consistent set of data. All board-wide settings can be accessed from the top of the screen, right below the header. Select the desired date range on the left side, or select a filter by pressing the "+" button on the right side. By default, board-wide date ranges and filters are temporary. If you wish to save the date range and filter selections you've made to the board, so they'll appear for all users, click "Save", to the right of the filters. Similarly, you can press "Cancel" to discard the changes.
-
-
-
-Applying date ranges and filters on a board does not change the queries saved in each individual report; instead, it only changes the data displayed when you view those reports in the current board. If you click into a report from the board, however, Mixpanel will maintain the date range and filters to ensure you see data consistent between the board and report. Navigate to the report on its own, though, and you'll see the report's original saved date range and filters.
-
-Board-wide settings are also not modifiable in the report. Since the board-wide settings are always applied, we maintain them so they don't affect report state and to keep consistent results once a user navigates back to the board.
-
-### Board-wide Date Ranges
-
-By default, the board respects the date range selected by each individual report. You can set a date range board-wide. All date range settings are the same as in reports, so any date range you select in boards will be the same as if it were selected in a report.
-
-### Board-wide Filters
-
-Press the plus button to add a filter. Filters are applied to every report in the board. Note that the filters set from the board could conflict with filters on individual reports, leading to unexpected results. All board-wide filters are added to the "Filter" section in reports
-
-#### Board-wide Filter Settings
-
-
-
-Filter Settings are only available for enterprise plans.
-
-Filter settings allow for additional configuration on boards, meant for boards that are highly consumed or are standardized across a set of filters. Filter settings are only available for string filters using "is" or "is not" operators.
-
-- "Limit filter values to the selection above"
- Reduces the set of values available when accessing the filter to the choices selected. This is useful when there are a large set of filter values, and the board creator wants to focus in only on a certain set of filter values
-
-- "Start filter with nothing selected"
- Starts the filter as not filtering for anything. This is useful when the filter property is known, or when wanting to focus to a particular property. This also saves time from users from having to select this property.
-
-These settings can be used in combination, so that a filter property can be selected, and only be allowed to choose a particular subset of values.
-
-## Board Subscriptions
-
-Board Subscriptions allow you to receive a snapshot of a board sent as an email or a slack message. Subscriptions allow members to share recent data with both project members and external audiences, providing quick and meaningful insight into a Mixpanel project.
-
-You must be a Project Owner, Admin, or Analyst to create a subscription.
-
-Subscriptions will send the board on a recurring schedule. You can choose a daily, weekly or monthly interval. Note that subscriptions only show the 8 reports that are on the top of a board.
-
-To create a Subscription:
-
-1. Select **Subscribe** from the header at the top right of the board. You can see a list of existing subscriptions for the board here as well. Select "Create New".
- 
-
-2. Fill out the resulting form, selecting the desired email recipients or Slack channel, as well as the sending frequency (daily, weekly, or monthly).
- 
- - Any email address will receive the email, whether or not they are internal or external to your organization
- - Private Slack Channels are not available at this time
-3. Click "Subscribe".
-
-### Seeing All Subscriptions
-
-
-You can access this by clicking the "Subscribe" button at the top right of the board. Then select "View All".
-This gives you a view of all subscriptions across all users.
-
-### Subscriptions for Private Boards
-
-It is possible to subscribe to a private board. However, there are some restrictions to what will be visible or accessible.
-
-1. If you convert a regular board with subscriptions into a private board, existing subscriptions will still work with existing recipients. However, if they click **View Board**, they will not be able to access your private board. Creating new subscriptions or editing existing subscriptions within the private board will force you to limit recipients to yourself.
-2. You cannot edit subscriptions of someone else’s private board without selecting a different board that you have access to (regardless of your permissions or role). You can still delete the subscription or select a different board.
-
-## Sharing and Permissions
-
-
- Growth and Enterprise plan users can control who views and edits reports in a board. Free plan users have view and edit permissions for all boards and reports in a project. See our [pricing page](https://mixpanel.com/pricing/) for more details.
-
-
-Sharing and permissions are set at the board level, and all reports saved on a board inherit the same set of sharing and permissions settings of that board.
-
-To share a board, and therefore all reports contained within it, click the Share button at the top right of the board. From here, sharing works as before, but remember, sharing a board now shares all of that board's reports as well.
-
-
-
-Both reports and boards can also be shared via the "Copy URL" button at the top right. Clicking this button will immediately copy the short link to the report or board, so you can quickly paste it into your application of choice.
-
-
-
-So long as the recipient has access to the project, they will be able to see the shared report or board. However, unless they have specifically given Editor permissions, they will only be able to view it, not edit it.
-
-In the sharing process, you can choose the permissions level granted to the individual with whom you're sharing the board. Teammates with access to a board can either be Viewers (any changes made will not be saved) or Editors (changes made will be saved).
-
-As with sharing, setting a user's permission level on a board will give them the same permission level for all reports on that board.
-
-## Move Board
-
-Move helps teams organize their work and easily replicate Boards across projects and organizations. Using Move, you can find a Board you want to copy, duplicate it, and move it to a different project.
-
-Let’s take an example situation:
-
-1. An organization has Project A and Project B that support different products and teams within the organization.
-2. Team A has some fantastic Boards that have been well received by leadership, executives, and investors.
-3. Team B would like to replicate these reports without having to build them all from scratch.
-
-This is where Move comes in. With the right permissions, Team A can move copies of their Boards to Team B’s project, allowing Team B to fill in their events and be up and running quickly.
-
-*Please note: Moving boards from projects based in the US -> EU as well as EU -> US is unavailable at this time.
-
-### Turning Move Off and On
-
-1. Go to Project Settings
-2. Select Moving Boards from the left hand menu
-3. If you are an organization admin, you will be able to select the how freely you want boards to be able to be moved: not at all, within the organization, or between organizations.
- - Not at all: no Board can be moved to any other project, no matter the organization
- - Within organization: a Board can be moved to any other project in the same organization
- - Any organization: a Board can be moved to any other project, even one in a different organization
- This setting does not affect whether you can move a Board into a project, only whether you can move a Board out of a project.
-
-4. On this page, you can also see who last updated the permissions and when.
-
-
-
-### Using Move
-
-
-
-Step 1: Go to the Board you wish to move.
-
-Step 2: Hover over the `Move to` option.
-
-Step 3a: Enterprise users: select ‘projects’, then select the specific project that you want to move the board to. Once you’ve selected a project, then list will populate with Boards you can place the current Board in if you wish.
-
-Step 3b: Non-enterprise users: hover over the "Move To" option, and the project menu will appear immediately. From there, you can choose “Move to your Boards” or another location and select your choice.
-
-Step 3c: You can also use Move to use Boards from a demo project in your own. Get your free Mixpanel demo account and click [here](https://mixpanel.com/api/app/demo_project?show-demo-dataset-modal=true) to access the demo datasets. Once you're in, you can set up a new Board easily using a [template](/docs/boards/templates), or you can build a report from scratch. If you like what you see and want to use the analysis in your own project, you can click the button that says "Use this Board." You'll then select the project to which you want to move the board.
-
-Step 4: If there are events and properties used in the old project but not the new project, the affected reports will remain empty or say “no data” until new events and properties are selected.
-
-When a report can’t populate, it will display one of two states: a faded out sample report or a “no data” status.
-
-- Charts that show "no data" occur when an event has been tracked in the last 30 days, but a filter or date range result in no data for the report.
-- For the sample report to appear, the report would have to be configured with an event that hasn't existed or at least hasn't been tracked in past 30 days.
-
-For example: a join membership club event happened 100 times yesterday, but 0 so far today. If you create a report for today, it will show “no data”. But if this is day one of the program and it has never been tracked before, it will show a dummy sample report. From this empty state, you can set up your new reports like any other report.
-
-👉🏽 NOTE: If you would like a version of the Board to stay in the parent project, duplicate it and move the new duplicate Board.
-
-## FAQ
-
-### Where are reports saved to?
-
-Reports are always saved to boards. Previously, reports were separately saved and added to boards. In boards now, when you save a report, you'll be prompted to save it to a specific board. In essence, the board now acts as a folder, with many potential purposes, including:
-
-- A centralized place to track numerous metrics related to a product launch
-- A chain of analyses digging into a particular behavior or issue
-- A set of draft reports you're working on
-
-This will make it easy to keep reports organized, and reduce time wasted recreating the same reports again and again.
-
-Note: This change only applies to the reports that can be added to boards—Mixpanel's core reports: Insights, Flows, Funnels, and Retention. Advanced reports like Signal, Experiments, and Impact have been moved to the Applications folder at the top right of the page.
-
-
-
-### Where are sharing and permissions set?
-
-Previously, sharing and permissions were editable at both the report and board levels. This made managing sharing and permissions tedious due to the sheer number of items requiring individual settings.
-
-Now, all reports saved on the same board will have the same sharing and permissions settings. This means sharing multiple reports with your team is a simple matter of sharing the board. As before, however, any report or board can be shared by simply clicking the "Copy URL" button, and sharing the resulting short link.
-
-
-
-### What happens to reports on multiple boards?
-
-All copies of reports have a source location. This can be seen when looking at the report details.
-
-
-
-However, the same report can be viewed from multiple different boards.
-
-
-
-On boards, the arrow icon on the top left indicates of the report lives on this board, or is a linked view.
-
-### What is a linked report?
-
-Every report in Mixpanel has a board where it was originally saved to. This is called the original board. However, in the interest of being able to use the same report across a variety of boards and sharing the same insight across your team and company, Mixpanel has introduced the concept of a "linked report". A linked report is denoted by the arrow in the icon of the report. Any time an existing report is added to a board or a copy is made, a linked report is made. Any changes to the report will get reflected in all of the linked reports associated with the report.
-
-
-
-### What is TV Mode?
-
-The **Enter TV Mode** option enables displaying a Board on a big screen (such as a TV in the office) where top-level company metrics / KPIs can be constantly monitored. The Board will auto-refresh every 10 minutes when in TV mode.
-
-
-
-### How do I standardize the color of segments across reports on the same dashboard?
-
-1. On the report, de-select all segments.
-2. Click the down arrow button next to segment name in the table below and select "Segment A->Z" for each report.
-3. Select all segments.
-In all reports, the segments colors should match.
-
-This should allow you to standardize across your reports as long as they have the same segment names.
-
diff --git a/pages/docs/boards/move-boards.mdx b/pages/docs/boards/move-boards.mdx
new file mode 100644
index 0000000000..a7dfb78408
--- /dev/null
+++ b/pages/docs/boards/move-boards.mdx
@@ -0,0 +1,54 @@
+# Move Boards: Reuse Boards across different projects
+
+## Overview
+
+Move helps teams organize their work and easily replicate Boards across projects and organizations. Using Move, you can find a Board you want to copy, duplicate it, and move it to a different project.
+
+Let's take an example situation:
+
+1. An organization has Project A and Project B that support different products and teams within the organization.
+2. Team A has some fantastic Boards that have been well received by leadership, executives, and investors.
+3. Team B would like to replicate these reports without having to build them all from scratch.
+
+This is where Move comes in. With the right permissions, Team A can move copies of their Boards to Team B's project, allowing Team B to fill in their events and be up and running quickly.
+
+**Please note: Moving boards from projects based in the US -> EU as well as EU -> US is unavailable at this time.**
+
+### Turning Move Off and On
+
+1. Go to Project Settings
+2. Select Moving Boards from the left hand menu
+3. If you are an organization admin, you will be able to select the how freely you want boards to be able to be moved: not at all, within the organization, or between organizations.
+ - Not at all: no Board can be moved to any other project, no matter the organization
+ - Within organization: a Board can be moved to any other project in the same organization
+ - Any organization: a Board can be moved to any other project, even one in a different organization
+ This setting does not affect whether you can move a Board into a project, only whether you can move a Board out of a project.
+
+4. On this page, you can also see who last updated the permissions and when.
+
+
+
+### Using Move
+
+
+
+Step 1: Go to the Board you wish to move.
+
+Step 2: Hover over the `Move to` option.
+
+Step 3a: Enterprise users: select "projects", then select the specific project that you want to move the board to. Once you've selected a project, then list will populate with Boards you can place the current Board in if you wish.
+
+Step 3b: Non-enterprise users: hover over the "Move To" option, and the project menu will appear immediately. From there, you can choose “Move to your Boards” or another location and select your choice.
+
+Step 3c: You can also use Move to use Boards from a demo project in your own. Get your free Mixpanel demo account and click [here](https://mixpanel.com/api/app/demo_project?show-demo-dataset-modal=true) to access the demo datasets. Once you're in, you can set up a new Board easily using a [template](/docs/boards/templates), or you can build a report from scratch. If you like what you see and want to use the analysis in your own project, you can click the button that says "Use this Board." You'll then select the project to which you want to move the board.
+
+Step 4: If there are events and properties used in the old project but not the new project, the affected reports will remain empty or say “no data” until new events and properties are selected.
+
+When a report can't populate, it will display one of two states: a faded out sample report or a “no data” status.
+
+- Charts that show "no data" occur when an event has been tracked in the last 30 days, but a filter or date range result in no data for the report.
+- For the sample report to appear, the report would have to be configured with an event that hasn't existed or at least hasn't been tracked in past 30 days.
+
+For example: a join membership club event happened 100 times yesterday, but 0 so far today. If you create a report for today, it will show “no data”. But if this is day one of the program and it has never been tracked before, it will show a dummy sample report. From this empty state, you can set up your new reports like any other report.
+
+**NOTE:** If you would like a version of the Board to stay in the parent project, duplicate it and move the new duplicate Board.
\ No newline at end of file
diff --git a/pages/docs/boards/sharing-and-permission.mdx b/pages/docs/boards/sharing-and-permission.mdx
new file mode 100644
index 0000000000..181c8ac00b
--- /dev/null
+++ b/pages/docs/boards/sharing-and-permission.mdx
@@ -0,0 +1,48 @@
+import { Callout } from 'nextra/components'
+
+# Sharing and Permission
+
+
+ Growth and Enterprise plan users can control who views and edits reports in a board. Free plan users have view and edit permissions for all boards and reports in a project. See our [pricing page](https://mixpanel.com/pricing/) for more details.
+
+
+## Overview
+Reports are always saved to boards. When you save a report, you'll be prompted to save it to a specific board. In essence, the board now acts as a folder, with many potential purposes, including:
+
+- A centralized place to track numerous metrics related to a product launch
+- A chain of analyses digging into a particular behavior or issue
+- A set of draft reports you're working on
+
+This will make it easy to keep reports organized, and reduce time wasted recreating the same reports again and again.
+
+Note: This only applies to the Mixpanel's core reports (Insights, Flows, Funnels, and Retention). Advanced reports like Signal, Experiments, and Impact lives in the Applications folder at the top right of the page.
+
+
+
+## Sharing
+
+Sharing and permissions are set at the board level, and all reports saved on a board inherit the same set of sharing and permissions settings of that board.
+
+To share a board, and therefore all reports contained within it, click the Share button at the top right of the board. From here, sharing works as before, but remember, sharing a board shares all of that board's other reports as well.
+
+
+
+Both reports and boards can also be shared via the "Copy URL" button at the top right. Clicking this button will immediately copy the short link to the report or board, so you can quickly paste it into your application of choice.
+
+
+
+So long as the recipient has access to the project, they will be able to see the shared report or board. However, unless they have specifically given Editor permissions, they will only be able to view it, not edit it.
+
+## Permissions
+
+Sharing and permissions are set at the board level, and all reports saved on a board inherit the same set of sharing and permissions settings of that board.
+
+In the sharing process, you can choose the permissions level granted to the individual with whom you're sharing the board. Teammates with access to a board can either be Viewers (any changes made will not be saved) or Editors (changes made will be saved).
+
+As with sharing, setting a user's permission level on a board will give them the same permission level for all reports on that board.
+
+## Linked Reports
+
+Every report in Mixpanel has a board where it was originally saved to. This is called the original board. However, in the interest of being able to use the same report across a variety of boards and sharing the same insight across your team and company, Mixpanel has introduced the concept of a "linked report". A linked report is denoted by the arrow in the icon of the report. Any time an existing report is added to a board or a copy is made, a linked report is made. Any changes to the report will get reflected in all of the linked reports associated with the report.
+
+
\ No newline at end of file
diff --git a/pages/docs/reports.mdx b/pages/docs/reports.mdx
index c448ef375f..5dd5b22a44 100644
--- a/pages/docs/reports.mdx
+++ b/pages/docs/reports.mdx
@@ -222,6 +222,8 @@ Compare to overall allows you compare each segment value and see what proportion
When you are satisfied with the analysis, and decide that this is something that you are likely to revisit, Mixpanel recommends that you save the report to a [Board](/docs/boards). You can do this by pressing "Save" in the top right and selecting the Board you would like to save to, or creating a new Board.
+All reports are saved to a Board, which inherits the sharing settings and permissions applied to that Board. Learn more about saving, sharing, and permission for your reports and Boards [here](/docs/boards/sharing-and-permission).
+
## Typecasting
diff --git a/pages/docs/tracking-methods/id-management/migrating-to-simplified-id-merge-system.md b/pages/docs/tracking-methods/id-management/migrating-to-simplified-id-merge-system.md
index 8b9adf5d52..fb214f3e26 100644
--- a/pages/docs/tracking-methods/id-management/migrating-to-simplified-id-merge-system.md
+++ b/pages/docs/tracking-methods/id-management/migrating-to-simplified-id-merge-system.md
@@ -425,17 +425,17 @@ As part of creating the new Simplified ID Merge project, you would also need to
3. Boards & Reports
- Move Board: Mixpanel provides a [Move Board](/docs/boards/advanced#move-board) feature that allows you to directly [transfer Boards between projects](/changelogs/2023-07-27-move) preserving reports, filters, and text annotations.
+ Move Board: Mixpanel provides a [Move Board](/docs/boards/move-boards) feature that allows you to directly [transfer Boards between projects](/changelogs/2023-07-27-move) preserving reports, filters, and text annotations.
Before you move any Board, it's important to note the following:
- Duplicate the existing Board and move the new copy into the new project. This would minimize impact where users are still using Boards and reports in the old project.
- Any saved cohorts, custom events, custom properties, lookup tables would need to be created first as they don't get automatically moved as part of the Move Board.
- - You may need to replicate the permissions for the moved Board should you have very specific [sharing permissions](/docs/boards/advanced#sharing) set in the existing project.
+ - You may need to replicate the permissions for the moved Board should you have very specific [sharing permissions](/docs/boards/sharing-and-permission) set in the existing project.
- Double check that all reports (especially those that use cohorts, custom events, custom properties, lookup tables) are working properly.
-4. Lexicon
+1. Lexicon
Schemas API or CSV Export/Import: Migrate the Lexicon schema definitions (i.e. display name, descriptions, etc.) of your events, event properties, and user properties from the existing project to the new project using either the [Lexicon Schemas API](https://developer.mixpanel.com/reference/lexicon-schemas-api) or [Lexicon CSV Export/Import](/docs/data-governance/lexicon#export-and-import-lexicon-data).
diff --git a/pages/docs/users.md b/pages/docs/users.mdx
similarity index 64%
rename from pages/docs/users.md
rename to pages/docs/users.mdx
index 4c1b642c0e..b0a9d3b652 100644
--- a/pages/docs/users.md
+++ b/pages/docs/users.mdx
@@ -8,7 +8,7 @@ If you want to import User Profiles into Mixpanel, see our [User Profiles guide]
### Use Case
-Mixpanel’s Users page aggregates and organizes a collection of user profiles. This facilitates a granular view into the behavior of individual users or groups of users. The Users page can be used to:
+Mixpanel's Users page aggregates and organizes a collection of user profiles. This facilitates a granular view into the behavior of individual users or groups of users. The Users page can be used to:
- Count users based on behavior.
- Explore their unique history.
@@ -17,17 +17,17 @@ Mixpanel’s Users page aggregates and organizes a collection of user profiles.
## Basic Features
-You can select **User Profiles** or **All Users** in the Users page. If you select **User Profiles**, the page will only show users that have at least one user profile property set. If you select **All Users**, the page will show all users who have completed any event.
+You can select **User Profiles** or **All Users** in the Users page. If you select **User Profiles**, the page will only show users that have at least one user profile property set. If you select **All Users**, the page will show all users who have completed any event.
-By clicking the name of a user in the User tables, you can explore that user's unique history by examining their user profile. Learn more about the Users Profiles [here](/docs/data-structure/user-profiles).
+By clicking the name of a user in the User tables, you can explore that user's unique history by examining their user profile. Learn more about the Users Profiles [here](/docs/data-structure/user-profiles).
### Cohorts
A cohort is a group of users who share a certain set of properties or have performed a particular combination or frequency of events. You can create a cohort on the Users page by generating filtering criteria. Once a cohort is created, you can save it and use it to group and filter data in other Mixpanel reports.
-Learn more about Cohorts [here](/docs/users/cohorts).
+Learn more about Cohorts [here](/docs/users/cohorts).
@@ -35,7 +35,7 @@ Learn more about Cohorts [here](/docs/users/cohorts).
### Modifying Table Columns
-You may wish to change what data is displayed in the Users table. You can do so by clicking on **Edit Columns** and selecting / deselecting the profile properties you wish to display on the User table
+You may wish to change what data is displayed in the Users table. You can do so by clicking on **Edit Columns** and selecting / deselecting the profile properties you wish to display on the User table
@@ -44,12 +44,12 @@ You may wish to change what data is displayed in the Users table. You can do so
### How do I create a cohort out of a list of user emails I have?
-To upload a group of user (or group) profiles and easily sort them into a cohort, add a value to the CSV which sorts the profiles into a cohort as a property. For example, give each profile the unique property of "Cohort = Android Users". Next, go to the [Cohorts](/docs/users/cohorts#creating-cohorts) tab to create a cohort as usual, and filter to user profiles with that property and save. This will create a cohort of users with that matching property.
+To upload a group of user (or group) profiles and easily sort them into a cohort, add a value to the CSV which sorts the profiles into a cohort as a property. For example, give each profile the unique property of "Cohort = Android Users". Next, go to the [Cohorts](/docs/users/cohorts#creating-cohorts) tab to create a cohort as usual, and filter to user profiles with that property and save. This will create a cohort of users with that matching property.
Note that when creating cohorts this way, the cohort will remain static, meaning that it will not update over time like other cohorts as the property is unchanging.
### How do I download User Profiles in Mixpanel?
-To download your user profiles from the Users page, simply click the **Export icon.** This will download all the profile data being displayed in the current report - to download more properties, edit your columns to select more properties. You can choose to filter the list or select individual profiles to download instead of downloading the full list.
+To download your user profiles from the Users page, simply click the **Export icon.** This will download all the profile data being displayed in the current report - to download more properties, edit your columns to select more properties. You can choose to filter the list or select individual profiles to download instead of downloading the full list.
diff --git a/pages/guides/launch/create-boards.mdx b/pages/guides/launch/create-boards.mdx
index 9f97fac512..375f5fe9a5 100644
--- a/pages/guides/launch/create-boards.mdx
+++ b/pages/guides/launch/create-boards.mdx
@@ -21,8 +21,8 @@ If you're new to your company or product analytics in general, one of the best w
3. Our Mixpanel Customer Success Team have also created boards in our demo projects that you can copy into your own projects. These include [boards to help with monitoring the quality of the data](https://mixpanel.com/project/3018488/view/3536632/app/boards/#id=6664368) you bring into Mixpanel, and [boards for troubleshooting your data](https://mixpanel.com/project/3018488/view/3536632/app/boards/#id=6664372).
## Creating and Sharing Your Board
-Once you've created your own board, you can [share](/docs/boards/advanced#sharing) it with your coworkers within your organization for them to view or add creators to it and start collaborating. They need to have a Mixpanel login to access these boards.
+Once you've created your own board, you can [share](/docs/boards/sharing-and-permission) it with your coworkers within your organization for them to view or add creators to it and start collaborating. They need to have a Mixpanel login to access these boards.
If you want to share the board outside of your organization (anyone without a Mixpanel login to your project), you can do so via [public boards](/docs/boards/public-boards). Note that your Project Owner has to first enable the feature in your [Project Settings](https://mixpanel.com/settings/project), but once done, all project users except those with the role "Consumers" will be able to create public board links.
-In certain instances, e.g. communication with your executives, you might want to send an email of the top metrics instead of links to the live board itself. You can do that via [Board Subscriptions](/docs/boards/advanced#board-subscriptions). These emails, which can also be sent as Slack messages, allow you to schedule and share the most recent metrics with both project members and external audiences.
+In certain instances, e.g. communication with your executives, you might want to send an email of the top metrics instead of links to the live board itself. You can do that via [Board Subscriptions](/docs/boards#board-subscriptions). These emails, which can also be sent as Slack messages, allow you to schedule and share the most recent metrics with both project members and external audiences.
diff --git a/pages/guides/playbooks/project-migration.md b/pages/guides/playbooks/project-migration.md
index fd847e4910..e21e969a43 100644
--- a/pages/guides/playbooks/project-migration.md
+++ b/pages/guides/playbooks/project-migration.md
@@ -405,7 +405,7 @@ Saved entities, such as reports, boards, custom events, custom properties, cohor
💡 **Best Practices:**
- **Prioritize Key Entities:** Focus on migrating the most important and frequently used entities first to ensure critical business functions continue uninterrupted.
- **Collaborate with Stakeholders:** Involve key stakeholders throughout the migration process to ensure that their needs are met and that the migrated entities align with their expectations.
-- **Boards & Reports**: Utilize [Move](/docs/boards/advanced#move-board) to transfer saved boards and reports across the same region (i.e. US, EU data centers). Permissions are managed by group admins allowing Boards to be moved across Projects or Organizations, depending on your use case.
+- **Boards & Reports**: Utilize [Move](/docs/boards/move-boards) to transfer saved boards and reports across the same region (i.e. US, EU data centers). Permissions are managed by group admins allowing Boards to be moved across Projects or Organizations, depending on your use case.
- Move does not support the migration of custom events, custom properties, cohorts, and lexicon metadata. This would need to be done manually. Review these lists with stakeholders and decide if any of these saved entities would need to be recreated in the new project to set your end users up for success.
- Lexicon metadata can be [retrieved](https://developer.mixpanel.com/reference/list-all-schemas-for-project) from existing projects and [recreated](https://developer.mixpanel.com/reference/upload-schemas-for-project) in the new project via our Lexicon Schemas API.
diff --git a/redirects/local.txt b/redirects/local.txt
index 4bbd7e0f46..6c91508586 100644
--- a/redirects/local.txt
+++ b/redirects/local.txt
@@ -265,3 +265,4 @@
/docs/features/revenue_analytics /guides/launch/revenue-analytics
/docs/tracking-methods/data-warehouse#mirror /docs/tracking-methods/warehouse-connectors#mirror
/docs/tracking-methods/data-warehouse /docs/tracking-methods/warehouse-connectors
+/docs/boards/advanced /docs/boards
\ No newline at end of file