Edmund Documentation
/USER MANUAL

Roles & permissions

The four Edmund roles — Administrator, Expert user, User and Reader — and the exact permission matrix for who can chat, give feedback, curate documents and journals, and administer the organization.

Administrator Last reviewed July 2026

Edmund has four roles. Each one decides who can chat, who gives feedback, who curates the knowledge behind the answers, and who administers the organization. A person’s role is set in Organization settings → Users (Uživatelé), and which projects they can reach is decided separately by their team — the day-to-day administration is covered in Users & teams.

The Users list — set each person's role and open View permissions.

The four roles

  • Administrator (Administrátor) — full control of the organization. Everything an Expert user can do, plus: create, update and delete projects; connect and manage data sources; manage users, teams, maintenance journals and suggestions; change organization settings; and view analytics.
  • Expert user (Uživatel Expert) — uses chat and gives feedback, and curates knowledge on the projects their team can reach: manages documents, PLC programs and maintenance-journal records. Does not administer the organization.
  • User (Uživatel) — uses chat, gives feedback, and views documents, PLC programs, data sources and maintenance journals. Does not change the knowledge or any settings.
  • Reader (Čtenář) — view only. Can open documents, PLC programs, data sources and journals, but cannot use chat or give feedback.

Permission matrix

This is the same matrix shown in the app under Zobrazit oprávnění (View permissions).

CapabilityAdministratorExpert userUserReader
Use chatYesYesYes
Give feedback on answersYesYesYes
View documents, PLC programs, data sources & journalsYesYesYesYes
Manage documents & PLC programsYesYes
Manage maintenance-journal recordsYesYes
Manage project data sourcesYes
Create, update or delete projectsYes
Manage users, teams, org settings & analyticsYes
Manage org data sources & maintenance journalsYes

Projects follow teams

Roles set what a person can do; teams set which projects they can do it in. Administrators see every project in the organization. Expert users, Users and Readers see unassigned projects plus the projects belonging to their teams — so team membership is how you control access. Assign people to teams under Týmy (Teams), where each team lists the projects it can reach.

Tip

The app enforces these permissions for you — a capability a role doesn’t have simply won’t appear. This page is a reference for what to expect, not where access is granted. If someone needs a capability they don’t see, change their role in Users (Uživatelé) or their team in Teams (Týmy) — both under Organization settings.