Update Asgardeo billing portal docs for resource-based (PAYG) subscriptions#6246
Update Asgardeo billing portal docs for resource-based (PAYG) subscriptions#6246Lakshan-Banneheke wants to merge 4 commits into
Conversation
|
Warning Review limit reached
Next review available in: 47 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe ChangesBilling Portal Documentation Update
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
en/asgardeo/docs/guides/your-asgardeo/subscribe-to-asgardeo/subscribe-via-billing-portal.md (1)
11-11: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winUse the repository’s
log inwording here.
Sign inconflicts with the repository convention for user actions. Change this toLog into keep the guide consistent. As per coding guidelines, uselog inas the verb andloginas the noun/adjective consistently.Suggested fix
-1. Sign in to the WSO2 Identity Platform Console. +1. Log in to the WSO2 Identity Platform Console.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@en/asgardeo/docs/guides/your-asgardeo/subscribe-to-asgardeo/subscribe-via-billing-portal.md` at line 11, The step text uses “Sign in” instead of the repository’s user-action wording. Update the affected sentence in the subscription guide to use “Log in” consistently, and keep the repo convention of using “log in” as the verb form (with “login” only as a noun/adjective) across this document.Sources: Coding guidelines, Learnings
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In
`@en/asgardeo/docs/guides/your-asgardeo/subscribe-to-asgardeo/subscribe-via-billing-portal.md`:
- Line 11: The step text uses “Sign in” instead of the repository’s user-action
wording. Update the affected sentence in the subscription guide to use “Log in”
consistently, and keep the repo convention of using “log in” as the verb form
(with “login” only as a noun/adjective) across this document.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yml
Review profile: CHILL
Plan: Pro
Run ID: d3df18b0-59c3-4d71-91a4-207161cee7d4
⛔ Files ignored due to path filters (7)
en/asgardeo/docs/assets/img/guides/billing/cancel.pngis excluded by!**/*.pngen/asgardeo/docs/assets/img/guides/billing/overview.pngis excluded by!**/*.pngen/asgardeo/docs/assets/img/guides/billing/step-review.pngis excluded by!**/*.pngen/asgardeo/docs/assets/img/guides/billing/step-select-tier.pngis excluded by!**/*.pngen/asgardeo/docs/assets/img/guides/billing/step-support.pngis excluded by!**/*.pngen/asgardeo/docs/assets/img/guides/billing/step-usage-commitments.pngis excluded by!**/*.pngen/asgardeo/docs/assets/img/guides/billing/step-usage-ppu.pngis excluded by!**/*.png
📒 Files selected for processing (1)
en/asgardeo/docs/guides/your-asgardeo/subscribe-to-asgardeo/subscribe-via-billing-portal.md
Lakshan-Banneheke
force-pushed
the
billing-docs
branch
from
b74b442 to
de2a7c1
Compare
|
|
||
| ## Downgrade/Cancel your subscription | ||
| !!! warning | ||
| Cancelling this subscription will immediately deactivate the organization, including all applications, authentication flows, and related services. You will no longer be able to access or use this organization after cancellation. |
There was a problem hiding this comment.
You will no longer be able to access or use this organization -> is this correct? ideally users can continue to use the same org with the downgraded plan, isn't it? since the trial is ended users may not be able to do anything, but should we block access?
There was a problem hiding this comment.
This is actually not related to the trial expiry. Trial expiry will be handled separately and the org will be downgraded to free tier.
This is in relation to a user who initially had a paid subscription, clicking on the Cancel button.
As per a previous discussion in the Product Council, it had been decided to deactivate the org when the above occurs.
However, we can consider downgrading them to the free tier as well. I'll look into it and see if we can revisit that decision.
There was a problem hiding this comment.
However, we can consider downgrading them to the free tier as well. I'll look into it and see if we can revisit that decision.
Yes, that would be the better path AFAIU. Deactivating the org on cancelling subscription feels hostile.
| To upgrade your subscription: | ||
|
|
||
| 1. Sign in to the WSO2 Identity Platform Console. | ||
| 1. Log in to the WSO2 Identity Platform Console. |
There was a problem hiding this comment.
Any reason this was changed? Sign in is the better option for a user action.
There was a problem hiding this comment.
This was changed due to a comment by Coderabbit. #6246 (review)
Use the repository’s log in wording here.
Sign in conflicts with the repository convention for user actions. Change this to Log in to keep the guide consistent. As per coding guidelines, use log in as the verb and login as the noun/adjective consistently.
Shall I switch back to Sign in?
…bscribe-via-billing-portal.md Co-authored-by: Himesh Siriwardana <himesh.siriwardana@gmail.com>
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@en/asgardeo/docs/guides/your-asgardeo/subscribe-to-asgardeo/subscribe-via-billing-portal.md`:
- Line 116: Bold the “Growth” plan name in the subscription guidance paragraph,
matching the existing formatting used for other Growth references and preserving
the surrounding text and UI-label formatting.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yml
Review profile: CHILL
Plan: Pro
Run ID: c823f766-267b-44ac-b97d-aa9d09ebe71a
⛔ Files ignored due to path filters (7)
en/asgardeo/docs/assets/img/guides/billing/cancel.pngis excluded by!**/*.pngen/asgardeo/docs/assets/img/guides/billing/overview.pngis excluded by!**/*.pngen/asgardeo/docs/assets/img/guides/billing/step-review.pngis excluded by!**/*.pngen/asgardeo/docs/assets/img/guides/billing/step-select-tier.pngis excluded by!**/*.pngen/asgardeo/docs/assets/img/guides/billing/step-support.pngis excluded by!**/*.pngen/asgardeo/docs/assets/img/guides/billing/step-usage-commitments.pngis excluded by!**/*.pngen/asgardeo/docs/assets/img/guides/billing/step-usage-ppu.pngis excluded by!**/*.png
📒 Files selected for processing (1)
en/asgardeo/docs/guides/your-asgardeo/subscribe-to-asgardeo/subscribe-via-billing-portal.md
…bscribe-via-billing-portal.md Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
3 participants
Purpose
Updates the Subscribe via Billing Portal guide to reflect the redesigned Asgardeo billing portal, which moves from the previous tier-based model (Free/Essentials/Professional/Enterprise with B2C/B2B/B2E use cases) to the new resource-based, Pay-As-You-Go (PAYG) model.
Key documentation changes:
Related PRs
Test environment
Documentation-only change. Verified locally with
mkdocs serve(mkdocs 1.6.1); page renders correctly and all image references resolve.Security checks