Freescout Restricted Customers
Find a file
Antoine Le Gonidec 2f9745f9d8
1.0.0 stable release
This is only a version bump from the previous 0.9.0 release.
2024-07-18 11:27:12 +02:00
Config Add missing copyright statements 2024-07-12 12:36:00 +02:00
Console/Commands Fix Entities namespace 2024-07-10 17:26:43 +02:00
Database/Migrations Prevent the creation of duplicated e-mails for a given Customer 2024-07-11 12:38:06 +02:00
Entities Rely on hooks to link Customers to a Mailbox 2024-07-11 12:10:41 +02:00
Http Improve routes overrides 2024-07-12 12:58:38 +02:00
Providers Add missing copyright statements 2024-07-12 12:36:00 +02:00
Public Add the required "Public" directory 2024-07-10 17:18:30 +02:00
Resources Drop the ability to link a Customer to multiple Mailboxes 2024-07-12 12:33:28 +02:00
CHANGELOG 1.0.0 stable release 2024-07-18 11:27:12 +02:00
composer.json 1.0.0 stable release 2024-07-18 11:27:12 +02:00
COPYING Import a copy of the GNU Affero General Public License (AGPL) 2024-07-03 12:43:15 +02:00
module.json 1.0.0 stable release 2024-07-18 11:27:12 +02:00
README.md 1.0.0 stable release 2024-07-18 11:27:12 +02:00
start.php Add missing copyright statements 2024-07-12 12:36:00 +02:00

Millions Missing France - Freescout Restricted Customers

Description

In a regular Freescout instance, all users have access to the e-mails of all customers. That can easily lead to confidentiality breaches when multiple organizations share a same Freescout instance.

This package tries to provide a solution to this problem, by linking each customer to a specific mailbox. The information related to a customer, especially their e-mail address, is only shown to users with access to the related mailbox.

Data loss warning

When this module is installed, it will link customers to mailboxes. Customers added once this module is active will be linked to mailboxes too. On uninstallation, simply unlinking them could cause several problems:

  • It could break unicity constraints, as two customers linked to disctinct mailboxes are allowed to use the same e-mail address as long as the module is active;
  • It would break the confidentiality promise, by letting all users having access to all customers.

To avoid these problems, on the module uninstallation all the customers linked to mailboxes are dropped from the database. This is an irreversible operation, the customers deleted that way are gone for good.

So it is highly recommended to backup your customers database:

  • Before installing this module;
  • Before uninstalling this module.

Installation instructions

Install the module

Install from the archive

Download the release tarball and extract its content into Modules/MMFRestrictedCustomers.

wget https://port.numenaute.org/MMF/freescout-restricted-customers/archive/1.0.0.tar.gz -O freescout-restricted-customers-1.0.0.tar.gz
tar xf freescout-restricted-customers-1.0.0.tar.gz -C Modules
mv Modules/freescout-restricted-customers Modules/MMFRestrictedCustomers

Install from git

git clone https://port.numenaute.org/MMF/freescout-restricted-customers.git Modules/MMFRestrictedCustomers

Edit the application routes

Routes set in Freescout itself can not be automatically overridden. Overriding them has to be done manually, in the following file:

routes/web.php

This section of the file:

// Customers
Route::get('/customers/{id}/edit', 'CustomersController@update')->name('customers.update');
Route::post('/customers/{id}/edit', 'CustomersController@updateSave');
Route::get('/customers/{id}/', 'CustomersController@conversations')->name('customers.conversations');
Route::get('/customers/ajax-search', ['uses' => 'CustomersController@ajaxSearch', 'laroute' => true])->name('customers.ajax_search');
Route::post('/customers/ajax', ['uses' => 'CustomersController@ajax', 'laroute' => true])->name('customers.ajax');

should be replaced with:

// Customers
Route::get('/customers/{id}/edit', '\Modules\MMFRestrictedCustomers\Http\Controllers\CustomersController@update')->name('customers.update');
Route::post('/customers/{id}/edit', 'CustomersController@updateSave');
Route::get('/customers/{id}/', '\Modules\MMFRestrictedCustomers\Http\Controllers\CustomersController@conversations')->name('customers.conversations');
Route::get('/customers/ajax-search', ['uses' => '\Modules\MMFRestrictedCustomers\Http\Controllers\CustomersController@ajaxSearch', 'laroute' => true])->name('customers.ajax_search');
Route::post('/customers/ajax', ['uses' => '\Modules\MMFRestrictedCustomers\Http\Controllers\CustomersController@ajax', 'laroute' => true])->name('customers.ajax');

Edit the artisan commands

Console commands set in other modules or in Freescout itself can not be automatically overridden. Overriding them has to be done manually, in the following file.

app/Console/Kernel.php

At the lines 107-108, this:

        $fetch_command_identifier = \Helper::getWorkerIdentifier('freescout:fetch-emails');
        $fetch_command_name = 'freescout:fetch-emails'

should be replaced with:

        $fetch_command_identifier = \Helper::getWorkerIdentifier('mmfrestrictedcustomers:fetch-emails');
        $fetch_command_name = 'mmfrestrictedcustomers:fetch-emails'

Update the database schema

php artisan migrate

Use the updated views

Beware that this will overwrite any customization you might have done to the following templates:

  • resources/views/conversations/search.blade.php
php artisan vendor:publish --provider='Modules\MMFRestrictedCustomers\Providers\MMFRestrictedCustomersServiceProvider' --tag='views' --force