diff --git a/docs/user-guide/client-management/upgrading-a-plan.md b/docs/user-guide/client-management/upgrading-a-plan.md index d203a3d612..829eb674d5 100644 --- a/docs/user-guide/client-management/upgrading-a-plan.md +++ b/docs/user-guide/client-management/upgrading-a-plan.md @@ -13,27 +13,27 @@ In this tutorial we will cover how they can upgrade their plan and what happens To upgrade their plan, your customers should access their dashboard and go to the **Account** page. -![Customer dashboard with Account page link](/img/admin/memberships-list.png) +![Customer subsite dashboard with Account menu link visible](/img/account-page/account-menu.png) On the Account page, they will be shown their current membership and the plan associated with it. To upgrade to another plan, they must click on **Change** on the top-right corner of **Your Membership** section. -![Your Membership section with Change button](/img/admin/memberships-list.png) +![Account page Your Membership card with Change button](/img/account-page/membership-change-button.png) They will be redirected to a checkout form where all the available plans will be displayed. They will also be able to see the **services and packages available for their current plan** , in case they just want to purchase a specific service or package (like unlimited visits or disk space in our example here), and not upgrade the plan. -![Checkout form showing available plans and packages](/img/admin/memberships-list.png) +![Upgrade picker showing available plans and packages on the customer side](/img/account-page/upgrade-picker.png) After they choose the product they want to purchase, they will see how much they will need to pay right now - excluding any existing credit - and how much they will be charged on the next billing date. Usually, if the product is another plan and the payment is going to be made between a membership charge, they will receive a credit for the amount paid on the first plan. -![Upgrade payment summary with credit and next billing amount](/img/admin/memberships-list.png) +![Upgrade payment summary showing credit applied and next billing amount](/img/account-page/upgrade-summary.png) If they select a plan or package that will not change anything from the current subscription, they will see a message explaining that. -![Message when selected plan does not change the subscription](/img/admin/memberships-list.png) +![Notice when the selected plan does not change the subscription](/img/account-page/upgrade-no-change.png) After the checkout is completed, the new product(s) will be added to your customers' account and all the limits or features of the new product(s) will be instantly added to it: visits, disk space, posts, etc... @@ -47,12 +47,12 @@ On each of your products, you'll have an **Up & Downgrades** tab. The first opti **Plan groups** is what allows you to let Ultimate Multisite know that certain plans belong to the same "family", and therefore should be used to construct upgrade/downgrade path options. -![Up and Downgrades tab with Plan Group field](/img/config/product-upgrades.png) +![Product edit Up and Downgrades tab with Plan Group field](/img/config/product-upgrades-plan-group.png) For example, you have a **Free plan** , a **Basic Plan** and a **Premium Plan** available. You want users subscribed under the **Free Plan** to be able to upgrade only to the **Premium Plan** and you do not want them to see the "Basic Plan" as an upgrade option. All you need to do is assign the same plan group name for both Free and Premium plans as shown in the screenshots below. -![Free Plan with High End plan group assigned](/img/config/product-upgrades.png) +![Free Plan product page with High End plan group assigned](/img/config/product-upgrades-free.png) -![Premium Plan with High End plan group assigned](/img/config/product-upgrades.png) +![Premium Plan product page with High End plan group assigned](/img/config/product-upgrades-premium.png) What this should do is tell Ultimate Multisite that there is a "family" of plans in the network called **High End**. When offering upgrades or downgrades, only plans from the same family will be presented as an option for the user. diff --git a/static/img/account-page/upgrade-no-change.png b/static/img/account-page/upgrade-no-change.png new file mode 100644 index 0000000000..4bdff9a0d7 Binary files /dev/null and b/static/img/account-page/upgrade-no-change.png differ diff --git a/static/img/account-page/upgrade-picker.png b/static/img/account-page/upgrade-picker.png new file mode 100644 index 0000000000..ab7e566a3b Binary files /dev/null and b/static/img/account-page/upgrade-picker.png differ diff --git a/static/img/account-page/upgrade-summary.png b/static/img/account-page/upgrade-summary.png new file mode 100644 index 0000000000..fa3ec955d4 Binary files /dev/null and b/static/img/account-page/upgrade-summary.png differ diff --git a/static/img/config/product-upgrades-free.png b/static/img/config/product-upgrades-free.png new file mode 100644 index 0000000000..089524ad3a Binary files /dev/null and b/static/img/config/product-upgrades-free.png differ diff --git a/static/img/config/product-upgrades-plan-group.png b/static/img/config/product-upgrades-plan-group.png new file mode 100644 index 0000000000..ee340c83ef Binary files /dev/null and b/static/img/config/product-upgrades-plan-group.png differ diff --git a/static/img/config/product-upgrades-premium.png b/static/img/config/product-upgrades-premium.png new file mode 100644 index 0000000000..76bebaa0b4 Binary files /dev/null and b/static/img/config/product-upgrades-premium.png differ