Review credit usage / expenses / credits dashboard / activity dashboard
Rose Pereira
Many times we make an order to the AI and it goes completely wrong, we order again using an appropriate prompt, made by another AI and it's still wrong. We spend our credits and it doesn't work out. This frustrates and discourages, as we saw our credits going away and we didn't close anything. Another thing, I didn't use it for a while due to work and it didn't accumulate, I thought it accumulated correctly, which only accumulates two months, in other words, 8000 credits is wrong, because the person pays. Today, with many free AIs, it makes a person discouraged to renew. You're going to lose with that.
C
Chris
This has been a deeply disappointing experience with Gamma.
I joined just a couple of hours ago and have already decided to leave the platform. I requested a simple, professional presentation with 8 slides. Instead, I received a design filled with AI-generated leaves and mountains — a layout I never asked for. Despite this, I was charged not only for the initial output, but also for each subsequent correction. Every iteration comes at a cost, even when the result does not align with the original brief.
What is particularly concerning is the underlying model: users are billed continuously, including when adjustments are required due to outputs that miss the mark. When I raised this with support, the response was essentially that the issue lies with the user, not the platform — and that if I am not satisfied, I am free to leave. No refund was offered, on the basis that credits had already been used, even though the initial delivery did not meet the request.
I fully understand that AI is not perfect — and that is precisely why accountability and flexibility on the provider’s side are essential. Charging users for correcting outputs that do not reflect their instructions creates a misalignment of incentives and, frankly, erodes trust.
If you position yourselves as a professional service provider, there must be a baseline commitment to quality, transparency, and client fairness. When something does not meet expectations, it should be acknowledged — not systematically redirected back to the user.
After two hours spent trying to resolve this, with no constructive outcome and no willingness to reconsider the charges, I am left questioning the overall client approach.
To finalize, no solutions, a part I mistaken, and no refund! Incredible support and service! Well done guys.
Nik Payne (Gamma design)
Merged in a post:
AI credit transparency and auditability.
k
kamel sellaoui
Hi Gamma team,
I want to submit a feature suggestion for AI credit transparency and auditability.
Your current credit summaries are useful at a high level, but they are not sufficient for finance, operations, or internal control purposes. The current format groups activity into broad time windows and mixes user-facing labels with backend event names. That makes it difficult to reconcile credit consumption, identify anomalies, eliminate duplicates, and verify whether charges were correct.
What would solve this is an audit-grade credit usage ledger, available in-product and exportable as CSV.
Here is the minimum field set that would make the ledger operationally useful:
Field Why it matters
Timestamp per atomic event Required to reconstruct exact usage chronology and stop grouped-window ambiguity
Request ID / Job ID Needed to detect retries, duplicates, reversals, and repeated charges
Document ID Needed to link usage to a specific Gamma file
Workspace ID Needed for team/workspace reconciliation
User ID / User email Needed to attribute usage by person
Event type (internal name) Needed to distinguish actions such as generateV2, generateV2WithImages, image_edit_maskless, image generation, card generation, etc.
User-facing action label Needed so admins can interpret technical event names without support intervention
Credits debited per event Core audit field
Credits credited / reversed per event Needed to explain refunds, failed runs, corrections, or comped actions
Net credit impact Simplifies reconciliation
Event status success / failed / cancelled / clarification / reversed / comped
Output count Important for image-heavy and multi-output actions
Model / feature used Useful for cost attribution and debugging
Opening balance before event Needed for ledger traceability
Closing balance after event Needed for full balance reconciliation
Billing source Monthly refill, rollover, referral, one-time purchase, promo credit, admin adjustment
Exportable notes / metadata Useful for internal tagging and audit comments
Why this matters:
1. Finance teams need a real ledger, not a narrative summary.
2. Admins need to explain sudden spikes in usage.
3. Teams need to separate normal generation from retries, failed jobs, reversals, and manual adjustments.
4. Credit disputes cannot be resolved reliably without atomic event-level records.
5. Larger workspaces need CSV export for internal reporting, anomaly detection, and chargeback.
Suggested deliverables:
• A usage page with filterable event-level credit history
• CSV export
• Filters by date, workspace, user, document, and event type
• Separate views for credits consumed vs credits added
• Clear mapping between backend event names and billable product actions
This would materially improve trust, auditability, and enterprise readiness.
Best regards,
Kamel Sellaoui
Nik Payne (Gamma design)
Merged in a post:
Credits used
M
Md. Shahinur Rahman
Please add a Credits used column in the Gammas list view. Right now the list shows Title, Folders, Last edited, and Creator, but there’s no way to see which generated items consumed the most credits. A Credits used column would let me sort and quickly identify what burned through my balance.
Nik Payne (Gamma design)
Md. Shahinur Rahman thanks for the super clear writeup. A “Credits used” column in the Gammas list view (and sortable) makes a ton of sense for tracking what’s eating your balance, I’ll pass this to the team.
Quick couple questions so we build it the right way:
1) Do you want credits shown per Gamma total, or broken out by actions (generate vs rewrite vs image, etc)?
2) Would you want this visible just in the main list view, or also inside folders/search results?
Nik Payne (Gamma design)
Merged in a post:
Member Activity Reporting (usage dashboard)
Trent Foley
As the admin within our organization, I am needing to run member activity reporting to understand the time & frequency of use by each of our team members to be able to report back to our board metrics pertaining to our AI adoption program.
Nik Payne (Gamma design)
Merged in a post:
We need a Credit Use Dashboard/History
H
Hans van Druten
So we could track our AI credit use and improve how we plan the presentations/sites and how we prompt the AI agent. Currently we don't know how much credit we are being charged for generating cards, texts and images, and how much for animating images and translating texts. Thank you devs.
Nik Payne (Gamma design)
Totally hear you, Hans van Druten. A credit usage dashboard with history and a per-action breakdown (cards/text/images, animation, translation) would make planning way easier. I’ll pass this to the team. Quick Q: would you want this broken down by project and by teammate too, or is an account-level timeline enough?
H
Hans van Druten
Yes a dashboard/window to see our credit use history will be great. Image animation is a credit guzzler currently.
Nik Payne (Gamma design)
kamel sellaoui this is super thoughtful, thank you. Totally hear you on needing an audit-grade, event-level ledger (not a grouped summary) for finance ops, reconciliation, and disputes. I’m going to pass this to the team.
Quick couple questions so we design it right:
1) Who’s the primary user for this in your org (finance, workspace admin, ops), and what’s the top 1-2 workflows they need (monthly close, anomaly detection, chargeback, dispute resolution)?
2) For the CSV, do you need it to include both debits and credits/adjustments in one unified ledger, or do you prefer separate exports/views for “consumed” vs “added”?
If you’ve got an example of another product’s usage ledger you consider “audit-grade,” I’d love to see it too.
k
kamel sellaoui
Nik wPayne (Gamma design)
Hi Elyn,
Thanks — this is exactly the direction we had in mind.
1. Primary users
The primary users would be:
• Workspace admins / operations
• Finance / reconciliation owners
Top workflows:
• monthly close and reconciliation
• anomaly detection and investigation
• usage attribution / internal chargeback by user or document when needed
In our case, the immediate need is to understand significant burn spikes on accounts, identify what generated them and reconcile totals cleanly.
2. CSV structure
Our preference is a unified ledger including both debits and credits/adjustments in the same export, with a clear net impact field per row.
The key requirement is that the ledger remains atomic and fully reconcilable, so that summing row-level impacts matches the balance movement for any selected period.
This is important because grouped summaries are not enough for finance ops, internal controls, or dispute handling, especially when an account shows unusually high burn on a specific day.
Best regards,
Kamel Sellaoui
Nik Payne (Gamma design)
kamel sellaouiThank you!
Nik Payne (Gamma design)
Thanks for writing this up, Rose Pereira. Totally hear the frustration of burning credits on retries when the output is off.
A couple quick questions so we can pass something actionable to the team:
1) When you say it “continues wrong”, what kind of wrong is it (facts incorrect, tone/style, structure, language, ignoring instructions)?
2) On the credit side, are you asking for (a) a way to review a detailed credit usage history per request, (b) a way to refund credits for bad generations, or (c) credits to roll over/accumulate longer when you don’t use the product?
If you can share one example prompt + the kind of result you expected (no sensitive info), that would help a lot.
Load More
→