A team template is a master card design applied across your employees' cards. It enforces your brand, defines which fields employees can edit, and makes sure every card your team shares looks like it came from the same organisation.
Requirements
- An Umbel team plan
- Owner or Admin role
What a template controls
- Visual design — brand colours, fonts, logo, and banner image
- Field permissions — which fields employees can and can't edit
- Pre-filled content — locked values like company name and website
1. Open the template editor
- Go to your team dashboard.
- Click Templates in the navigation.
- Click Create New Template.
2. Set the brand design
- Primary and accent colours — enter your brand hex codes
- Font — pick from the Google Fonts library
- Banner image — your company banner or a department-specific header
- Logo — displayed on every card using this template
Employees can't change these unless you explicitly allow it.
3. Configure field permissions
Each field on the card gets one of four permission levels:
| Permission | Meaning |
|---|---|
| Locked | Set by the admin; the employee can't change it |
| Mandatory | The employee must fill it in, with their own content |
| Open | The employee can fill it in or leave it blank |
| Forbidden | Hidden entirely |
A setup that works for most organisations:
- Company name, logo, brand colours → Locked
- Name, job title, mobile number → Mandatory
- Personal email, socials, extra links → Open
4. Pre-fill the locked fields
Enter the values that appear on every card using this template — company name, website, main office number, and so on.
5. Name it and assign it
Give the template a clear name (e.g. Sales Department, Executive Team) and save. When creating or editing employee cards, pick it from the Template dropdown.
Updating a template later
When your brand changes, update the template once — every card using it reflects the change immediately. No reprinting, no chasing employees.
Tips
- Create separate templates per department so each team's design and lead form match their use case.
- Start with fewer locked fields — employees engage more with cards they feel some ownership over.