How Taggie is structured

HighLevel presents tags as one flat list. Taggie adds a hierarchy for the people who have to name, find and maintain them.

The hierarchy at a glance

Workspace
└── Folder
    └── Folder (as deep as you need)
        └── Tag group
            └── Category
                └── Tag
                    └── Parts

Workspace

A workspace is the boundary around one taxonomy. It holds its own folders, tag groups, members, notes, billing coverage and HighLevel connection.

Use separate workspaces when the structures or CRM locations need to stand on their own.

Folders

Folders organize tag groups. They can nest to any depth, so a broad area can contain smaller areas without forcing that structure into every tag name.

Archiving takes a folder or another object out of the active workspace without deleting it. Deleted items go to trash for 30 days and can be restored during that window.

Tag groups

A tag group is the working unit for related tags. It can have its own naming-template override and display settings, and it can be synced on its own.

Folder rows roll up sync issues from the groups below them, so drift remains visible higher in the structure.

Categories

Categories split a group into ordered sets. A category can override the group or workspace naming template. If the template includes {cat_num}, the category’s position becomes part of every computed name in it.

Tags and parts

A tag is the local record that maps to a remote HighLevel tag. Its final name is computed from the active template.

Parts are the pieces of a multi-part tag. Their separator is configured separately from the main template, so a taxonomy can control both the outer name and how the parts join together.

Ordering can affect naming

Order is usually visual. It becomes a naming input when you use {cat_num} or {tag_num}. Reordering then changes the computed name, which means it can produce a rename on the next sync.

Taggie shows the before and after first. Treat any reorder that uses ordinal tokens as a naming change, not merely a layout change.