Get started
Design a template
Go further
The seven field types in Gensy, how required fields work, and how AI can suggest fields from a CSV file or an existing signature.
Fields describe what each employee brings to their signature. A template only knows fields: at deployment, each {{field_name}} variable is replaced with the value from the profile. The owner and admins manage them on the Fields page.
mailto: link.tel: link.New field opens a window: type, name, link or network for URL and Social media fields, and the Required checkbox. A required field is flagged with a badge on the employee profile and an asterisk in the portal, but saving isn’t blocked: only the email address is enforced. First name, Last name and Email are locked.
The table shows where each field is used, for example “4 templates · 245 employees”.
The page’s ··· menu offers two paths, at 3 credits each, from the Starter plan up:
Both lead to the Suggested fields list, with a confidence score. A “Same everywhere” column — company, website, main phone — is unchecked: it belongs in the template as fixed text, not as a field.
The same menu offers Export CSV template, a ready-to-fill file for importing employees.
5 custom fields on the Free plan, 10 on the Starter plan, unlimited from the Essential plan up. First name, Last name and Email don’t count; Job title, created by default, does.
A bilingual organization declares two fields — titre_fr and titre_en — rather than one: that’s what lets you display one or the other with a condition.
Before you confirm, Gensy shows how many employees have the field filled in and which templates use it. The field’s data is erased; this can’t be undone.
Need help?
Support answers from within the app, with your workspace already in context.
© 2026 GENSY.EMAIL (Agence Hélium Inc.)
All rights reserved.