Org, projects & QR codes
How projects are structured in Edmund — one per machine or line — what a project's settings control (name, suggestions, data sources, tags), and how each project's QR code opens its chat and prints for the floor.
In Edmund, everything a technician asks about is organized into projects, and each project carries its own QR code that opens that project’s chat. This page covers how projects are laid out, what each project’s settings control, and how to get the codes onto the floor.
A project is one machine or line
A project should map to one machine or one production line — keep it that narrow. A project that tries to cover a whole hall mixes documents, journals, and answers that belong to different equipment, and technicians end up sifting results that don’t apply to the machine in front of them.
Name each project after the real asset, using whatever your team already calls it on the floor — the asset tag, the cell number, or the common name. That keeps projects easy to recognize and to match to their printed codes. Which projects you see is controlled by your team; team membership is what grants access to a project.
Setting up the project structure — creating, renaming, and deleting projects, and changing project settings such as suggestions, data sources and tags — is an administrator action. As an Expert you work inside a project: its documents, PLC programs, and journal records.
Project settings
Open a project’s settings from its left navigation, under Nastavení projektu (Project settings). From here an administrator can:
Project name — set the name shown for the project across Edmund.
Project suggestions — activate up to five starter prompts for this project’s chat. These override the organization’s default suggestions when this machine’s typical questions differ from the rest of the plant. See Suggestions.
Data sources — the databases connected to this project. Manage description (Spravovat popis) adds a project-specific description that helps Edmund interpret that data for this machine. Connecting a database happens at the organization level; see Data sources.
If the tags feature is enabled for your organization, project settings is also where an administrator assigns the project its tags, which keep a growing list of projects filterable; see Tags. Deleting a project is also done here and is permanent.
QR codes
Every project has its own QR code, shown as a QR icon on the project’s card on the Projects page. Scanning it opens that project’s chat, so the codes belong where the work happens — on the machine, guard, or panel door.
On the Projects page, click the QR icon on a project card. A dialog shows that project’s code with Download as PDF (Stáhnout jako PDF).
A project's QR code opens its chat — download it as a PDF to print. To export every project’s code at once, use Download QR codes (Stáhnout QR kódy) at the top right of the Projects page. This bulk export is an administrator action.
Print each code and place it on its machine or line, somewhere a technician can reach without climbing or opening a guarded area.
Print codes laminated or under a clear cover. Floor labels collect coolant and dust, and a code that won’t scan sends the technician back to a manual lookup.
Where these settings live
Project settings sit with each project; everything organization-wide — name, language, logo, limits, and feature flags — lives in Organization settings. Features such as tags are optional per organization, so what appears in project settings can vary between plants.