Set “Show Card Backdrops” as a workspace, theme, or template default
O
Operacional Orizz
We need a workspace, theme, or template-level default setting to keep “Show Card Backdrops” enabled for all new and duplicated Gamma documents.
Our team creates client-facing travel proposals in Gamma and uses custom visual backgrounds as part of our brand identity. Today, even when duplicating an official template, we still need to manually check this setting every time. If someone forgets, the background appears blurred/hidden in present mode or exports, which affects the final client experience.
Please add one of these options:
- Workspace default: always show card backdrops.
- Theme-level setting.
- Template-level setting preserved on duplication.
- API parameter for generated documents.
This would reduce manual errors and improve brand consistency for teams using Gamma commercially.
Nik Payne (Gamma design)
I cut a ticket to help with this!
Nik Payne (Gamma design)
Operacional Orizz thanks for the super clear writeup, this makes a ton of sense. I’ll pass this to the team.
Quick couple questions so we scope it right:
1) Which path bites you most often: duplicating an existing doc, creating from a template, or generating a new doc via API?
2) When someone forgets to enable it, where do you notice the impact first: present mode, export (PDF/PPT), or both?
Also, if you have a preference, would you rather this live as a workspace-wide default (hard to mess up) or be something the template/theme “locks in” per doc?
O
Operacional Orizz
Nik Payne (Gamma design) Thanks!
The path that bites us most often is creating from a template. We’ve established an internal standard where our team always starts proposals from official templates, because that workflow works well for us.
When someone forgets to enable “Show Card Backdrops,” we usually notice the impact in exports only (PDF/PPT). That’s the format we use the most here at the agency for client-facing travel proposals.
I don’t have a strong preference between the proposed solutions, since either a workspace-wide default or a template/theme-level setting would solve the issue very well for us. But if I had to choose one, I’d prefer a workspace-wide default, since it would be the hardest for the team to miss.