Template Permissions
Sharing happens at the group a template sits in, never at the single template, and the person who made the group is the only one who can change who sees it. Both of those are deliberate and both will shape how you organise.
Where a template is filed decides who has it
4 of 4 can use it- roleAccount Executiveuse
- teamEMEA Salesuse
- Priya Ramanmade the templateusemodifydelete
- Tom Alvarezrole: Account Executiveusemodifydelete
- Nadia Okaforrole: Account Executiveusemodifydelete
- Ben Oseiteam: EMEA Salesusemodifydelete
Product figures from the platform’s own defaults - not customer averages
How it works.
The grant hangs off the group
A row names the group, whether it points at a role or at a team, which one, and how far it goes. Putting a template into that group is what shares it, so filing is the act of sharing.
Use and modify are genuinely different
A viewing check passes on either level and an edit demands a row that explicitly says modify, so the enforcement is real rather than advisory. The sharing dialog carries the level picker, so which of the two a grant confers is settled when the grant is made rather than afterwards.
Only the maker can see the sharing
Asking which roles hold a group you did not create comes back refused rather than empty, so nobody can walk the identifiers and map out somebody else's arrangement.
Deleting stays with the maker
Removing a template is reserved to whoever created it, whatever grants exist. A modify grant lets somebody rewrite the wording, never remove it from under the team using it.
Two moments in every message.
Every message passes through the same seven. Template Permissions is the lit ones, and everything either side of it is a different page in this category.
- 01Connect
the account it syncs with
- 02Compose
writing it, and from what
- 03Send
leaving now, or on a schedule
- 04Arrive
landing, and what it lands as
- 05Attach
pinning it to the right record
- 06Book
the meeting that comes of it
- 07Govern
who may use what, and see what
The specifics.
8 facts- Granted on
- A template group, which is what every screen calls it. There is no path for sharing one template on its own
- Granted to
- One row per CRM role, or one per team, and a group may carry as many rows as you need
- Levels
- Use, or modify. Modify requires its own row, is not implied by use, and is enforced on every edit
- Who administers
- Only the person who created the group. Being a workspace administrator does not open somebody else's
- Deleting a template
- Its creator, always. No grant ever confers this
- Role matching
- Your one effective role is compared. A grant to a role above yours in the tree does not reach down to you
- Removing a group
- Refused outright while anything is inside it, templates or nested groups alike. Empty it first, and only then do its grants go with it
- Nesting
- A group may hold groups. A template inside a nested one is reached through the grants on the group it actually sits in
What this sits beside.
Mail and diary are one surface with several parts. These are the ones a person passes through in the same minute.
More in Email & Calendar
13 capabilitiesWebmail, four sync providers, tracking, calendar and meetings.
Google Calendar writes out the moment you save and mails the invitations, and reads back on demand, so a meeting booked on a call is there before it ends.
Connect Gmail on one scope and mail arrives by push rather than polling, filed against the lead holding the address, with nobody having to forward anything.
Outlook and Microsoft 365 sync through Graph with delta queries and subscriptions, so large mailboxes stay current without re-reading themselves.
A Microsoft mailbox brings its calendar and address book over Graph, on subscriptions that renew themselves, with a ten-minute pass running underneath.
Any mailbox that speaks IMAP and SMTP connects with a form and a live login test, so a provider nobody built an integration for is still a real inbox here.
Opens and clicks recorded against the record, with signed link identifiers so the tracking endpoint never trusts a parameter it was handed.
Put a thread out of sight until it matters and schedule a send for the morning, with the parked thread coming back unread so you cannot walk past it.
One signature per connected mailbox, added by the send path to new messages and forwards, so mail from the platform arrives looking like mail from a person.
Book from the conversation, with the invitation, the joining link and the record all created together instead of in three separate tabs afterwards.
Connect Zoom and a booking creates, moves and cancels the meeting for you, with the joining link and passcode riding inside the calendar invitation.
Pick Google Meet on a booking and the calendar write mints the link with the invitation, so everyone on the account gets it rather than finding it in a note.
Connect Teams and a booking makes the meeting through Microsoft's own interface, carrying its joining address into the invitation the guests receive.
Inbound mail attaches to the lead holding any address on it, sender or recipient, matched exactly once lowercased. Two columns, one query, no resemblance.
The rest of the platform.
Five more categories, all on the same record and the same bill. Each card names three of its capabilities, so you can tell from here whether it is worth opening.
Email & Calendar
See template permissions on your own floor.
Thirty minutes, your numbers and your data. We will set template permissions up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included