Skip to main content

Creating Custom Protocols

A Protocol is a workspace-scoped Skill that admins create to extend Companion for everyone in the organization. Protocols are managed under Settings -> Protocols and are meant for repeatable workflows where the whole team should use the same instructions, tools, and context.

What a Protocol contains​

A Protocol starts with a name and a prompt. The name should make it clear when the Protocol should be used, while the prompt tells Companion how to behave when the Protocol is active. A strong prompt usually explains the task, the expected output, and any rules Companion should follow.

Protocols can also include tools and entity contexts. Tools give Companion specific capabilities while the Protocol is active, such as searching conversations, listing meetings, creating contacts, creating a Linear issue, or sending an email through Gmail. Entity contexts give Companion access to relevant workspace data, such as a specific project, account, or contact, so it can respond with the right background information.

When a workspace member activates a Protocol in Companion, Companion follows the Protocol's instructions and can use the tools or contexts configured by the admin.

A Protocol is the workspace-level form of a Skill. Personal Skills are visible only to their creator and are managed in Companion -> Skills, not under Settings -> Protocols.

Permissions​

Working with Protocols requires the relevant skills:*:all permission. Viewing Protocols requires skills:read:all, creating a Protocol requires skills:create:all, editing requires skills:update:all, and deleting requires skills:delete:all.

By default, these are admin-level permissions. If you cannot view or manage Protocols, ask a workspace admin to review your role. See Roles and Permissions for the full permission model.

Create a new Protocol​

To create a new Protocol, go to Settings -> Protocols and click New protocol. Add a clear name, then write the prompt that should guide Companion when someone uses the Protocol.

After the prompt is in place, configure any optional tools or entity contexts the Protocol needs. Use tools when Companion must take an action or retrieve information from a connected system. Use entity contexts when the Protocol should reason with specific workspace data.

When you save the Protocol, it becomes available to every workspace member in Companion. Members do not need to install it individually.

"Triggers" are planned automatic activation rules, such as running a Protocol when a specific condition is met. They are not configurable in the Protocols UI today. To activate a Protocol, a workspace member opens it from Companion.

Edit or delete a Protocol​

To edit a Protocol, go to Settings -> Protocols, find the Protocol, and click Edit. You can update the name, prompt, tools, or entity contexts. Changes take effect immediately for all workspace members.

To delete a Protocol, find it on the same page, click Delete, and confirm the action. Deletion removes the Protocol for everyone in the workspace, but it does not erase past Companion thread history.

Protocols vs personal Skills​

Protocols and personal Skills both give Companion reusable instructions, but they serve different scopes. A Protocol belongs to the workspace, is created by admins or users with skills:create:all, and is available to all workspace members. It is best for shared operating procedures that should be consistent across a team.

A personal Skill belongs to the person who created it, is managed in Companion -> Skills, and is visible only to that person. It is best for individual workflows, personal preferences, or repeated tasks that do not need to become a workspace standard.

For a broader explanation of Skills, see Skills overview. To understand how Skills and Agents appear in the Marketplace, see Marketplace overview. For permission details, see Roles and Permissions.