Direct answer: Confluence Standard or Premium can move to Free only after the site meets the Free user limit. Existing content remains, but important permission and collaboration controls change, while Atlassian refund eligibility is limited to qualifying initial purchases rather than routine renewals.
A Confluence cancellation should be treated as a transaction-specific workflow. Start with “Ten-user threshold matters”: Atlassian says a Confluence site with more than 10 users cannot switch to Free until additional users are removed. Then record the rule behind “Content is retained.” Keeping those two Confluence points visible makes it easier to separate the cancellation action from any refund, credit, fee, access, or equipment result.
Confluence policy checkpoints that control the outcome
Ten-user threshold matters
For Confluence, trace the billing trail tied to “Ten-user threshold matters.” Atlassian says a Confluence site with more than 10 users cannot switch to Free until additional users are removed. That Confluence checkpoint should be read on its own terms before any account, booking, subscription, or service change is submitted.
Use “Content is retained” as the next Confluence marker. When Standard or Premium changes to Free, Confluence keeps the site content rather than treating the plan change as content deletion. Compare the two Confluence markers before acting; the matching Confluence action here is “Count active Confluence users and identify the paid tier.” Save the resulting Confluence confirmation so the later outcome can be checked against both rules.
Content is retained
For Confluence, verify the account history tied to “Content is retained.” When Standard or Premium changes to Free, Confluence keeps the site content rather than treating the plan change as content deletion. That Confluence checkpoint should be read on its own terms before any account, booking, subscription, or service change is submitted.
Use “Permission controls are reduced” as the next Confluence marker. On Free, admins cannot continue editing the same granular permissions and restrictions available on paid tiers, and anonymous access is unavailable. Compare the two Confluence markers before acting; the matching Confluence action here is “Remove or suspend enough users to meet the Free threshold if needed.” Save the resulting Confluence confirmation so the later outcome can be checked against both rules.
Permission controls are reduced
For Confluence, match the booking file tied to “Permission controls are reduced.” On Free, admins cannot continue editing the same granular permissions and restrictions available on paid tiers, and anonymous access is unavailable. That Confluence checkpoint should be read on its own terms before any account, booking, subscription, or service change is submitted.
Use “Admin access is required” as the next Confluence marker. A Confluence admin uses Atlassian Billing to manage the subscription and select Free. Compare the two Confluence markers before acting; the matching Confluence action here is “Review space permissions, restrictions, guest access, and anonymous access before the downgrade.” Save the resulting Confluence confirmation so the later outcome can be checked against both rules.
Admin access is required
For Confluence, audit the confirmation set tied to “Admin access is required.” A Confluence admin uses Atlassian Billing to manage the subscription and select Free. That Confluence checkpoint should be read on its own terms before any account, booking, subscription, or service change is submitted.
Use “Initial cloud purchases get limited refund treatment” as the next Confluence marker. Monthly initial subscriptions may qualify during the first paid month after trial and new annual cloud purchases within 30 days. Compare the two Confluence markers before acting; the matching Confluence action here is “Change the plan from the Atlassian billing console and preserve the confirmation.” Save the resulting Confluence confirmation so the later outcome can be checked against both rules.
Initial cloud purchases get limited refund treatment
For Confluence, review the purchase record tied to “Initial cloud purchases get limited refund treatment.” Monthly initial subscriptions may qualify during the first paid month after trial and new annual cloud purchases within 30 days. That Confluence checkpoint should be read on its own terms before any account, booking, subscription, or service change is submitted.
Use “Renewal money is different” as the next Confluence marker. Atlassian says cloud renewals and upgrades are not refundable under its standard refund policy. Compare the two Confluence markers before acting; the matching Confluence action here is “If money is being requested back, evaluate that separately under Atlassian’s initial-purchase refund criteria.” Save the resulting Confluence confirmation so the later outcome can be checked against both rules.
Renewal money is different
For Confluence, confirm the service record tied to “Renewal money is different.” Atlassian says cloud renewals and upgrades are not refundable under its standard refund policy. That Confluence checkpoint should be read on its own terms before any account, booking, subscription, or service change is submitted.
Use “Ten-user threshold matters” as the next Confluence marker. Atlassian says a Confluence site with more than 10 users cannot switch to Free until additional users are removed. Compare the two Confluence markers before acting; the matching Confluence action here is “Count active Confluence users and identify the paid tier.” Save the resulting Confluence confirmation so the later outcome can be checked against both rules.
Confluence policy map at a glance
| Decision point | Official Confluence rule |
|---|---|
| Ten-user threshold matters | Atlassian says a Confluence site with more than 10 users cannot switch to Free until additional users are removed. |
| Content is retained | When Standard or Premium changes to Free, Confluence keeps the site content rather than treating the plan change as content deletion. |
| Permission controls are reduced | On Free, admins cannot continue editing the same granular permissions and restrictions available on paid tiers, and anonymous access is unavailable. |
| Admin access is required | A Confluence admin uses Atlassian Billing to manage the subscription and select Free. |
Real Confluence situations that change the answer
Twelve-user Confluence Premium site
The Confluence case “Twelve-user Confluence Premium site” should not be generalized. The Free change is blocked until the user count is reduced to the allowed threshold.
Its companion Confluence checkpoint is “Permission controls are reduced”: On Free, admins cannot continue editing the same granular permissions and restrictions available on paid tiers, and anonymous access is unavailable. Keep both Confluence details with the transaction record.
Team relies on restricted spaces
Use “Team relies on restricted spaces” as a Confluence case study. The expected timing outcome is: Existing restrictions are retained, but the Free tier limits the ability to edit permission structures afterward.
Now compare this Confluence case with “Admin access is required.” A Confluence admin uses Atlassian Billing to manage the subscription and select Free. That comparison explains which Confluence condition controls.
Customer cancels an annual renewal
In “Customer cancels an annual renewal,” Confluence gives this result: That is not the same as a new annual first purchase and does not meet Atlassian’s standard renewal-refund rule.
The Confluence rule “Initial cloud purchases get limited refund treatment” adds the second test. Monthly initial subscriptions may qualify during the first paid month after trial and new annual cloud purchases within 30 days. Save whichever Confluence confirmation proves the real transaction followed it.
Small team wants to keep pages but stop paying
For this Confluence transaction described as “Small team wants to keep pages but stop paying,” expect this post-cancel outcome: Moving to Free can preserve content, but the team should review lost paid controls before committing.
Cross-reference the Confluence point “Renewal money is different.” Atlassian says cloud renewals and upgrades are not refundable under its standard refund policy. Do not import a different provider’s rule into this Confluence case.
How to carry out a Confluence cancellation or refund request
Confluence action 1: Count active Confluence users and identify the paid tier
For Confluence, perform “Count active Confluence users and identify the paid tier” only after matching the deadline to “Ten-user threshold matters.” That Confluence rule is: Atlassian says a Confluence site with more than 10 users cannot switch to Free until additional users are removed.
The case “Twelve-user Confluence Premium site” shows how Confluence can behave in practice: The Free change is blocked until the user count is reduced to the allowed threshold. Use this Confluence confirmation to verify the same branch applied.
Confluence action 2: Remove or suspend enough users to meet the Free threshold if needed
The Confluence workflow now reaches “Remove or suspend enough users to meet the Free threshold if needed.” Record the billing owner before completing it, because “Content is retained” controls this Confluence branch.
Afterward, compare the Confluence result with “Team relies on restricted spaces.” Existing restrictions are retained, but the Free tier limits the ability to edit permission structures afterward. A mismatch should be documented before another Confluence request is sent.
Confluence action 3: Review space permissions, restrictions, guest access, and anonymous access before the downgrade
Use “Review space permissions, restrictions, guest access, and anonymous access before the downgrade” as the next Confluence action. Pair it with the Confluence rule “Permission controls are reduced,” especially the product type attached to that rule.
For the example “Customer cancels an annual renewal,” That is not the same as a new annual first purchase and does not meet Atlassian’s standard renewal-refund rule. That Confluence example gives a concrete result to compare with the completed action.
Confluence action 4: Change the plan from the Atlassian billing console and preserve the confirmation
Before Confluence action 4, write down the effective date. Then carry out “Change the plan from the Atlassian billing console and preserve the confirmation” under this Confluence checkpoint “Admin access is required.”
Use “Small team wants to keep pages but stop paying” as the post-action Confluence test. Moving to Free can preserve content, but the team should review lost paid controls before committing. Preserve the Confluence evidence until the expected change is visible.
Confluence action 5: If money is being requested back, evaluate that separately under Atlassian’s initial-purchase refund criteria
Action 5 for Confluence is “If money is being requested back, evaluate that separately under Atlassian’s initial-purchase refund criteria.” Its supporting Confluence rule is “Initial cloud purchases get limited refund treatment,” and the key record is the transaction identity.
The Confluence situation “Twelve-user Confluence Premium site” supplies the comparison point: The Free change is blocked until the user count is reduced to the allowed threshold. Check the completed Confluence record against that result.
Verify the final Confluence status
Start the Confluence closeout with “Renewal money is different.” Atlassian says cloud renewals and upgrades are not refundable under its standard refund policy.
Then test “Ten-user threshold matters” against the final Confluence screen. Atlassian says a Confluence site with more than 10 users cannot switch to Free until additional users are removed.
The Confluence example “Small team wants to keep pages but stop paying” should also fit: Moving to Free can preserve content, but the team should review lost paid controls before committing.
If those Confluence records disagree, note the exact date, product, biller, fare, plan, or property before support is contacted.
Confluence transaction worksheet
Confluence worksheet 1: Ten-user threshold matters
Match this Confluence checkpoint “Ten-user threshold matters” with this Confluence case “Team relies on restricted spaces.” The official Confluence point is: Atlassian says a Confluence site with more than 10 users cannot switch to Free until additional users are removed.
For “Team relies on restricted spaces,” Confluence gives this practical result: Existing restrictions are retained, but the Free tier limits the ability to edit permission structures afterward. The related Confluence action is “Review space permissions, restrictions, guest access, and anonymous access before the downgrade.” Save this Confluence confirmation that shows which result occurred.
Confluence worksheet 2: Content is retained
Trace this Confluence checkpoint “Content is retained” with this Confluence case “Customer cancels an annual renewal.” The official Confluence point is: When Standard or Premium changes to Free, Confluence keeps the site content rather than treating the plan change as content deletion.
For “Customer cancels an annual renewal,” Confluence gives this practical result: That is not the same as a new annual first purchase and does not meet Atlassian’s standard renewal-refund rule. The related Confluence action is “Change the plan from the Atlassian billing console and preserve the confirmation.” Save this Confluence confirmation that shows which result occurred.
Confluence worksheet 3: Permission controls are reduced
Reconcile this Confluence checkpoint “Permission controls are reduced” with this Confluence case “Small team wants to keep pages but stop paying.” The official Confluence point is: On Free, admins cannot continue editing the same granular permissions and restrictions available on paid tiers, and anonymous access is unavailable.
For “Small team wants to keep pages but stop paying,” Confluence gives this practical result: Moving to Free can preserve content, but the team should review lost paid controls before committing. The related Confluence action is “If money is being requested back, evaluate that separately under Atlassian’s initial-purchase refund criteria.” Save this Confluence confirmation that shows which result occurred.
Confluence worksheet 4: Admin access is required
Audit this Confluence checkpoint “Admin access is required” with this Confluence case “Twelve-user Confluence Premium site.” The official Confluence point is: A Confluence admin uses Atlassian Billing to manage the subscription and select Free.
For “Twelve-user Confluence Premium site,” Confluence gives this practical result: The Free change is blocked until the user count is reduced to the allowed threshold. The related Confluence action is “Count active Confluence users and identify the paid tier.” Save this Confluence confirmation that shows which result occurred.
What to save for this Confluence transaction
- Confluence original receipt, ticket, invoice, booking, or membership record
- Confluence policy checkpoint “Ten-user threshold matters” with the date that makes it relevant
- Confluence billing or issuing channel tied to the transaction
- Confluence cancellation, downgrade, return, or booking-change confirmation
- Confluence effective end date or next controlling date
- Confluence refund, credit, fee, or equipment-return reference when the policy creates one
Confluence cancellation and refund FAQ
How does “Ten-user threshold matters” affect a Confluence cancellation?
Confluence publishes this rule: Atlassian says a Confluence site with more than 10 users cannot switch to Free until additional users are removed. Compare that Confluence rule with “Twelve-user Confluence Premium site,” where The Free change is blocked until the user count is reduced to the allowed threshold.
How does “Content is retained” affect a Confluence cancellation?
Confluence publishes this rule: When Standard or Premium changes to Free, Confluence keeps the site content rather than treating the plan change as content deletion. For a concrete Confluence example, “Team relies on restricted spaces” means: Existing restrictions are retained, but the Free tier limits the ability to edit permission structures afterward.
How does “Permission controls are reduced” affect a Confluence cancellation?
Confluence publishes this rule: On Free, admins cannot continue editing the same granular permissions and restrictions available on paid tiers, and anonymous access is unavailable. The Confluence scenario “Customer cancels an annual renewal” narrows the answer: That is not the same as a new annual first purchase and does not meet Atlassian’s standard renewal-refund rule.
How does “Admin access is required” affect a Confluence cancellation?
Confluence publishes this rule: A Confluence admin uses Atlassian Billing to manage the subscription and select Free. Use the Confluence situation “Small team wants to keep pages but stop paying” as the cross-check: Moving to Free can preserve content, but the team should review lost paid controls before committing.
How does “Initial cloud purchases get limited refund treatment” affect a Confluence cancellation?
Confluence publishes this rule: Monthly initial subscriptions may qualify during the first paid month after trial and new annual cloud purchases within 30 days. In Confluence practice, “Twelve-user Confluence Premium site” adds this result: The Free change is blocked until the user count is reduced to the allowed threshold.
How does “Renewal money is different” affect a Confluence cancellation?
Confluence publishes this rule: Atlassian says cloud renewals and upgrades are not refundable under its standard refund policy. The Confluence case “Team relies on restricted spaces” gives the practical check: Existing restrictions are retained, but the Free tier limits the ability to edit permission structures afterward.
Which Confluence records are worth keeping after the request?
Keep the original Confluence transaction record, the effective change date, and the final Confluence confirmation. Store any approved Confluence refund, credit, fee, or return reference with the payment or booking record.
What changes when a third party controls this Confluence transaction?
Use this Confluence source that assigns responsibility to the app store, travel agent, property, club, or other biller. The correct Confluence route is the one that reaches the party that actually issued the charge, booking, or ticket.
Related RefundGuides pages for Confluence readers
For Confluence, these existing RefundGuides pages provide nearby software apps navigation. They are supporting context only; the linked official Confluence policy controls the transaction described here.
- Zoom Subscription Cancellation & Refund Guide: Plan Terms, Renewals, Add-Ons and App Stores
- Downgrading Calendly to Free: Renewal Timing and Nonrefundable Payments
- Evernote Cancellation & Refund Guide: 20-Day Monthly, 60-Day Annual and App Store Billing
Official Confluence sources checked on 2026-09-15
Official Confluence documentation below was checked on 2026-09-15. Recheck the applicable Confluence source before a later purchase or cancellation because the controlling terms can change.