Skills

Tenant membership supplies the Skill operation permissions. A creator owns their Skill. Only its owner can edit, delete or change sharing; other members can read it once it is shared with the tenant.

These permissions are not selectable in a custom role because the resource relationship, not an extra tenant-wide role grant, decides access. Tenant administration does not create blanket ownership of Skills.

Permissions

This family contains 5 permissions. “Baseline member” means every current tenant member already has the operation permission, including members with any system role. It does not bypass the resource checks described above. “Custom role” means the identifier can be selected when defining a custom role.

skill.create

Create a Skill; the caller becomes its owner.

Property	Value
Scope	Selected tenant
Granted by	Baseline member
Custom role	No. Baseline tenant membership; creating a Skill establishes ownership.

skill.delete

Delete a Skill owned by the caller.

Property	Value
Scope	Selected tenant
Granted by	Baseline member
Custom role	No. Baseline tenant membership; resource access still requires a Skill relationship.

skill.read

Read a Skill the caller owns or that has been shared with the tenant.

Property	Value
Scope	Selected tenant
Granted by	Baseline member
Custom role	No. Baseline tenant membership; resource access still requires a Skill relationship.

skill.share

Share or unshare an owned Skill with the tenant.

Property	Value
Scope	Selected tenant
Granted by	Baseline member
Custom role	No. Baseline tenant membership; resource access still requires a Skill relationship.

skill.update

Edit a Skill owned by the caller.

Property	Value
Scope	Selected tenant
Granted by	Baseline member
Custom role	No. Baseline tenant membership; resource access still requires a Skill relationship.