Merge pull request #9636 from circleci/DOCSS-1930-unregistered-users

Unregistered user charging changes

Author: rosieyohannan

docs/guides/modules/ROOT/partials/faq/billing-faq-snip.adoc

@@ -19,19 +19,30 @@ You can choose to pay for premium features per active user, compute, and optiona
 
 * Access to features, such as new machine sizes, are paid with a monthly fee of 25,000 credits per active user (not including applicable taxes).
 * Compute is paid for monthly in credits for the machine size and duration you use:
- ** Credits are sold in packages of 25,000 at $15 each (not including applicable taxes).
- ** Credits rollover each month and expire after one year.
-* Docker Layer Caching (DLC) is paid for with credits per usage, similar to
-compute credits.
-* You can find the full explanation of how credits and features are priced link:https://circleci.com/pricing/[here on our pricing page].
+** Credits are sold in packages of 25,000 at $15 each (not including applicable taxes).
+** Credits roll over each month and expire after one year.
+* Docker Layer Caching (DLC) is paid for with credits per usage, similar to compute credits.
+* You can find a full explanation of how credits and features are priced link:https://circleci.com/pricing/[here on our pricing page].
 
 [#run-out-of-credits]
 === What happens when I run out of credits?
 
-On the *Performance Plan*, when you reach 0 credits, you will be refilled approximately 25% of your credit subscription, with a minimum refill of 25,000 credits. For example, if your monthly package size is 100,000 credits, you will automatically be refilled 25,000 credits (at $.0006 each, not including applicable taxes) when you reach 2000 remaining credits.
+On the *Performance Plan*, when you reach 0 credits, you will be refilled approximately 25% of your credit subscription, with a minimum refill of 25,000 credits. For example, if your monthly package size is 100,000 credits, you will automatically be refilled 25,000 credits when you reach 0 remaining credits. Credits are priced at $.0006 each, not including applicable taxes.
 
 If you notice that your account is receiving repeated refills, review your credit usage by logging in to the CircleCI web app, then select menu:Plan[Plan Usage]. In most cases, increasing your credit package should minimize repeat refills. You can manage your plan by clicking `Plan Overview`.
 
+On the *Scale/Custom Plan*, you have the option to agree to use Credit Auto-Refill (CAR). When your usage gets to 20% of credit purchase, you receive a notice that credit is getting low. If your credit gets to 10%, and you have not made another purchase, you receive a refill of either 25% (default) or 10% of your credit purchase.
+
+For example:
+
+. You buy 100M credits.
+. Get notice at 20M credits.
+. CAR at 10M credits.
+
+CAR can be interrupted with a supplemental purchase.
+
+You can decline CAR, but you will not get a notice at 20%, and if your credits deplete to 0, your service will be interrupted until you make another purchase.
+
 On the *Free Plan*, jobs will fail to run once you have run out of credits.
 
 [#do-credits-expire]
@@ -102,7 +113,7 @@ Yes, all prepaid billing customers still receive the benefit of 30,000 credits a
 
 Yes, log in to the CircleCI web app, then navigate to menu:Plan[Share & Transfer].
 
-On non-free plans, you can share your plan with free organizations for which you have admin access using the `Add Shared Organization` option. All orgs you have shared your plan with will then be listed on the Share & Transfer page and child organizations will bill all credits and other usage to the parent org.
+On non-free plans, you can share your plan with free organizations for which you have admin access using the `Add Shared Organization` option. All orgs you have shared your plan with are listed on the Share & Transfer page. Child organizations will bill all credits and other usage to the parent org.
 
 On non-free plans, you can transfer your plan to another free organization for which you have admin access using the `Transfer Plan` option. When you transfer a paid plan to another org, your org will be downgraded to the Free Plan.
 
@@ -196,11 +207,11 @@ CircleCI no longer offers discounts for open source customers on the Performance
 
 Docker layer caching (DLC) reduces build times on pipelines where Docker images are built by only rebuilding Docker layers that have changed (read more on the xref:guides:optimize:docker-layer-caching.adoc[Docker Layer Caching] page). DLC costs 200 credits per job run.
 
-To estimate your DLC cost, look at the jobs in your config file with Docker layer caching enabled, and the number of Docker images you are building in those jobs. There are cases where a job can be written once in a config file but the job runs multiple times in a pipeline, for example, with parallelism enabled.
+To estimate your DLC cost, look at the jobs in your config file with Docker layer caching enabled, and the number of Docker images you are building in those jobs. In some cases, a job that appears only once in a config file can run multiple times in a pipeline. For example, with parallelism enabled.
 
 Note that the benefits of Docker layer caching are only apparent on pipelines that are building Docker images, and reduces image build times by reusing the unchanged layers of the application image built during your job. If your pipeline does not include a job where Docker images are built, Docker layer caching will provide no benefit.
 
 [#support-plan-info]
 === What does a paid support plan include?
 
-By purchasing a paid support plan with CircleCI, you can change the response time from our Support team to be as low as 30 minutes, with a 24 x 7 coverage plan, to ensure that any issues you have while using CircleCI are investigated as quickly as possible. For more information, link:https://support.circleci.com/hc/en-us/articles/4415357235995-Support-Plans-Priority-Response[refer to this support article].
+By purchasing a 24 x 7 coverage support plan with CircleCI, you can change the response time from our Support team to be as low as 30 minutes. This ensures that any issues you have while using CircleCI are investigated as quickly as possible. For more information, link:https://support.circleci.com/hc/en-us/articles/4415357235995-Support-Plans-Priority-Response[refer to this support article].

docs/guides/modules/plans-pricing/pages/plan-performance.adoc

@@ -12,7 +12,7 @@ The Performance Plan offers a set number of credits across a variety of resource
 
 The Performance Plan offers a higher amount of network usage, and other advantages over the Free Plan, as described below.
 
-The Performance Plan offers *five* link:https://support.circleci.com/hc/en-us/articles/360034783154-What-is-an-Active-User[active users], and you can increase this number as you grow. Each additional user is charges at 25,000 credits. Refer to the link:https://circleci.com/pricing#[pricing page] for details.
+The Performance Plan offers *five* link:https://support.circleci.com/hc/en-us/articles/360034783154-What-is-an-Active-User[active users], and you can increase this number as you grow. Each additional user is charged at 25,000 credits. Refer to the link:https://circleci.com/pricing[pricing page] for details.
 
 [#access-to-ip-ranges]
 === Access to IP ranges

docs/guides/modules/plans-pricing/pages/plan-scale.adoc

@@ -25,11 +25,11 @@ For more information about these resources, refer to the xref:execution-managed:
 
 [#custom-concurrency]
 === Custom concurrency
-Customize the amount of jobs you need to run concurrently. This customization is available on all build configurations and execution environments. See <<#concurrency,Concurrency>> below for more information.
+Customize the number of jobs you need to run concurrently. This customization is available on all build configurations and execution environments. See <<#concurrency,Concurrency>> below for more information.
 
 [#custom-user-seat-count]
 === Custom user seat count
-Customize the amount of active users based on your needs.
+Customize the number of active users based on your needs.
 
 [#unlimited-self-hosted-runners]
 === Unlimited self-hosted runners

docs/guides/modules/plans-pricing/pages/plan-server.adoc

@@ -9,15 +9,21 @@ This document describes the Server Plan available to developers.
 
 [#server-plan]
 == Server Plan
-CircleCI server is an on-premises CI/CD platform for enterprise customers who have compliance or security needs that require them to operate within their firewall, in a private cloud, or in a data center. See the xref:server-admin:overview:circleci-server-overview.adoc[Server documentation] for more information.
+CircleCI server is an on-premises CI/CD platform for enterprise customers who have compliance or security needs that require operation:
+
+* Within a firewall.
+* In a private cloud.
+* In a data center.
+
+See the xref:server-admin:overview:circleci-server-overview.adoc[Server documentation] for more information.
 
 The Server Plan offers custom credit options that can be used across all CircleCI resource classes, per month, depending on your build configuration and execution environment.
 
 The Server Plan gives you access to a few additional upgrades over some of the other plans:
 
 [#custom-user-seat-count]
 === Custom user seat count
-Customize the amount of active users based on your needs.
+Customize the number of active users based on your needs.
 
 [#custom-storage-retention]
 === Custom storage retention

docs/guides/modules/plans-pricing/pages/prevent-unregistered-users-from-spending-credits.adoc

@@ -3,33 +3,33 @@
 :page-description: A how to guide to configuring your org so that unregistered users will not be able to perform actions that spend credits
 :experimental:
 
-It is possible for _unregistered_ users to trigger pipelines, and therefore, spend credits. Use the **Prevent unregistered user spend** option to only allow registered users the ability to trigger work that consumes credits. For a full breakdown of the various ways pipelines can be triggered, see the xref:orchestrate:triggers-overview.adoc[Triggers overview].
+Unregistered users trigger pipelines, spend credits and count towards your plan usage. You can choose to use the **Prevent unregistered user spend** option to only allow registered (users with a CircleCI account) users the ability to trigger work that consumes credits. For a full breakdown of the various ways pipelines can be triggered, see the xref:orchestrate:triggers-overview.adoc[Triggers overview].
 
 ****
-An _unregistered_ user is how CircleCI tracks users who have triggered builds but have not signed up for a CircleCI account. Unregistered user activity within an org is mapped to, and counts as, a single link:https://support.circleci.com/hc/en-us/articles/360034783154[active user].
+*Unregistered users* are how CircleCI track users who have triggered builds but have not signed up for a CircleCI account. Each unregistered user within an org is mapped to, and counts as, a single link:https://support.circleci.com/hc/en-us/articles/360034783154[active user]. Unregistered users count towards your plan usage.
 
 For more information about unregistered users, see this link:https://support.circleci.com/hc/en-us/articles/360037744473-What-is-an-Unregistered-User-[support article]
 ****
 
 [#prerequisites]
 == Prerequisites
 
-* A CircleCI account connected to your code. You can link:https://circleci.com/signup/[sign up for free]
-* You must be on the link:https://circleci.com/pricing/[Performance or Scale Plan]
-* You must be an org admin
+* A CircleCI account connected to your code. You can link:https://circleci.com/signup/[sign up for free].
+* You must be on the link:https://circleci.com/pricing/[Performance or Scale Plan].
+* You must be an org admin.
 
 [#steps]
 == Steps
 
 Follow these steps to prevent unregistered users from triggering work that consumes credits:
 
-. In the CircleCI web app, click btn:[Plan] in the sidebar
+. In the link:https://app.circleci.com/[CircleCI web app], select *Plan* in the sidebar.
 . Select the **Usage Controls** tab. If you do not see this option you might be on the Free Plan, or you may not be an org admin, in which case this guide does not apply to you.
-. Click the switch for the **Prevent unregistered user spend** option to "On"
+. Select **Prevent unregistered user spend** option to switch it to "On".
 
 To disable this feature you can toggle this switch "Off" at any time.
 
-With this option enabled, any unregistered users, that is, users who do not have a CircleCI account, and who are not associated with your org, will see the following if they attempt to trigger a pipeline:
+Once enabled, any unregistered users, that is, users who do not have a CircleCI account, will see the following if they attempt to trigger a pipeline:
 
-* The pipeline will fail to start
+* The pipeline will fail to start.
 * The `block-unregistered-user` error will be displayed in a banner on the dashboard