Skip to main content

Tags

Overview​

Tags classify guests within an event and optionally include a hierarchy (Subtags). They enable segmentation for operations (reports, emails, badges) and are event‑scoped. You can create, edit, soft‑delete (trash), restore, and permanently delete tags. When a tag is in use by guests, you can reassign those guests before deletion.

📌 Why Tags?

Rapid segmentation for Emails, Badges, Reports with optional hierarchy and safe reassignment.

Interface Preview (Placeholders)​

Tags ListCreate/Edit Tag
Tags listingCreate Tag form
Add Real Screenshots

Replace placeholders with:

  • /images/tags/tags-list.png (full list with filters Active / Deleted / All)
  • /images/tags/tag-create.png (create/edit form showing Subtags rows)

Quick Start​

  1. Go to Event > Tags.
  2. Click Create Tag; enter Name + (optional) Description.
  3. (Optional) Add Subtags rows.
  4. Save.
  5. Use row actions to Edit, Delete (trash), Restore, or Permanently delete.
  • Listing: Event > Tags (filter Active / Deleted / All)
  • Create: Tags > Create Tag
  • Edit: Row action > Edit
  • Delete / Restore / Force Delete: Row action (contextual)

Common Tasks​

Create a tag and subtags​

  1. Create Tag.
  2. Enter Tag Name (required) + Description (optional).
  3. Click + Add Subtag for each new subtag (Name + Description).
  4. Save.

Edit a tag / subtags​

  1. Row action Edit.
  2. Update fields.
  3. Add / modify / remove subtags.
  4. Update Tag.

Soft delete a tag​

  • Click Delete. If guests use the tag, a Move Guests modal appears to reassign first.

Restore a tag​

  • Filter Deleted; click Restore.

Permanently delete​

  • Only when in Deleted state. Action is irreversible.

Filter list​

  • Dropdown: Active / Deleted / All. Deleted rows are grey with badge.

Reassign Flow (Deleting Tag In Use)​

  1. Delete action triggers Move Guests modal if guests found.
  2. Select target tag (cannot be the same).
  3. Confirm – reassignment happens atomically, original tag moves to trash.

Table Reference​

  • Name
  • Subtags (pipe‑separated names or dash if none)
  • Deleted badge (when trashed)
  • Actions (state + permission dependent)

Permissions​

ActionPermission
View Tagstag.viewAny
Create Tagtag.create
Edit Tagtag.edit
Delete (trash)tag.delete
Restoretag.restore
Permanently Deletetag.forceDelete

Data Model (Conceptual)​

  • tags: id, event_id, name, description, deleted_at
  • sub_tags: id, tag_id, name, description, deleted_at
  • guests: id, tag_id, …

Behavior:

  • Each guest references exactly one tag.
  • Subtags belong to a tag; edited inline.
  • Soft delete sets deleted_at; restore clears it; force delete removes the row.

Best Practices​

  • Keep names short & unambiguous (VIP, Staff, Sponsor).
  • Use Subtags for finer roles/levels.
  • Prefer soft delete for audit trail; permanently delete only when sure.

Troubleshooting​

IssueCauseFix
Can’t deleteTag in useReassign guests first
Restore missingNot in Deleted stateSwitch filter to Deleted
Actions hiddenMissing permissionRequest appropriate permission

FAQs​

  • Multiple tags per guest? Not supported; use Subtags for hierarchy.
  • Subtags transfer when reassigning? Reassignment updates guests’ main tag only.
  • Subtags after delete? Removed with parent (soft or force).

Add Your Screenshots​

Suggested real asset paths:

  • /images/tags/tags-list.png
  • /images/tags/tag-create.png

Markdown examples:

![Tags List](/images/tags/tags-list.png)
![Create Tag](/images/tags/tag-create.png)

Last updated: 2025-11-11