Template Permissions
Filing a template into a group is what shares it, so there is no second step for anybody to forget. Who sees that group is set by whoever made it, and by nobody else, workspace administrators included.
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.
Filing is the act of sharing
A share 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 nobody has to remember a second step afterward.
Use and rewrite are genuinely different
Opening one passes on either level and an edit demands a row that explicitly says modify, so the line is enforced rather than advised. Which of the two a grant confers is settled in the sharing dialog when the grant is made, not argued about later.
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 go looking through how somebody else has their work arranged.
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 pull it out 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 mailbox connections, tracking, calendar and meetings.
Book a slot while the customer is still on the line and the invitation is in their inbox before you say goodbye. What they change comes back when you sync.
Mail is here without anybody pressing refresh or forwarding anything, filed against the lead holding the address. Google knocks the moment something changes.
The mailbox stays connected, and a message somebody moved is not sitting here twice. Outlook and Microsoft 365 over Graph, picking up only what changed.
A Microsoft mailbox brings its diary and address book with it, and whether it sits in Microsoft 365 or on a server in your building is worked out for you.
The connection for a mailbox nobody hosts for you. We sign in for real before saving the hosts and ports, so a typo is caught while you are still at the form.
What does not count is the useful part: a rep opening their own message, a crawler, the same person twice in five minutes. A figure a supervisor can act on.
Park a thread and it comes back at the hour you named, unread, so nobody walks past it. Hold a send and it leaves at the hour you named, once, never twice.
Nobody retypes their sign-off. It is held once per mailbox and added on the way out, so mail from the platform arrives looking like mail from a person.
A meeting agreed on a call is never lost because somebody else's service was slow. The booking is saved here first, then the room and the calendar entry.
Move the meeting an hour and the Zoom room moves with it, on the link guests already have. Delete the booking and the room goes too, with nobody chasing it.
The join link is made by the calendar itself, on the same save that books the meeting, so nobody hunts for it later. One Google account is the whole setup.
Pick Teams on a booking and the join link is written into the invitation guests receive, so nobody chases it in a follow-up. A room you own travels too.
Mail files itself against the lead, on a rule short enough to print: the addresses on the lead, matched exactly. No domain guessing, and nothing to dispute.
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