Users, roles & teams
How an administrator invites users by email, assigns one of Edmund's four roles, and uses teams to control which projects each person can see.
Everyone who uses Edmund has a login, a role, and — for anyone who isn’t an administrator — a team. You manage all three from Organization settings. This page covers day-to-day user administration; for the full capability-by-capability breakdown of the four roles, see roles & permissions.
Invite users
Open Organization settings → Users (Uživatelé). Each row shows a person’s Role, their Teams, and their Status — for example Přijato once they’ve joined, or pending while an invite is still outstanding. From here you can also open View permissions (Zobrazit oprávnění) or invite someone new.
Select Invite user (Pozvat uživatele).
Choose the role for the person you’re inviting.
Enter the email address. You can add several addresses at once to invite more than one person with the same role.
Pick the team they should belong to — teams are explained in Teams and project visibility below — then send the invite.
Edmund emails each person an invitation automatically. The invitation is valid for 24 hours — after that you’ll need to send a new one.
Your organization has a maximum number of users, shown in Organization settings → General (Obecné) — see Organization settings. Once you reach it, you can’t invite anyone else; contact the Edmund team to raise the limit.
Roles
Edmund has four roles. Each user has exactly one, and it decides what they can do across the organization:
- Administrátor (Administrator) — full control: manages users, teams, projects, organization settings and data sources, curates knowledge, and uses chat.
- Uživatel Expert (Expert user) — curates the knowledge behind answers (documents, PLC programs and maintenance-journal records) and uses chat.
- Uživatel (User) — uses chat, views the documents and knowledge behind answers, and can rate replies; doesn’t manage knowledge.
- Čtenář (Reader) — read-only: can view a project’s documents and knowledge but can’t use chat or leave feedback.
Change a person’s role any time from the Role dropdown on their row. The Users screen also has a built-in View permissions matrix; the same breakdown, line by line, is on roles & permissions.
Teams and project visibility
Teams are Edmund’s access model — teams decide which projects a person can see, not their role. Assign projects to a team, add people to the team, and its members can see those projects.
Non-admin users see the projects belonging to their team, plus any project not assigned to a team. Administrators see every project regardless of team.
Go to Organization settings → Teams (Týmy) and select Add team.
Name the team, choose the projects that belong to it, and add the users who are members.
A non-admin user with no team sees only unassigned projects — often nothing useful to ask about. Put people in a team when you invite them so they have a machine to work with from day one.