Role and Permission data are cached to speed up performance.
While we recommend not changing the cache “key” name, if you wish to alter the expiration time you may do so in the
config/permission.php file, in the
cache array. Note that as of v2.26.0 the
cache entry here is now an array, and
expiration_time is a sub-array entry.
When you use the built-in functions for manipulating roles and permissions, the cache is automatically reset for you, and relations are automatically reloaded for the current model record:
$user->assignRole('writer'); $user->removeRole('writer'); $user->syncRoles(params); $role->givePermissionTo('edit articles'); $role->revokePermissionTo('edit articles'); $role->syncPermissions(params); $permission->assignRole('writer'); $permission->removeRole('writer'); $permission->syncRoles(params);
HOWEVER, if you manipulate permission/role data directly in the database instead of calling the supplied methods, then you will not see the changes reflected in the application unless you manually reset the cache.
To manually reset the cache for this package, you can run the following in your app code:
Or you can use an Artisan command:
php artisan permission:cache-reset
TIP: If you are leveraging a caching service such as
memcached and there are other sites
running on your server, you could run into cache clashes between apps. It is prudent to set your own
prefix in Laravel’s
/config/cache.php to something unique for each application.
This will prevent other applications from accidentally using/changing your cached data.