Search and organize templates

A useful template library is easy to search and trust

Templates save time only when people can find the right one and trust that it is current. Search, tags, names, previews, and cleanup all work together. If the library is full of vague names and stale copies, people will go back to duplicating old canvases manually.

Use the Canvas templates manager to search, preview, create from, edit, duplicate, tag, delete, and manage visibility for templates when your role allows those actions.

For the template model, see Canvas templates overview.

Search templates

Open Canvas templates and use the search field. Search by workflow, meeting type, team, client pattern, or template name. Good search terms include retro, kickoff, launch, design review, lesson, interview, planning, or brief.

Suggestions or recent template searches may appear. Use them when they match the workflow you need. Clear the query to return to the full template library.

Template search is for templates. Use Search across ALLO when you are looking for an actual canvas, project, file, person, dashboard, or goal.

Use tags and categories

Tags help people find templates by workflow. Useful tag groups include meeting type, team, business process, customer stage, class, project phase, or review type.

Keep tags predictable. Retrospective and Retro should not both exist unless your workspace has a reason. Launch, Go-to-market, and GTM should be standardized so people can search confidently.

Do not use tags for information that belongs in the template name. A template called Weekly planning does not need a weekly planning tag unless tags drive a specific browse experience.

Name templates for the user’s job

Template names should describe the work someone wants to start. Customer interview, Sprint retrospective, Design critique, Launch brief, and Client kickoff are strong because they match user intent.

Avoid internal names like Team Ops Template v3 copy, Sarah draft, New template, or Canvas template final. Those names make search worse and create doubt about which template is current.

If a template is tied to a specific team or process, include that context: Marketing launch brief, Product sprint planning, or Sales discovery call.

Preview before organizing

Before renaming, deleting, or duplicating a template, preview it. The name may be vague but the structure may still be useful. Preview lets you see whether the template has current prompts, outdated examples, missing pages, or broken structure.

If preview fails, check permission and source canvas access before assuming the template is empty. See Template permissions and visibility.

Duplicate templates for real variants

Duplicate a template when a workflow needs a separate, durable variation. For example, duplicate Customer interview to create Customer interview - enterprise if enterprise interviews need different prompts.

Do not duplicate just to make a one-time canvas. Create a canvas from the template instead. Too many near-identical templates make the library harder to trust.

After duplicating, rename the new template immediately and update tags, visibility, and preview content so people understand why it exists.

Edit or retire stale templates

If a template is outdated but still useful, edit it. Update prompts, remove old examples, fix page names, and make the structure match current practice.

If a template should no longer be used, delete it or restrict it if your role allows. Deleting a template does not delete canvases already created from it. Those canvases are separate work.

If you are not sure whether a template is still needed, rename it with clear owner context or ask the team before deletion. Do not leave a vague stale template in the main library.

Organize templates by ownership

Every custom template should have an owner or owner group. The owner is responsible for keeping it current, deciding visibility, and handling permission issues. Without ownership, old templates quietly become traps.

For team-wide templates, use workspace-visible settings only when the template is ready for broad reuse. Keep drafts private or restricted until they are tested.

For personal templates, use names and visibility that make it clear they are personal, not workspace standards.

Bulk actions and selected templates

The template manager may show additional actions after you select one or more templates. Bulk actions can be useful for tagging, deleting, moving, or changing visibility depending on what your workspace supports.

Be careful with bulk delete or visibility changes. A mistake can hide useful templates from the team or remove the wrong reusable starting point. Preview or review selected names before confirming.

If a bulk action is missing, your role, selection state, template type, or workspace settings may not allow it.

If a template is missing

Clear search, remove tag filters, and confirm the workspace. Check whether you are looking for a standard ALLO template, a workspace custom template, or a creation option like Blank canvas or PDF import.

Ask the template owner whether the template was renamed, restricted, deleted, or replaced. If it was deleted by mistake, check whether recovery is possible through the relevant canvas or Trash.

If another person can see it and you cannot, the issue is likely permission or workspace/account mismatch. When work looks missing has the wider recovery checklist.

Maintenance examples

For a launch template library, keep one current Launch brief, one Launch checklist, one Launch retrospective, and clear variants only when teams truly need them.

For education or training, tag by class, lesson type, or facilitation format. Use names that instructors and students would search for.

For design teams, separate Design critique, User interview synthesis, and Concept review rather than one vague Design template.