There is no license information available for the latest version (2.1.0) of this package.

A Laravel setting manager per user

2.1.0 2019-09-03 19:01 UTC

This package is auto-updated.

Last update: 2024-04-29 03:53:23 UTC


This package provides an easy way to access settings for the current logged in user as well as global app settings.

NOTE: Some features have changed in v2

  1. Changes
  2. About
  3. Install
  4. Usage
  5. HasSettings Trait
  6. Config
  7. Alternate Configuration
  8. Extending
  9. License



  • Added support for float type values.


Support for app specific AND user specific settings has been added.

  • Added AppSetting model and facade
  • Added app_setting helper
  • Added user_setting helper
  • Renamed Setting model and facade to UserSetting
  • Deprecated setting helper
  • Renamed config key setting_model to user_setting_model

If you use the setting helper it will still work but will be removed, so use user_setting instead. The Setting facade has been renamed to UserSetting if you still have code with the Setting facade you can rename the alias in your config/app.php

'aliases' => [
	'Setting' => TaylorNetwork\Setting\Facades\UserSetting::class,


This package uses Laravel's auth function to access the logged in user and return their setting for a given key, or a default value. Similar to the way that the config and env functions work.

When using the HasSettings trait it allows you to access a non-logged in user's settings.

By default if the default value is not set and a setting cannot be found, null is returned. The default value will also be returned if there is no logged in user.

It also includes support for app specific settings via AppSetting


Via Composer

$ composer require taylornetwork/setting

Run database migrations

$ php artisan migrate

You can optionally add the HasSettings trait to your user model to access settings directly.

namespace App;

use Illuminate\Foundation\Auth\User as Authenticatable;
use TaylorNetwork\Setting\Traits\HasSettings;

class User extends Authenticatable
   use HasSettings;
   // ...


Note: the UserSetting and AppSetting classes extend Illuminate\Database\Eloquent\Model

Available Methods

All of these methods are available when using the class or facade.

guard($guard) [UserSetting only]

This will allow you to manually set an auth guard before trying to find an active user.

UserSetting::guard('api')->get('key', 'defaultValue');

get($key, $default = null) [UserSetting and AppSetting]

Get a setting for the app/logged in user or return the default value.



set($key, $value) [UserSetting and AppSetting]

Creates or updates the setting for the logged in user or app.

UserSetting::set('someKey', 'someValue');

AppSetting::set('someKey', 'someValue');



use TaylorNetwork\Setting\UserSetting;

$setting = new UserSetting;
$setting->get('someKey', 'defaultValue');


use TaylorNetwork\Setting\AppSetting;

$setting = new AppSetting;
$setting->get('someKey', 'defaultValue');




UserSetting::set('someKey', 'someValue');

UserSetting::guard('api')->get('someKey', 'Default Value!');



AppSetting::set('someKey', 'someValue');


The user_setting and app_setting helper functions are aliases for the get method. The user_setting helper has an optional third parameter to pass a guard or guards.


// Returns the user's value or null

// Returns the app's value or null

// Returns the user's value or 'defaultValue'
user_setting('key', 'defaultValue');

// Returns the app's value or 'defaultValue'
app_setting('key', 'defaultValue');

// Returns the user's value or 'defaultValue' using the 'api' guard
user_setting('key', 'defaultValue', 'api');

// Will try and get a value from each guard in order
// If a value other than the default value is found it will immediately return it.
// If none is found after using all the guards in the array, the default value is returned.
user_setting('key', 'defaultValue', ['web', 'api']);

HasSettings Trait

The HasSettings trait adds a settings relation and the following methods to your model

setting($key, $default = null)

This is the same as the get method above BUT can be used for any user not just one that is logged in.

updateSetting($key, $value)

This will create or update a setting for the specified user.


If you need to change the default auth guard or user model, publish config.

$ php artisan vendor:publish --provider="TaylorNetwork\Setting\SettingServiceProvider" --tag=config

Alternate Configuration

You can modify the settings table to suit your needs, publish the migrations

$ php artisan vendor:publish --provider="TaylorNetwork\Setting\SettingServiceProvider" --tag=migrations

Be sure to update the config with appropriate related_column if you change it.


You can extend the UserSetting and AppSetting models if you need additional functionality.

namespace App;

use TaylorNetwork\Setting\UserSetting;

class Setting extends UserSetting
	// --

Be sure to update the config with the appropriate new user_setting_model or app_setting_model.


The MIT License (MIT). Please see License File for more information.