Notifications, Usage, and AI Credits
How notification preferences, device push subscriptions, personal and organization AI credit balances, usage metrics, and active workspace session controls work from the account settings side.
Where you see this in the app
These controls live mainly in:
| Route / UI | What it is for |
|---|---|
Settings → Notifications | Choose which emails you want and whether non-payment emails are paused |
/feed | See the signed-in device notification prompt when this browser or Android app session is eligible |
Settings → Usage | Review AI credit balance, buy top-ups, inspect usage metrics, and manage active workspaces |
Settings → Organizations | Manage organization wallets, top-ups, invitations, and org-billed usage when you belong to a team |
Notification preferences
The notifications page is about account communication preferences.
The main choices are:
| Setting | Plain-English meaning |
|---|---|
Pause all emails | Skip non-payment emails broadly |
Payment + receipts | Keep purchase, subscription, and payout emails |
Reminders | Receive check-in reminders and similar nudges |
Onboarding tips | Receive activation and setup guidance |
Product updates | Receive occasional release/news emails |
The page also explicitly warns that compliance-critical payment receipts may still send even when non-payment emails are paused.
Device push notifications are managed separately from email preferences. A signed-in user may enable browser or Android app notifications from the /feed prompt or retry from Settings → Notifications.
The current device subscription depends on browser or operating-system permission. If the device blocks notifications, GetPaidX can show the subscription controls, but the user may still need to allow notifications in the browser or phone settings.
AI credit balance and top-ups
The usage page starts with the wallet-style AI credit summary.
| UI label | What it means |
|---|---|
AI credits | Available spendable balance for AI usage |
Balance | Current wallet balance |
starter buffer | The built-in overdraft cushion shown by the app |
| top-up packages | Purchase options that add more usage credit |
This section is about keeping your account funded for AI-assisted features, not about a subscription plan by itself.
Organization AI credits
Organizations can have their own AI-credit wallet.
Use an organization wallet when a team, client account, lab, or company should pay for workspace AI usage instead of only one personal account.
The organization page shows:
| UI area | What it means |
|---|---|
| wallet summary | Current organization AI-credit balance |
| top-up packages | Stripe Checkout packages that add credits to the organization wallet |
| usage events | Recent org-billed workspace/model usage |
| wallet transactions | Recent organization credit purchases and debits |
Only organization members with billing authority can top up or inspect the org billing ledger.
Organization membership is separate from following. Following a creator does not make you part of their organization, and joining an organization does not automatically follow every member.
Organization membership is also separate from conference peer-review roles. A reviewer, chair, or program committee member still needs the relevant peer-review role or assignment even if they belong to the same organization.
Organization credits do not change Stripe Connect payout identity. Creator payout accounts remain user-scoped.
Usage metrics
The Workspace usage section summarizes activity across your account.
The current metrics are:
- total requests,
- total tokens,
- input tokens,
- output tokens,
- cached tokens,
- reasoning tokens.
These numbers help a user understand how heavily their workspaces are using AI resources over time.
Active workspaces
The Active workspaces section is operational control for currently running interactive sessions.
| Action or field | Plain-English meaning |
|---|---|
Refresh | Reload the current active-session list |
Close | End one workspace session |
Close all | End all running sessions tied to the billing account |
| status / mode / heartbeat | Operational state for each running session |
This page is useful when AI usage or billing feels higher than expected and you need to confirm whether workspaces are still running.
Related docs
Related docs
See it in action
Previous
API Tokens, Webhooks, and Account Controls
The browser-level guide to PATs, token scope groups, webhooks, notifications, usage, AI credits, and custom domains.
Next
Android App and Device Notifications
How Android app mode, the feed push prompt, and device-level notification subscriptions work for signed-in users.