Jump to content

Recommended Posts

Posted

Each of our schools has their own footer formatted in a table however I need to update one of them and when i do so, i cannot get it to format back to a table.

 

When i inspect the element / view the source code, i can see that the footer formatter is set so that the configured footer is set in a table.

 

Question is, how on earth do you set the footer in Google Workspace to format as a table?

Posted

Strange one. The official line is that the Append footer option in Google Admin > ... > Gmail > Compliance doesn't support HTML content.

 

https://apps.google.com/supportwidget/articlehome?hl=en-GB&article_url=https%3A%2F%2Fsupport.google.com%2Fa%2Fanswer%2F2364576%3Fhl%3Den-GB&assistant_id=generic-unu&product_context=2364576&product_name=UnuFlow&trigger_context=a

 

Are you sure that it's a footer and not a part of their individual signature?

Posted
Strange one. The official line is that the Append footer option in Google Admin > ... > Gmail > Compliance doesn't support HTML content.

 

https://apps.google.com/supportwidget/articlehome?hl=en-GB&article_url=https%3A%2F%2Fsupport.google.com%2Fa%2Fanswer%2F2364576%3Fhl%3Den-GB&assistant_id=generic-unu&product_context=2364576&product_name=UnuFlow&trigger_context=a

 

Are you sure that it's a footer and not a part of their individual signature?

 

Positive!

 

Here is a screenshot of what is currently configured.

 

Email.png

 

I've had a scoot around on the net and one article says:

 

https://www.eringibson.co/email-signature-gmail/

 

But this doesn't work under compliance, yet the other schools have had it configured.

Posted

The support article specifically says that the editor doesn't support HTML, and it appears to strip out table formatting if you paste in an HTML table, so I wonder if that footer has been added via the API, or was added before the ability to paste in HTML content was restricted. I don't think that there is an API covering stuff like compliance rules, etc. for Gmail. The Gmail API appears to be for mailbox stuff, rather than org-wide admin console stuff. You migt be out of luck.

 

I would recommend prepping a new footer that isn't table-based, and keeping but disabling the existing one.

Posted
It's a bit of a Steve Jobs "don't hold it like that" thing, but I guess your content should be considered part of the signature block rather than a footer, which is most likely intended for legalese discalimer stuff rather than branding. But then it's not as if Google have provided any signature management tools, either. I created my own Sheets/AppsScript solution for signatures, which I'm hoping to be able to share on GitHub at some point (it's based partly on this - https://caspan.com/2021/10/google-app-script-set-gmail-signature-template-on-org-users/).
  • Thanks 1
Posted
It's a bit of a Steve Jobs "don't hold it like that" thing, but I guess your content should be considered part of the signature block rather than a footer, which is most likely intended for legalese discalimer stuff rather than branding. But then it's not as if Google have provided any signature management tools, either. I created my own Sheets/AppsScript solution for signatures, which I'm hoping to be able to share on GitHub at some point (it's based partly on this - https://caspan.com/2021/10/google-app-script-set-gmail-signature-template-on-org-users/).

 

I'd be interested to see it. The footers were designed before we joined the MAT and the person who designed them has since left the trust.

 

I imagine it was a way of easily configuring school signatures from each school meaning that users didn't have to create their own when new users started at each school.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...