Templates

Sharing templates

Templates start private. Share one with specific people, teams, or the whole organization — and use an explicit exclusion when a team grant reaches someone it shouldn't.

Every template starts Private — only you. Nobody else can find it, open it, or apply it; it won't appear in anyone else's Templates list or apply picker.

Share it when it's ready, from the Share… action on the template's row or in the builder header.

Access levels

Level	What it allows
Can use	View and apply the template
Can edit	View, apply, and edit it
Exclude	Blocked, even if a team or the organization grants access
Remove from list	Drop this entry and fall back to team or organization access

You can grant to individual people, teams, or the whole organization.

Exclude and Remove are not the same

Remove from list deletes the entry, after which the person falls back to whatever their team or the organization gives them. Exclude is an active block that survives those grants. Use Remove to undo a mistake; use Exclude to carve one person out of a team that should otherwise have access.

How access is worked out

When several rules could apply to one person, DevStride settles it in this order:

Their own entry wins — whatever it says, including Exclude.
Otherwise, an Exclude on any of their teams wins.
Otherwise, the best level any of their teams grants.
Otherwise, the organization level.

The share dialog spells out the consequences inline. If you exclude someone who is on a team you've granted access, the row tells you the person-level exclusion wins and they won't see the template.

At the bottom, a plain-English summary states the effective audience — who can use it, who can also edit it, and who can change sharing.

Only the owner — the person who created it — or an administrator holding MANAGE_ALL_ITEM_TEMPLATES.

Notably, Can edit does not include sharing or deleting. Someone can improve your template's content without being able to change who sees it or remove it.

Ownership stays with the author

There's no way to hand a template to someone else. The author remains the owner, and their own access is always re-asserted when sharing is saved — you cannot accidentally lock yourself out of your own template. If ownership genuinely needs to move, have the new owner Duplicate it: the copy is theirs.

Duplicating instead of editing

Anyone who can see a template can Duplicate it, provided they can create templates at all. The copy is named <name> (copy), is owned by them, and starts private.

This is the intended path when you want to adapt someone else's template. Opening a template you can't edit gives you a read-only builder with Duplicate to edit right there.

Reading the audience

The Audience column shows:

Badge	Meaning
Private	Only you
Organization	Everyone in the organization
Shared · 1 person, 2 teams	Specific people and teams
Shared with you	Someone shared it with you

A row you can see but not change also reads Can use · not editable, so you know before you open it.

Deleting

Deleting asks for confirmation and warns you it can't be undone.

Work already created from a template is never affected. Applied work is ordinary items and workstreams with no live link back to the template — deleting the template leaves every item it ever created exactly where it is.

Applying a template

Dry-run a draft with Try it, then walk the four-step apply flow — choose a location and template, fill in variables, review an exact server-side preview, and create the work.

Template health