From 23f66b2d02ab97ff0e908a09e4b899962cd842ff Mon Sep 17 00:00:00 2001 From: christophe perrin Date: Mon, 2 Jun 2025 14:56:09 +0200 Subject: [PATCH 1/7] added managing team entry in wiki --- docs/web-console-docs/managing-teams.mdx | 72 ++++++++++++++++++++++++ 1 file changed, 72 insertions(+) create mode 100644 docs/web-console-docs/managing-teams.mdx diff --git a/docs/web-console-docs/managing-teams.mdx b/docs/web-console-docs/managing-teams.mdx new file mode 100644 index 00000000..fc2f406f --- /dev/null +++ b/docs/web-console-docs/managing-teams.mdx @@ -0,0 +1,72 @@ +sidebar_position: 16 +--- + +# Guide to creating and managing teams + +Manage your organisation's structure by creating teams, assigning users, and setting up hierarchical relationships between teams. +Teams help isolate access to content and provide a more relevant experience for users in large organisations. + +## Creating a team + +To create a new team: + +1. Navigate to **Settings → Teams**. +2. Click the **Create team** button in the top right. +3. In the form: + - **Team name**: Enter a unique name for the team. + - **Initials**: Customise the abbreviation shown in the team tree and content owned by the team. + - **Colour**: Pick a colour to help visually distinguish this team. + - **Parent team**: Choose where this team belongs in the organisational hierarchy. + - Teams can have only **one parent**. + - Teams are all children of the top level team representing your organisation. + - **Team focus and mission**: Describe what the team does. + +4. Click **Create team** to add the team to the hierarchy. + +INFO You must have the relevant permissions (`Team admin` or `Team create`) to create a team. + +## Managing team members + +From a team's detail page: + +1. Use the **Add** button in the "Members" section to add users to the team. +2. Search for a user by name or email and click to add them. +3. Added users become **direct members** of the selected team. + +### Implicit membership + +Users assigned to a team are also **implicitly members of all its parent teams**. +This allows parent teams to automatically include members from all their child teams. + +- Implicit members are shown with the label `Inherited member`. +- You cannot remove implicit members from a parent team — you must remove them from their direct team instead. + +## Editing or archiving teams + +To update a team: + +- Click **Edit** in the team’s detail view to change its name, description, or initials. + +To archive a team: + +- Click the `...` menu in the team card and select **Archive**. +- Confirm the action in the modal. Archived teams are hidden from the team hierarchy by default. +- The top level team representing the entire organisation cannot be archived. + +## Moving a team + +You can change the parent of a team to reorganise your hierarchy: + +1. Open the team you want to move. +2. Click the `...` menu and select **Move**. +3. Choose a new parent from the dropdown list. +4. Confirm the move. + + +## Viewing the company hierarchy + +The left-hand panel shows the full **team hierarchy**: +- Expand/collapse nodes to navigate deeper levels. +- Archived teams can be toggled using the **Show/hide archived** switch. + +Click any team to view its members, child teams, and details. \ No newline at end of file From abdbbefe75048f00e766be576d83eec19265a9a9 Mon Sep 17 00:00:00 2001 From: christophe perrin Date: Mon, 2 Jun 2025 15:11:15 +0200 Subject: [PATCH 2/7] Fixed a few typos --- docs/web-console-docs/managing-teams.mdx | 20 +++++++++++++++----- 1 file changed, 15 insertions(+), 5 deletions(-) diff --git a/docs/web-console-docs/managing-teams.mdx b/docs/web-console-docs/managing-teams.mdx index fc2f406f..834422f5 100644 --- a/docs/web-console-docs/managing-teams.mdx +++ b/docs/web-console-docs/managing-teams.mdx @@ -1,3 +1,4 @@ +--- sidebar_position: 16 --- @@ -18,12 +19,14 @@ To create a new team: - **Colour**: Pick a colour to help visually distinguish this team. - **Parent team**: Choose where this team belongs in the organisational hierarchy. - Teams can have only **one parent**. - - Teams are all children of the top level team representing your organisation. + - Teams are all children of the top-level team representing your organisation. - **Team focus and mission**: Describe what the team does. 4. Click **Create team** to add the team to the hierarchy. -INFO You must have the relevant permissions (`Team admin` or `Team create`) to create a team. +:::info +You must have the relevant permissions (`Team admin` or `Team create`) to create a team. +::: ## Managing team members @@ -51,7 +54,11 @@ To archive a team: - Click the `...` menu in the team card and select **Archive**. - Confirm the action in the modal. Archived teams are hidden from the team hierarchy by default. -- The top level team representing the entire organisation cannot be archived. +- The top-level team representing the entire organisation cannot be archived. + +:::info +You must have the relevant permissions (`Team admin` or `Team edit`) to manage a team. +::: ## Moving a team @@ -62,10 +69,13 @@ You can change the parent of a team to reorganise your hierarchy: 3. Choose a new parent from the dropdown list. 4. Confirm the move. +:::info +You must have the relevant permissions (`Team admin` or `Team edit`) to move a team. +::: -## Viewing the company hierarchy +## Viewing the team hierarchy -The left-hand panel shows the full **team hierarchy**: +The left-hand panel shows the full **team hierarchy** for your organisation: - Expand/collapse nodes to navigate deeper levels. - Archived teams can be toggled using the **Show/hide archived** switch. From df020e285a73d921311977198f3c4fab69227b90 Mon Sep 17 00:00:00 2001 From: christophe perrin Date: Mon, 2 Jun 2025 15:13:41 +0200 Subject: [PATCH 3/7] and more typos --- docs/web-console-docs/managing-teams.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/web-console-docs/managing-teams.mdx b/docs/web-console-docs/managing-teams.mdx index 834422f5..cf096ef2 100644 --- a/docs/web-console-docs/managing-teams.mdx +++ b/docs/web-console-docs/managing-teams.mdx @@ -2,7 +2,7 @@ sidebar_position: 16 --- -# Guide to creating and managing teams +# Creating and managing teams Manage your organisation's structure by creating teams, assigning users, and setting up hierarchical relationships between teams. Teams help isolate access to content and provide a more relevant experience for users in large organisations. From 201b2c3e93971984aa9f45c8b8586f6354c50f8a Mon Sep 17 00:00:00 2001 From: christophe perrin Date: Mon, 2 Jun 2025 15:18:36 +0200 Subject: [PATCH 4/7] change file name to refect the H1 --- docs/web-console-docs/managing-teams.mdx | 82 ------------------------ 1 file changed, 82 deletions(-) delete mode 100644 docs/web-console-docs/managing-teams.mdx diff --git a/docs/web-console-docs/managing-teams.mdx b/docs/web-console-docs/managing-teams.mdx deleted file mode 100644 index cf096ef2..00000000 --- a/docs/web-console-docs/managing-teams.mdx +++ /dev/null @@ -1,82 +0,0 @@ ---- -sidebar_position: 16 ---- - -# Creating and managing teams - -Manage your organisation's structure by creating teams, assigning users, and setting up hierarchical relationships between teams. -Teams help isolate access to content and provide a more relevant experience for users in large organisations. - -## Creating a team - -To create a new team: - -1. Navigate to **Settings → Teams**. -2. Click the **Create team** button in the top right. -3. In the form: - - **Team name**: Enter a unique name for the team. - - **Initials**: Customise the abbreviation shown in the team tree and content owned by the team. - - **Colour**: Pick a colour to help visually distinguish this team. - - **Parent team**: Choose where this team belongs in the organisational hierarchy. - - Teams can have only **one parent**. - - Teams are all children of the top-level team representing your organisation. - - **Team focus and mission**: Describe what the team does. - -4. Click **Create team** to add the team to the hierarchy. - -:::info -You must have the relevant permissions (`Team admin` or `Team create`) to create a team. -::: - -## Managing team members - -From a team's detail page: - -1. Use the **Add** button in the "Members" section to add users to the team. -2. Search for a user by name or email and click to add them. -3. Added users become **direct members** of the selected team. - -### Implicit membership - -Users assigned to a team are also **implicitly members of all its parent teams**. -This allows parent teams to automatically include members from all their child teams. - -- Implicit members are shown with the label `Inherited member`. -- You cannot remove implicit members from a parent team — you must remove them from their direct team instead. - -## Editing or archiving teams - -To update a team: - -- Click **Edit** in the team’s detail view to change its name, description, or initials. - -To archive a team: - -- Click the `...` menu in the team card and select **Archive**. -- Confirm the action in the modal. Archived teams are hidden from the team hierarchy by default. -- The top-level team representing the entire organisation cannot be archived. - -:::info -You must have the relevant permissions (`Team admin` or `Team edit`) to manage a team. -::: - -## Moving a team - -You can change the parent of a team to reorganise your hierarchy: - -1. Open the team you want to move. -2. Click the `...` menu and select **Move**. -3. Choose a new parent from the dropdown list. -4. Confirm the move. - -:::info -You must have the relevant permissions (`Team admin` or `Team edit`) to move a team. -::: - -## Viewing the team hierarchy - -The left-hand panel shows the full **team hierarchy** for your organisation: -- Expand/collapse nodes to navigate deeper levels. -- Archived teams can be toggled using the **Show/hide archived** switch. - -Click any team to view its members, child teams, and details. \ No newline at end of file From 2b59ef4801f5597964be669c0702aa675c097168 Mon Sep 17 00:00:00 2001 From: christophe perrin Date: Mon, 7 Jul 2025 10:34:53 +0200 Subject: [PATCH 5/7] fixed some typo --- .../Interpreting-metrics-in-experiment-results.mdx | 2 +- docs/web-console-docs/events.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/web-console-docs/Interpreting-metrics-in-experiment-results.mdx b/docs/web-console-docs/Interpreting-metrics-in-experiment-results.mdx index 0682c245..d0162212 100644 --- a/docs/web-console-docs/Interpreting-metrics-in-experiment-results.mdx +++ b/docs/web-console-docs/Interpreting-metrics-in-experiment-results.mdx @@ -97,7 +97,7 @@ Group Sequential Testing, makes it easy to visually interpret results. The graph --- ### Interpreting the Boundaries -1. **Efficiency Boundary (Green)**: +1. **Efficacy Boundary (Green)**: - Crossing this boundary means there is enough evidence to conclude the variant performs significantly better than the baseline. - The experiment can be stopped early, and the variant can be considered successful. diff --git a/docs/web-console-docs/events.mdx b/docs/web-console-docs/events.mdx index 243d6e75..415b36d7 100644 --- a/docs/web-console-docs/events.mdx +++ b/docs/web-console-docs/events.mdx @@ -11,7 +11,7 @@ code and the Web Console. To access it, select `Events` from the sidebar and choose `All`. :::info -If you want to **export ALL the exposure and goal events for a single experiment**, you can do it directly from the experiment overview page by clicking on the ... menu and seleting **Export data**. +If you want to **export ALL the exposure and goal events for a single experiment**, you can do it directly from the experiment overview page by clicking on the ... menu and selecting **Export data**. ::: ## The Events List From f1c4049478320e0e7f1bc8b794eca99972e18e50 Mon Sep 17 00:00:00 2001 From: christophe perrin Date: Mon, 7 Jul 2025 11:26:45 +0200 Subject: [PATCH 6/7] Added July release notes --- docs/platform-release-notes/2025/02.mdx | 6 ++++ docs/platform-release-notes/2025/03.mdx | 11 +++++++- docs/platform-release-notes/2025/04.mdx | 7 +++++ docs/platform-release-notes/2025/05.mdx | 7 +++++ docs/platform-release-notes/2025/06.mdx | 11 ++++++++ docs/platform-release-notes/2025/07.mdx | 37 +++++++++++++++++++++++++ 6 files changed, 78 insertions(+), 1 deletion(-) create mode 100644 docs/platform-release-notes/2025/07.mdx diff --git a/docs/platform-release-notes/2025/02.mdx b/docs/platform-release-notes/2025/02.mdx index 80084ba8..d991d4d9 100644 --- a/docs/platform-release-notes/2025/02.mdx +++ b/docs/platform-release-notes/2025/02.mdx @@ -5,6 +5,8 @@ enhancements based on customer feedback and QA reports. Additionally, we're excited to introduce the **beta version of our new Velocity Report**, designed to help you track your experimentation program more effectively. +--- + ## Beta Feature: Velocity Report We're introducing the @@ -21,6 +23,8 @@ experimentation process. would you like to see on the report? Let us know so we can improve it together. +--- + ## Bug Fixes & Improvements This release includes **50+ bug fixes and small improvements** reported by @@ -51,6 +55,8 @@ our customers and QA team. Here are some key updates: These updates enhance platform stability, performance, and usability to make experimentation even smoother. +--- + ## Feedback & Next Steps Your input is invaluable! If you have thoughts on the diff --git a/docs/platform-release-notes/2025/03.mdx b/docs/platform-release-notes/2025/03.mdx index 44764d01..57332b76 100644 --- a/docs/platform-release-notes/2025/03.mdx +++ b/docs/platform-release-notes/2025/03.mdx @@ -1,10 +1,13 @@ # March 2025 -This March release focuses mainly on our reports by improving the +## Overview + This release focuses mainly on our reports by improving the **Velocity Report** and launching the new **Decisions Report**. Both of those reports will help you get a better overview and track your experimentation program more effectively. +--- + ## Velocity Report updates In this release we focused on improving the Velocity Report which we launched @@ -23,6 +26,8 @@ key updates: On as well as early stops, we renamed the **Aborted** widget to **Not completed**. +--- + ## Beta Feature: Decisions Report After the Velocity Report, we are also excited to launch the second part @@ -43,6 +48,8 @@ past decisions. your feedback on this first release of the Decisions Report so we can make it right for you. +--- + ## Experiment Dashboard redesign We are working on a new improved version of one of the most important @@ -60,6 +67,8 @@ decisions. - **What's next?** Give us your feedback below or send it to [support@absmartly.com](mailto:support@absmartly.com). +--- + ## Feedback & Next Steps We want to build the best possible experimentation platform for you so if diff --git a/docs/platform-release-notes/2025/04.mdx b/docs/platform-release-notes/2025/04.mdx index d04e87e8..864affa6 100644 --- a/docs/platform-release-notes/2025/04.mdx +++ b/docs/platform-release-notes/2025/04.mdx @@ -1,9 +1,12 @@ # April 2025 +## Overview Overview In this new release we mainly focused on improvement to the **Velocity **and **Decisions Reports**. All those improvements are driven by feedback we received from you so keep them coming. Here are some of the most important updates. +--- + ## Velocity Report - **Aggregate data per quarter:** To help you run your quarterly experimentation reports we made it possible to aggregate the data per quarter (previously you could only aggregate per year, month or week). @@ -12,6 +15,8 @@ In this new release we mainly focused on improvement to the **Velocity **and  **Stay tuned**: One of the main feature requests we received for the Velocity Report is to be able to open the list of experiments in each report. We are hoping to introduce this feature in one of our upcoming releases. +--- + ## Decisions Report Earlier this month we launched the new [Decisions Reports (Beta)](/docs/web-console-docs/experiment-reports/#decisions-overview). In this release we are introducing a few improvements to provide better insights into each decision. @@ -19,6 +24,8 @@ Earlier this month we launched the new [Decisions Reports (Beta)](/docs/web-con - **Secondary & Guardrail metrics:** Like with the primary metric, you can now see the experiment results on the secondary and guardrail metrics. This helps understand the rationale behind each decision.** - **Health checks:** We are now surfacing any [health check violations](/docs/web-console-docs/Experiment-health-checks) in the reports so you can get better insights into the quality of each decision. +--- + ## Feedback & Next Steps As always we value your feedback so please share with us what you would like to see improve in the future. We have some really exciting new features coming your way in the next few releases so stay tuned. diff --git a/docs/platform-release-notes/2025/05.mdx b/docs/platform-release-notes/2025/05.mdx index c53fae47..39858e44 100644 --- a/docs/platform-release-notes/2025/05.mdx +++ b/docs/platform-release-notes/2025/05.mdx @@ -1,12 +1,17 @@ # May 2025 +## Overview This release focuses on backend improvements and foundational work to support future features. While there are few visible changes for you today, these updates improve platform stability and pave the way for upcoming capabilities. We still managed to squeeze a few improvements to the Velocity report and to the Experiment Dashboard redesign. +--- + ## Velocity Report - **View the list of experiments:** The most requested feature request for the velocity report. You can now click on any graph on the Velocity Report to get the list of experiments included. - **Early stop vs Early full-on:** The Experiments not completed graph now shows the breakdown between the early full-on and early stops. +--- + ## Experiment Dashboard Redesign Our new Experiment Dashboard redesign is still in progress and you can see. The main reason behind this redesign is to consolidate how *Fixed Horizon* and *Group Sequential* experiments are shown and to make it easier for everyone to make quality decisions. In this release we added GST data to the metric's table. Please have a look and let us know what you think. @@ -14,6 +19,8 @@ Our new Experiment Dashboard redesign is still in progress and you can see. The - **How to see it?** Within the dashboard of any existing experiment you will have a *'Load new UI'* button which will enable you to toggle between the old and the new view. - **What’s next?** Give us your feedback below or send it to [support@absmartly.com](mailto:support@absmartly.com). +--- + ## Feedback and Next Steps As always we value your feedback so please share with us what you would like to see improve in the future. We have some really exciting new features coming your way in the next few releases so stay tuned. diff --git a/docs/platform-release-notes/2025/06.mdx b/docs/platform-release-notes/2025/06.mdx index 95964702..f87e19fd 100644 --- a/docs/platform-release-notes/2025/06.mdx +++ b/docs/platform-release-notes/2025/06.mdx @@ -1,7 +1,10 @@ # June 2025 +## Overview Our latest release introduces new features to support better collaboration, data access, and metric/goal discoverability. With foundational Team Management features and a faster way to download experiment data, this update sets the stage for a more streamlined and scalable experimentation experience. +--- + ## New Feature: Team Management (Foundations) Teams become much more than just metadata, you can now properly define and manage teams within the platform. This update allows you to map your internal organizational structure directly into the product by: @@ -12,6 +15,8 @@ Teams become much more than just metadata, you can now properly define and manag This is the first step toward upcoming improvements around ownership, permissions, and team-level collaboration. Go to `Settings > Teams` to get started with managing your team and inviting your team members. If you already have teams defined in ABsmartly, you can simply move them to the right place in your org structure. Check our [wiki page](/docs/web-console-docs/creating-and-managing-teams) for more information on creating and managing teams in ABsmartly. +--- + ## New Feature: One-Click Experiment Data Export We added an **Export data** button to the experiment overview page, allowing you to export participant exposures and goal event data for that experiment with a single click. @@ -29,6 +34,8 @@ We added an **Export data** button to the experiment overview page, allowing you Only users with the Events:List permissions will be able to trigger the export and download the file. +--- + ## Improved Metrics & Goals List Pages Finding the right metrics and goals just got easier. We've enhanced the list pages to: @@ -36,10 +43,14 @@ Finding the right metrics and goals just got easier. We've enhanced the list pag - Improve searchability and filtering (archived vs unarchived) - Help you quickly identify and select the metrics and goals that matter +--- + ## Other Fixes & Improvements This release also includes several smaller enhancements and bug fixes to improve overall platform stability and performance. +--- + ## Feedback and Next Steps As always we value your feedback so please share with us what you would like to see improve in the future. We want to build the right product for you so [reach out to us](mailto:support@absmartly.com) if you want to discuss our roadmap or your specific needs. diff --git a/docs/platform-release-notes/2025/07.mdx b/docs/platform-release-notes/2025/07.mdx new file mode 100644 index 00000000..f4f723a5 --- /dev/null +++ b/docs/platform-release-notes/2025/07.mdx @@ -0,0 +1,37 @@ +# July 2025 + +## Overview +This release introduces a brand-new notification system to help teams stay on top of what matters, along with the official launch of the improved Metrics Overview tab. +These updates are designed to make your workflow more informed, timely, and collaborative. + +--- + +## New Feature: Built-In Notifications +Never miss a key event again. Our new built-in notification system ensures you're always up to date with what's happening on the platform. + +- **Team assignments**: Get notified when you're added/removed to a team +- **Experiment/feature lifecycle updates**: Get alerts when an experiment starts, stops, is put full-on or when a feature is turned on/off. + +More alert types will be added in upcoming releases — stay tuned! + +--- + +## New Feature: Impact per Day Estimates +We've added a new **Impact per Day estimates** on all relevant metric type inside the experiment overview to help you better understand the real-world significance of your experiment results. +This gives you a clearer picture of the **daily impact** your changes could have when rolled out, making it easier to evaluate their practical value. + +--- + +## Metrics Overview Tab Out of Beta +Thanks to all your feedback, the new Metrics Overview tab is now officially out of beta. + +- Cleaner layout and better tooltips and timestamps +- Consolidation of GST and Fixed Horizon experiment results in a single table +- Display impact per day for all relevant metrics +- More actionable information at a glance + +These changes are designed to help you make faster, more informed decisions when reviewing experiment results. + +--- + +Let us know if you have any questions or if you would like to discuss future features with us. From 937465aadf2780e20a845f4a9016f1298cb9fbe9 Mon Sep 17 00:00:00 2001 From: christophe perrin Date: Mon, 7 Jul 2025 11:32:24 +0200 Subject: [PATCH 7/7] remove duplicate word --- docs/platform-release-notes/2025/04.mdx | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/platform-release-notes/2025/04.mdx b/docs/platform-release-notes/2025/04.mdx index 864affa6..fa70a0d4 100644 --- a/docs/platform-release-notes/2025/04.mdx +++ b/docs/platform-release-notes/2025/04.mdx @@ -1,7 +1,6 @@ # April 2025 ## Overview -Overview In this new release we mainly focused on improvement to the **Velocity **and **Decisions Reports**. All those improvements are driven by feedback we received from you so keep them coming. Here are some of the most important updates.