Update file names for images in the imported posts
|
|
@ -17,9 +17,9 @@ Give this application permissions to read, write and modify (but not delete) ema
|
||||||
|
|
||||||
1. If the final step fails with a ‘403 forbidden’ error, it may be necessary to log into the helpdesk as the user, go to ‘Profile’:
|
1. If the final step fails with a ‘403 forbidden’ error, it may be necessary to log into the helpdesk as the user, go to ‘Profile’:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
From there, navigate to ‘linked accounts’, and select ‘remove’:
|
From there, navigate to ‘linked accounts’, and select ‘remove’:
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -9,29 +9,29 @@ sidebar_position: 100
|
||||||
|
|
||||||
1. To check whether the PGP plugin is installed, check the Integrations tab in Zammad. This should show ‘PGP’ in the list of integrations. A green dot will appear next to its name if the plugin is enabled - here the plugin is not yet enabled:
|
1. To check whether the PGP plugin is installed, check the Integrations tab in Zammad. This should show ‘PGP’ in the list of integrations. A green dot will appear next to its name if the plugin is enabled - here the plugin is not yet enabled:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
1. To enable the plugin, open the settings for ‘PGP’, and toggle the switch in the top left corner of the page:
|
1. To enable the plugin, open the settings for ‘PGP’, and toggle the switch in the top left corner of the page:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Sending encrypted email to a user
|
## Sending encrypted email to a user
|
||||||
|
|
||||||
1. The ‘Public and Private Keys’ section will display all the known encryption keys and associated emails. To be able to send encrypted email to an email address, it is necessary to upload the public key associated with that email address. Usually the public keys will be sent from the PGP users themselves, as attachments to tickets created via email. Here’s an example of such a ticket:
|
1. The ‘Public and Private Keys’ section will display all the known encryption keys and associated emails. To be able to send encrypted email to an email address, it is necessary to upload the public key associated with that email address. Usually the public keys will be sent from the PGP users themselves, as attachments to tickets created via email. Here’s an example of such a ticket:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
1. To be able to reply to this user using encrypted email, download this attachment and upload it to the ‘Public and Private Keys’ section of the PGP integrations, by selecting ‘Add Public Key’, and then ‘Browse’:
|
1. To be able to reply to this user using encrypted email, download this attachment and upload it to the ‘Public and Private Keys’ section of the PGP integrations, by selecting ‘Add Public Key’, and then ‘Browse’:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
1. The PGP key fingerprint and email will now show up in the list:
|
1. The PGP key fingerprint and email will now show up in the list:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
1. Replying on the ticket will now show the option to ‘Encrypt’, enabled by default. This means the reply will be sent encrypted. The padlock can be clicked to disable encryption.:
|
1. Replying on the ticket will now show the option to ‘Encrypt’, enabled by default. This means the reply will be sent encrypted. The padlock can be clicked to disable encryption.:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Receiving encrypted email from a user:
|
## Receiving encrypted email from a user:
|
||||||
|
|
||||||
|
|
@ -81,15 +81,15 @@ gpg --export-secret-key -a helpdesk > helpdesk.priv
|
||||||
|
|
||||||
1. The next step is to upload the helpdesk’s public and private keys to Zammad. The private key will be used to decrypt messages that were sent encrypted to the helpdesk. The public key will be distributed to the helpdesk users who wish to send encrypted email. First, upload the public key to the ‘Public and Private Keys’ section of the PGP integrations, by selecting ‘Add Public Key’, and then ‘Browse’ and selecting the public key exported in the previous step:
|
1. The next step is to upload the helpdesk’s public and private keys to Zammad. The private key will be used to decrypt messages that were sent encrypted to the helpdesk. The public key will be distributed to the helpdesk users who wish to send encrypted email. First, upload the public key to the ‘Public and Private Keys’ section of the PGP integrations, by selecting ‘Add Public Key’, and then ‘Browse’ and selecting the public key exported in the previous step:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
1. Now add the private key, by selecting ‘Add Private Key’, and then ‘Browse’ and selecting the private key exported in the previous step:
|
1. Now add the private key, by selecting ‘Add Private Key’, and then ‘Browse’ and selecting the private key exported in the previous step:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
The display should now indicate the private key was uploaded
|
The display should now indicate the private key was uploaded
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
1. Ticket replies will now be sent signed by default. When an encrypted email is sent by a user, its contents will automatically be decrypted and displayed in a ticket.
|
1. Ticket replies will now be sent signed by default. When an encrypted email is sent by a user, its contents will automatically be decrypted and displayed in a ticket.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -48,7 +48,7 @@ In the Admin panel, go the Groups tab, and select New Group.
|
||||||
|
|
||||||
Add the group name to match the name of the project. The “Assignment timeout” can be left blank. If a signature is already configured it can be selected under “Signature”. If this project uses an Email channel - select it from the drop-down menu under “Email”, then hit Submit.
|
Add the group name to match the name of the project. The “Assignment timeout” can be left blank. If a signature is already configured it can be selected under “Signature”. If this project uses an Email channel - select it from the drop-down menu under “Email”, then hit Submit.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## 2. Create an associated Agent Role
|
## 2. Create an associated Agent Role
|
||||||
|
|
||||||
|
|
@ -56,7 +56,7 @@ Roles are required to separate permissions between the groups, as they allow cus
|
||||||
|
|
||||||
In the Admin panel, go the Roles tab, and select New Role.
|
In the Admin panel, go the Roles tab, and select New Role.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Add the name of the new role, then scroll down to select the permissions for this role. Scroll over “admin”, “chat”, “cti”, “knowledge base” and “report” without making selecting them. Do select “agent”, and in the group table below it select only “full” for the group created above. Also select “user_preferences”.
|
Add the name of the new role, then scroll down to select the permissions for this role. Scroll over “admin”, “chat”, “cti”, “knowledge base” and “report” without making selecting them. Do select “agent”, and in the group table below it select only “full” for the group created above. Also select “user_preferences”.
|
||||||
|
|
||||||
|
|
@ -64,13 +64,13 @@ Under permissions, “Default at signup” should be left to “no”.
|
||||||
|
|
||||||
Apply the changes by hitting “Submit”.
|
Apply the changes by hitting “Submit”.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## 3. Create overviews for the new role
|
## 3. Create overviews for the new role
|
||||||
|
|
||||||
By default, Zammad comes with the following Overviews:
|
By default, Zammad comes with the following Overviews:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
The default “Unassigned and Open” and “Open” overviews that come with Zammad allow all agents to see unassigned and open tickets, regardless of their group, even if agents do not have permissions for that group. Agents would not be able to modify tickets without the necessary permissions, however to “hide” the incoming tickets of a group from agents not belonging to that group, new Overviews must be created to take the place of the default “Unassigned and Open” and “Open” overviews that come with Zammad.
|
The default “Unassigned and Open” and “Open” overviews that come with Zammad allow all agents to see unassigned and open tickets, regardless of their group, even if agents do not have permissions for that group. Agents would not be able to modify tickets without the necessary permissions, however to “hide” the incoming tickets of a group from agents not belonging to that group, new Overviews must be created to take the place of the default “Unassigned and Open” and “Open” overviews that come with Zammad.
|
||||||
|
|
||||||
|
|
@ -78,11 +78,11 @@ The default “Unassigned and Open” and “Open” overviews that come with Za
|
||||||
|
|
||||||
In the Admin panel, go the Overviews tab, and select New Overview. Give it the name “Unassigned & Open - \<project-name\>” and then make the overview available for the role created in the previous step:
|
In the Admin panel, go the Overviews tab, and select New Overview. Give it the name “Unassigned & Open - \<project-name\>” and then make the overview available for the role created in the previous step:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Scroll down, and under “Conditions for shown tickets”, select “State” new and open; and use the “+” button on the right to add another condition. Change the condition to limit the shown tickets to the group created in the first step. Ensure the group is highlighted as selected before hitting “Submit”, as in the example below:
|
Scroll down, and under “Conditions for shown tickets”, select “State” new and open; and use the “+” button on the right to add another condition. Change the condition to limit the shown tickets to the group created in the first step. Ensure the group is highlighted as selected before hitting “Submit”, as in the example below:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
3.2 Creating a new overview for open tickets:
|
3.2 Creating a new overview for open tickets:
|
||||||
|
|
||||||
|
|
@ -92,7 +92,7 @@ If you want to add a second overview for only open tickets, repeat the previous
|
||||||
|
|
||||||
Edit the “My Assigned Tickets”, “My Subscribed Tickets” and optionally the “My Pending Reached Tickets” default overviews to make them available to the role created earlier:
|
Edit the “My Assigned Tickets”, “My Subscribed Tickets” and optionally the “My Pending Reached Tickets” default overviews to make them available to the role created earlier:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
<aside>
|
<aside>
|
||||||
💡 Note that we did not discuss the “Pending reached” or “Escalated” overviews, but the same principles apply - as they have the option of “leaking” information about tickets for other groups new overviews must be created in their place.
|
💡 Note that we did not discuss the “Pending reached” or “Escalated” overviews, but the same principles apply - as they have the option of “leaking” information about tickets for other groups new overviews must be created in their place.
|
||||||
|
|
@ -104,7 +104,7 @@ Select the Email channel from the Admin panel. Click the group shown under “De
|
||||||
|
|
||||||
In the screenshot below we show the email channel for this helpdesk is configured to send tickets straight to group “Demo group 1”:
|
In the screenshot below we show the email channel for this helpdesk is configured to send tickets straight to group “Demo group 1”:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
<aside>
|
<aside>
|
||||||
💡 Note: A ticket can be added to a group by default if the channel is configured to do so. Another way that a ticket may be added to a group is manually, by changing the “Group” tab of a ticket by an agent with appropriate permissions.
|
💡 Note: A ticket can be added to a group by default if the channel is configured to do so. Another way that a ticket may be added to a group is manually, by changing the “Group” tab of a ticket by an agent with appropriate permissions.
|
||||||
|
|
@ -115,13 +115,13 @@ In the screenshot below we show the email channel for this helpdesk is configure
|
||||||
|
|
||||||
Agents are added by selecting ‘New Users’ from the ‘Users’ admin tab. When adding a new agent user, ensure to only give assign them the role created in step 2, and untick the default “Agent” and “Customer” roles. Moreover, in the group table underneath, only select “Full” permissions for the group created in step 1. The screenshot below shows a configuration example:
|
Agents are added by selecting ‘New Users’ from the ‘Users’ admin tab. When adding a new agent user, ensure to only give assign them the role created in step 2, and untick the default “Agent” and “Customer” roles. Moreover, in the group table underneath, only select “Full” permissions for the group created in step 1. The screenshot below shows a configuration example:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### Finishing and checking agent configurations
|
### Finishing and checking agent configurations
|
||||||
|
|
||||||
To check the configuration for an agent, an administrator can view the helpdesk from that user’s perspective. In the Users tab, click the 3 dots on the right of the target user, and select “View from user’s perspective”:
|
To check the configuration for an agent, an administrator can view the helpdesk from that user’s perspective. In the Users tab, click the 3 dots on the right of the target user, and select “View from user’s perspective”:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
This will allow you to view the helpdesk as the user - and going to overviews, only the overviews defined in step 3 should be visible.
|
This will allow you to view the helpdesk as the user - and going to overviews, only the overviews defined in step 3 should be visible.
|
||||||
|
|
||||||
|
|
@ -131,4 +131,4 @@ Access the user’s Profile from the bottom left corner panel, then navigate to
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Before Width: | Height: | Size: 24 KiB After Width: | Height: | Size: 24 KiB |
|
Before Width: | Height: | Size: 8.3 KiB After Width: | Height: | Size: 8.3 KiB |
|
Before Width: | Height: | Size: 26 KiB After Width: | Height: | Size: 26 KiB |
|
Before Width: | Height: | Size: 31 KiB After Width: | Height: | Size: 31 KiB |
|
Before Width: | Height: | Size: 29 KiB After Width: | Height: | Size: 29 KiB |
|
Before Width: | Height: | Size: 94 KiB After Width: | Height: | Size: 94 KiB |
|
Before Width: | Height: | Size: 33 KiB After Width: | Height: | Size: 33 KiB |
|
Before Width: | Height: | Size: 123 KiB After Width: | Height: | Size: 123 KiB |
|
Before Width: | Height: | Size: 19 KiB After Width: | Height: | Size: 19 KiB |
|
Before Width: | Height: | Size: 31 KiB After Width: | Height: | Size: 31 KiB |
|
Before Width: | Height: | Size: 23 KiB After Width: | Height: | Size: 23 KiB |
|
Before Width: | Height: | Size: 175 KiB After Width: | Height: | Size: 175 KiB |
|
Before Width: | Height: | Size: 36 KiB After Width: | Height: | Size: 36 KiB |
|
Before Width: | Height: | Size: 200 KiB After Width: | Height: | Size: 200 KiB |
|
Before Width: | Height: | Size: 103 KiB After Width: | Height: | Size: 103 KiB |
|
Before Width: | Height: | Size: 139 KiB After Width: | Height: | Size: 139 KiB |
|
Before Width: | Height: | Size: 157 KiB After Width: | Height: | Size: 157 KiB |
|
Before Width: | Height: | Size: 147 KiB After Width: | Height: | Size: 147 KiB |
|
Before Width: | Height: | Size: 146 KiB After Width: | Height: | Size: 146 KiB |
|
Before Width: | Height: | Size: 81 KiB After Width: | Height: | Size: 81 KiB |
|
Before Width: | Height: | Size: 49 KiB After Width: | Height: | Size: 49 KiB |
|
Before Width: | Height: | Size: 329 KiB After Width: | Height: | Size: 329 KiB |