Let me publish or share gammas on my domain or subdomain (eg. "example.com/{my-gamma}") | Voters

Let me publish or share gammas on my domain or subdomain (eg. "example.com/{my-gamma}")

Mark Simpson

It would be great if we could have our own domain with ssl or whitelabel the gamma. Right now we can only publish to subdomains.

Nik Payne (Gamma design)

Merged in a post:

password protected custom url gamma's

Ton Tognolli

i want to share the link with clients so they can see their reports we build for them.

but we need them to be on our domain and password protected. now we need to choose, because gamma can do either one or the other. not both

Ton Tognolli

The scope is simple. We create reports for clients with high confidential information. We want share it with clients so they can see the strategy we outline for them. These documents/famma reports need to be password protected per document and stored on our custom domain.
For example: client1-competitoranalysis.ourcustomdomain.com
Client2-competitoranalysis.ourcustomdomain.com
Etc.
One custom domain, multiple reports, each report their own password.
Feel free to ask if this is unclear.
Ps. We found a workaround with a 3rd party tool. But inside gamma is ofcourse preferable.

Nik Payne (Gamma design)

Hey Ton Tognolli, totally get the need here. Sharing client reports on your own domain is great, but it’s a non-starter if it can’t also be password protected. I’ll pass this request to the team.

Quick question so we can scope it right: do you need a single shared password for all clients, or a different password per client/report?

Leo Selie

I don't want to publish a site for each proposal, so using a custom (sub) domain would be great--thanks for considering!

Nik Payne (Gamma design)

Merged in a post:

Custom Domains / Subdomains for Shared Presentations

Victoria Racher

Allow users to assign a custom domain or subdomain to individual shared presentations (not only to published Gamma websites).

Nik Payne (Gamma design)

Victoria Racher love this idea, and thanks for spelling it out so clearly. I’ll pass it along to the team. Quick couple questions so we capture the right use case: are you imagining this for share links (the URL people click) or for the domain shown in the browser once it loads, and do you need it per-presentation or more like “everything in this workspace uses subdomain X” with overrides?

Victoria Racher

Nik Payne (Gamma design) Thanks for the quick response!
Ideally, this would apply to the share link itself (the URL people click) rather than only changing the domain after the presentation loads. The main goal is to have a clean, branded link that can be shared externally.
For the setup, the most useful approach would be:
A workspace-level subdomain (e.g. slides.company.com)
With per-presentation paths (e.g. /platform-overview, /demo, /investor)
So the share links would look like:
"slides.company.com/platform-overview"
"slides.company.com/customer-demo"
Per-presentation overrides probably wouldn’t be necessary in most cases - the main value is having a consistent branded base domain for all shared presentations.
This is mainly useful for sales and external sharing, where a clean and trustworthy link makes a big difference compared to a generic tool URL.
One additional detail that would make this especially useful:
The presentation paths should be manually editable, independent from the presentation title.
In many cases the title of a presentation changes or is longer than what you’d want in a URL. It would be helpful if the path could be set manually, for example:
Title: Company Platform Overview
URL: slides.company.com/platform
Thanks a lot and best ragards

Nik Payne (Gamma design)

Victoria Racher: Super helpful. Thanks!

Kevin Darcy

Yes, white labeled gamma presentation links (not sites) is a must!

Nik Payne (Gamma design)

Merged in a post:

Chat Bot?

Richard Keyt

Does Gamma have a chat bot? If so, how can I access it

Michelle Tran (Design @ Gamma)

Hi Richard Keyt! We do have a chat bot, please see this support article to learn more about Agent: https://help.gamma.app/en/articles/8033284-can-i-edit-my-content-using-ai

Richard Keyt

Michelle Tran (Design @ Gamma). That AI agent is not a chat bot. does gamma have a chat bot? I am trying to learn if I can export a gamm template to my website to the url that is unique to the template? Can I input a template to www.abc.com/one and another template to www.abc.com/two

Gabriel Melchor

I love what Gamma is doing, but this feature can't come fast enough. a) I don't want my clients knowing what I used to generate proposals or other documents, and b) knowing it's an AI platform can cause a perception issue as mentioned below.
What would be ideal for my use case is the option to have something like customdomain.com/deckname/, or /deckname-KEY/ to make brute force crawling difficult for private docs like proposals or private presentations.
I also don't want to create subdomains for each deck that I publish. Since I will be using this for proposals, sales decks, presentations, etc. that is going to create a MESS of a DNS table, and it's a pain to have to maintain such.
Anyone using this to create documents in bulk is going to have a nightmare managing all that, and it creates technical debt to have to go and clean it up later.
Please let us use normal directories on a domain instead of subdomains for publishing white labeled Gammas!

→