Is this a problem with wildcards?

[jskorlol]

        Permission::create(['name' => 'admin']);
        Permission::create(['name' => 'admin.account.view']);
        Permission::create(['name' => 'admin.account.edit']);

I created the permission like this.

When you turn on the wildcard option

The first user with "admin" permission
All privileges of admin.* are assigned.

is this a bug?

Even though it's "admin"'s permission, not "admin.*" permission,
Taking all the rest... I think there is a difficulty in branching authority.

[PaolaRuby]

You have to give all the information, the authors cannot guess or use psychic powers to know which package version you use, php version, etc, it's the only way someone can give you an answer

[erikn69]

Try to use 'admin.index' instead of just 'admin'

It seems like an expected behavior, look at this test:

laravel-permission/tests/WildcardHasPermissionsTest.php

Lines 43 to 47 in 2512d5a

	$permission3 = Permission::create(['name' => 'posts']);
	$this->testUserRole->givePermissionTo([$permission1, $permission2, $permission3]);
	$this->assertTrue($user1->hasPermissionTo('posts.create'));

Just with 'post' has permission to 'post.create'

[jbmaciel]

I believe this is not a bug, it is in the documentation.