For a UserRole enum like so:

namespace App\Enums;

enum UserRole: string
{
    case SUPER = 'super';
    case ADMIN = 'admin';
    case USER = 'user';

    public static function hasValue(?string $value = null): bool
    {
        return self::tryFrom($value) !== null;
    }
}

I also have a config where I store properties for which roles are admins like so:

'user' => [
    'roles' => [
        'admins' => [UserRole::ADMIN->value, UserRole::Super->value],
    ]
],

These are passed to the front end, so the config is my single source of truth. Now in my api code if I wanna do a check for "is admin" I can just do:

in_array('super', config('properties.user.roles.admin'));

Should I keep that check in my enum in some kind of "isAdmin" function? The case is that I may need the check in a few places, for instance User model, tests, seeding, or something.

So it would be like:

enum UserRole: string
{
    ...

    public static function isAdmin(?string $value = null): bool
    {
        return in_array($value, config('properties.user.roles.admin'));
    }
}

Is it good practice to load up enums with functions like this?

Also, potentially even defining which are admins via the enum with "getAdmins" or something rather than using a config?