Skill permissions

Root Signals provides granular access control for skills through skill permissions. Skill permissions allow you to control who can view, edit, and execute skills within your organization.

Skill Visibility

Skills can have two visibility states - unlisted or listed.

  • Unlisted skills are only visible to the user who created the skill and to the administrators of the organization.

  • Listed skills are visible to everyone in the organization.

The visibility of a skill can be changed by clicking the three dots at the end of the skill row in the skills table view and selecting "Change status". Only the skill creator and administrators have the ability to change the visibility of a skill.

Skill Editing

By default, only the creator of a skill and the administrators of the organization can edit a skill. This includes changing the intent, prompt, validators, test data, and model of the skill.

If a user attempts to edit a skill they don't have permissions for, they will receive an access denied error message.

Skill Execution

All users within an organization can execute listed and unlisted skills.

In summary

Skill permissions in Root Signals allow you to control the visibility, editability and executability of skills at an organization level. Unlisted skills provide a way to keep skills private during development, while listed skills can be shared with the entire organization. Administrators have overriding access to manage all skills. This permission system provides the right balance of collaboration and control for skill management.

Last updated