I will use laravel notifications table for handling clients notifications instead of creating the below two tables:.

notifications

client_notification

so the relation between users and notifications will be one to many instead of many to many this will be helpful because: 1) No need for many to many relationship // faster querying
2) Laravel notifications table uses polymorphic relationship so we can upgrade the app to send notifications to admins also if we want
3) save some time :) // Otherwise i will return back to the default solution if something went wrong.

In client_govornorate table & bood_type_client table can be modified.
Instead of using to tables we can use just one table using polymorphic relationship.

In site settings table: Instead of create 5 fields or more for every social link and it can be increased in the future of the application .
I will create one field {social_links} and it will contain a json data.
ex:
{ facebook: 'http://www.facebook.com/blood-bank', twitter: 'http://www.twitter.com/blood-bank' }

Some relations we will not use it, so i did not implement it.