Add Authorized Spend via Console Documentation

[fenilmodi00]

Problem Statement

The current Authorized Spend documentation only covers CLI-based commands using provider-services but completely lacks documentation on how to use this feature via the Akash Console web interface.

Current Documentation Gap

The existing documentation covers:

• ✅ CLI commands for authorizing wallets
• ✅ CLI commands for viewing authorizations
• ✅ CLI commands for creating deployments with authorized funds
• ✅ CLI commands for managing authorizations

Missing:

• ❌ How to set up authorized spend via Console
• ❌ Console UI walkthrough for authorization process
• ❌ Screenshots/guides for Console-based authorized spend workflow

Proposed Solution

Add a new section to the existing page: "Using Authorized Spend via Console" ;

Content to Add:

Console-Based Authorized Spend Setup

1. How to Access Authorized Spend in Console

   • Navigation path within Console UI
   • Prerequisites (wallet connection, funding requirements)

2. Step-by-Step Console Walkthrough

   • Screenshots of the authorization process
   • Form fields explanation
   • Setting spending limits via UI
   • Wallet selection process

3. Managing Authorizations via Console

   • How to view existing authorizations
   • How to modify spending limits
   • How to revoke authorizations
   • How to check remaining authorized balances

4. Deploying with Authorized Funds via Console

   • How the deployment process differs when using authorized funds
   • UI elements that show authorized vs direct funding
   • Error handling and troubleshooting

Console vs CLI Comparison

• Feature parity comparison
• When to use Console vs CLI for authorized spend
• Any limitations or differences in functionality

Visual Documentation

• Screenshots of each step in the Console UI
• Annotated UI elements
• Before/after states

Expected User Flow Documentation

The documentation should cover the typical user workflow:

1. Organization Admin (Funding Wallet):

   • Navigate to Authorized Spend section in Console
   • Add team member wallet addresses
   • Set spending limits per wallet
   • Monitor usage and remaining balances

2. Team Member (Deploy Wallet):

   • Log into Console with authorized wallet
   • Create deployments using authorized funds
   • Check remaining authorized balance
   • Deploy applications without direct access to organization funds

Impact

This documentation will:

• ✅ Make Authorized Spend more accessible to non-CLI users
• ✅ Increase adoption of the feature for team-based deployments
• ✅ Reduce support requests about Console-based authorized spend
• ✅ Provide visual guidance for UI-based workflows
• ✅ Help organizations better manage deployment spending

Suggested Implementation

1: Add new section to existing page:

• /docs/network-features/authorized-spend/index.md
• Add "Using Authorized Spend via Console" section

[gouravKJ]

@fenilmodi00 can i be assigned for this

[gouravKJ]

@fenilmodi00

[fenilmodi00]

@fenilmodi00 can i be assigned for this

Hey, thanks for showing interest!
Before the maintainers assign this issue — since it’s an intermediate-level one
I’d love to know if you’ve used the Authorized Spend feature via the console before?

[ReetShah13]

i would love to contribute
we are using this feature in our start-up

[mannubaveja007]

Hey can I contribute to this? or should I directly attach the PR

[fenilmodi00]

i would love to contribute we are using this feature in our start-up

can you DM me on Discord my username is fenil_modi

[fenilmodi00]

Hey can I contribute to this? or should I directly attach the PR

You can , since this is an intermediate-level issue, you need to have experience using authz spends via the console. Do you have that experience?

[fenilmodi00]

@HoomanDgtl We can assign this issue to @ReetShah13.

They are already using this feature, so it would be best to have the documentation created by them.

---

💰 Bounty:
This issue carries a $100 bounty in AKT as part of the Hacktoberfest initiative.

The bounty will be released upon merge of a high-quality PR that includes:

• A clear and thorough explanation
• Helpful visuals or examples
• All relevant technical disclaimers and edge-case behaviors