Edmund Documentation
/USER MANUAL

Tags

How an administrator builds the organization's tag structure in Edmund: create a group, add tags inside it, assign them to projects, and keep the naming disciplined so filtering stays useful.

Administrator Last reviewed July 2026

Tags let you organize your projects and maintenance journals with groups of tags. You define a structure once — groups such as Location, Hall, Line, or Machine — then assign the tags inside them to projects so the list stays filterable and a technician’s search lands on the right machine.

Warning

Tags are an optional feature. The Tags area only appears when the tags feature is enabled for your organization — if you don’t see it, it isn’t turned on. See Organization settings.

Tags: groups with tags inside, assigned to projects to filter and find them.

Groups and tags

A group holds tags of the same kind. Groups usually mirror how your plant is already organized:

GroupExample tags
Locationsite or plant codes
HallHall A, Hall B
LineL11, PU6
Machinepress, conveyor, degreasing line

A tag is one concrete value inside a group. If the group is Location, the tags are your actual site codes.

Build the structure

  1. Decide what you’ll filter by. Work out how you want to sort projects — that’s your set of groups. Keep it small; every group should answer a question someone actually asks.

  2. Create a group. In Organization settings → Tags (Štítky), choose Add group (Přidat skupinu), enter a Name, and save.

  3. Add tags to the group. Choose Add tag (Přidat štítek), fill in the Name, pick the right Group, and save. Keep names short and consistent.

  4. Assign tags to projects. Open a project’s settings and apply the relevant tag from each group. Tagged projects can then be filtered and found.

Tip

One tag should state one clear property of a project. Don’t overload a single tag with several meanings — that’s what a second group is for.

Keep the structure healthy

You’ll come back to Tags as projects are added, so keep the structure disciplined:

  • Add new tags into the right group, not as loose one-offs.
  • Don’t create duplicate names for the same meaning.
  • When your internal structure changes — a hall renamed, a line moved — update the existing projects too.
  • Name groups and tags so a new user understands them without asking.

A clean structure pays off beyond projects: a maintenance journal can also be assigned by tag, so it reaches the right projects automatically — see Maintenance journal.