Depending on your organization’s IT capabilities, users can be managed individually or in bulk, or even synchronized with third-party directory services.
Learn more about managing users…
😲 Customers get their own user accounts, too?
Yes! Unlike e.g. OTRS, Zammad needs to store accounts for everyone who communicates through the system.
Why? It helps us do things like show all tickets from a certain customer.
How? Zammad checks the sender of every incoming message at every inbox it monitors, and if it doesn’t recognize the address, ✨ poof—new customer account!
(Your customers never need to set a password. Of course, they can if they want to, but the account will be there even if they never use it.)
Reference Guide: User Details¶
Most of the attributes you can set on user accounts are self-explanatory. The ones that aren’t are described below.
🕵️ Admins aren’t the only ones who can change these settings.
In most cases, agents can, too (using the new ticket dialog, search bar or the ticket pane).
- 👤 Login
A user’s email and login may differ, but either one can be used to sign in.
This attribute cannot be set via the Admin Panel. Instead, use the Zammad console, the REST API, or CSV import.
- 🔑 Password
Yes, administrators really do have the power to change other users’ passwords.
(Agents do not, though.)
- 🏢 Organization
Unternehmen are a way to group customers together (usually, members of the same company). This allows you to do things like view all tickets for that company or set up special Triggers that fire only for those customers.
🚫 You can’t assign a customer to an organization that doesn’t exist yet.
To add one, go to Manage > Organizations in the Admin Panel.
- 🏤 Secondary Organizations
This option allows you to assign more organizations, in addition to the user’s primary organization.
Secondary organizations behave the same like the primary ones with one exception: Secondaries are not as highlighted like their primaries.
Listings for all organizational tickets are not affected by this. Zammad will mix primary and secondary organization tickets together.
While the number of secondary organizations is not limited directly, you may want to keep this to a reasonable number of organizations.
30-40 organizations at maximum should be good enough.
- 👑 VIP
This flag is a way for your team to indicate high-status customers. Just as with organizations, you can set up special Triggers, Automatisierungen jobs, SLAs, and Übersichten just for VIPs.
- 📑 Note
Notes are visible to all staff members, including agents.
😵 Are you using the Note field to keep track of your own “custom” user attributes?
Wish you could add your own fields to the New/Edit User dialog?
You can! To learn more, see Objects.
- ▶️ Active
Disabling this flag is a soft alternative to deleting a user. So what’s the difference?
There is no way to restore a deleted user; inactive users can be reactivated at any time.
When a user is deleted, all their associated tickets are lost, as well; deactivating a user keeps all associated tickets intact.
Inactive users still appear in search results:
- 🔓 Permissions
Under this heading, you can manage two separate (but related) user details:
Rollen dictate what users can do in the system. If you need to grant someone privileges to edit the knowledge base or access part of the admin panel, roles are the answer.
Group Access Levels dictate which tickets an agent can work with. If someone’s not receiving notifications for incoming tickets or can’t be assigned a ticket, group access levels are likely to blame.
🤔 Huh? I don’t see the group access table…
The group access table is only visible in agent profiles, when there is more than one active group in the system.