Advaith V.

Hey, we have PDFs being created via Gamma, and then stored to a bank of knowledge. These files need to be referred to easily by agents on our platform, and file names would have a large weighting to allow this. Gamma currently creates these file names by using the title only (we believe) of the presentations it creates. However, sometimes the title is very short/non-descriptive and the subtitle/other headers have the vital context. Therefore, I was wondering if there is a better way to control the file names of the assets created by Gamma. Maybe a parameter we can include while making the generation call to Gamma for the file_name of the asset? That way we can get our ai to come up with the best name for it. Or is there any way that the file_name created by Gamma can use that extra context from the subtitle if the title is short

Hi, we are currently using the Gamma api to generate presentations. We currrently pass the following parameters: tone, themeId, audience, exportAs, numCards, textMode, textAmount, imageSource, cardDimensions, additionalInstructions, inputText. Since recently, the presentations we've been generating for our customers who have their own gamma theme ids (with their own accent images, etc) have been generating these in the slides:(first image) These look off brand for our customers. I did a bit of digging and found that these are being generated by the BETA AI infographics feature. We want to turn this off for our generations, and I was wondering what the best way is. Is it including instrucions in the additionalInstructions block? Or is there a deterministic way to prevent using this?