Centralized email signature management in three steps
Three steps, and each one names what the administrator actually clicks. If you are evaluating this against a weekend of writing a PowerShell script, this page is the comparison you need.
Connect the tenant
You sign in to AutoSignature and choose your platform. For Microsoft 365 you approve a scoped permission grant as a global administrator, the same consent screen your tenant shows for any application. For Google Workspace you authorise the connection from your admin account and confirm the org units that are in scope.
- The consent screen lists the permissions before you approve: read directory profiles, set signatures on the mailboxes in scope.
- You can connect both platforms to one account, which is the normal state after an acquisition.
- The grant lives in your tenant, so you revoke it from your own console whenever you want.
- Nothing is installed on anyone's computer, and no mail flow changes.
Time this takes: a few minutes, most of them spent reading the permission list.
Build the template
You open the studio, pick one of the twelve layouts, and set the brand: logo, accent colour, typeface and spacing. Then you map directory fields to the tokens in the template, and the preview fills with a real person from your own directory.
- Switch between people in the preview to see how the layout behaves with a long job title and a short one.
- Switch between Outlook, Gmail, Apple Mail and mobile to see each client's rendering before anyone receives it.
- Turn on the blocks you want: banner, disclaimer, social links, meeting link, photo.
- Save a short mobile variant of the same set in the same screen.
Time this takes: an hour or two, because agreeing on the design is the slow part, not building it.
Deploy to groups
You define the groups that get each set, by department, office, country or entity, and you deploy. The rollout screen shows the mailbox count, the platform and the exact signature each group receives.
- Deploy to one group first, read the result, then widen to the rest.
- Every rollout is a version with the person, the change and the timestamp.
- Rollback returns a group to its previous version in one click.
- Later changes are the same three clicks: edit the set, preview, deploy.
Time this takes: minutes per group, and the first one is the only one you will watch closely.
Nothing they have to do
People keep writing email. The next message they send carries the new signature, the mobile variant appears on their phone, and replies use the short block if you chose that. There is no announcement to write and no instructions to send, which is the point of managing signatures centrally.
The work that stops
- No signature ticket from a new joiner, because the joiner is signed on day one.
- No chase after a rebrand, because the logo changes in one place.
- No spreadsheet of who pasted the HTML and who did not.
- No manual edit for a promotion, because the directory already knows.
Read the full feature list, the platform pages or the pricing when you are ready to size it.