Team Skills let you build a workflow once and share it with your whole team. Every Member in the workspace gets a consistent way of working. Team Skills is coming soon: it isn't part of the initial release of the new Plaud Intelligence and arrives in a follow-up update.
What are Team Skills?
A Skill is a saved workflow, such as a summary format, a report structure, or a set of steps Plaud Agent can run against your conversation data. In Plaud Team, a Member can keep a Skill private, or share it with the Team Community so every Member in the workspace can use it.
Custom summary templates and the template community carry over to the new version and keep working. Once Team Skills is available, your team's standard formats and workflows can also live as Skills.
Before you start
- Team Skills are available on the Plaud Mobile App and Plaud Web, for Plaud Team workspaces.
- Every Skill starts as a Member's private draft. Sharing it with the team is a deliberate choice, not automatic.
- The Team Community and the Public Community are separate stores. A Skill shared to your Team Community stays inside your workspace; sharing it out to the Public Community isn't supported. A Skill from the Public Community can be installed into your Team workspace.
- An Admin can't open a Member's private Skills. Admin oversight covers Team Spaces and Skills the Admin has published to the Team Community, not a Member's private drafts.
How to share a Skill with your team
- Under Tools, open the Skill you want to share. Skills you created show your name after by on the detail page.
- Click Publish at the top of the Skill detail page.
- In the Publish to team dialog, choose a Category and click Submit for review. Publishing makes a separate copy for the team, so your private draft is unaffected by later edits to the shared copy.
- Members in your Team workspace can now find the Skill on Plaud Web under Tools → Skills → Team, and choose to install it. Skills shared by you or your teammates all appear in this tab.
Any Member, not just Admins, can publish a Skill to the team this way. No Admin approval is needed. To take a Skill you published off the team, open its ⋯ menu and choose Unpublish.
How Admins auto-assign a Skill to the workspace
- Open the published team Skill you want every Member to have.
- In the Skill's ⋯ menu, turn on Auto-assign to workspace, then click Turn on in the confirmation prompt.
- The Skill becomes mandatory for your team. It installs automatically for every current Member and Admin, and for anyone who joins later, and its detail page shows the notice "This skill will be automatically added to all current and future team members' workspaces." Members don't need to install it themselves.
- Turning Auto-assign to workspace off again makes the Skill an optional team Skill. Copies Members already installed aren't removed, and they can keep using them.
There's no limit on how many Skills an Admin can auto-assign.
An auto-assigned Skill works differently from a Personal Official Skill. An Official Skill comes from Plaud and can't be removed. An auto-assigned Skill is installed by your Admin, but a Member can still uninstall it.
Updates and versions
- Editing your own Skill updates your private copy only. To update the version other Members installed, share it again.
- When you share an update, installed copies keep their current version until each Member chooses to update, unless an Admin turned on auto-update for the workspace.
- A Skill installed from the team, including auto-assigned Skills, can update silently if your Admin has turned on auto-update for the workspace.
Deleting a shared Skill
- To delete a Skill you created, open its ⋯ menu and choose Delete. A confirmation prompt appears: the Skill and its source files are permanently deleted from your workspace, and Also unpublish it from the community is selected by default, so the team copy is taken down together.
- Even when you unpublish the team copy, Members who have already added the Skill can continue to use their installed copies.
- You can untick Also unpublish it from the community to keep the team copy when you delete your private Skill. That copy becomes an orphaned copy: you can still take it down later, but you no longer have your original edit path to update it. We recommend deleting both together rather than leaving an orphaned copy behind.
- There's no version history or trash for Skills. The deletion cannot be undone, and if no other copy of the Skill exists, it can't be recovered.
- An Admin can't take down a Skill that another Member published. Members can only remove content they created and published themselves.
Turning off Skill access for your workspace
Skill access is a workspace-wide switch that only an Admin can control. On Plaud Web, go to Settings → Workspace management → Security, and find the Skill access toggle under Sharing permissions. When the toggle is on, Members can create, add, and use Skills in the workspace.
- When an Admin turns Skill access off, no one in the workspace, including Admins, can create or use any Skill. This covers Official Skills, Skills your team has already built, and Skill suites.
- The Skills tabs under Tools and individual Skill pages become unavailable while Skill access is off.
- Turning Skill access off doesn't delete anything. Existing Skills, upload history, and shared team Skills are preserved.
- Turning Skill access back on immediately restores everything as it was.
This is meant for workspaces concerned about a Skill accessing files or data it shouldn't. Today Skill access is an all-or-nothing switch; more granular controls, such as allowing use but not creation, may come later.
FAQ about Team Skills
Can I move a Skill from my Team workspace to the Public Community?
No. Content shared to your Team Community stays inside your workspace and can't be published out to the Public Community.
Can an Admin see or edit my private Skills?
No. An Admin's oversight covers Team Spaces and Skills published to the Team Community, not a Member's private Skills.
What happened to custom summary templates and multi-dimensional summaries?
They keep working. Custom summary templates and the template community carry over to the new version. Once Team Skills is available, you can also build the same formats as Skills and share them with your team.
Do templates work the same way as Skills?
Templates follow the same sharing model: private by default, shared to the Team Community by choice, and never published from the Team Community out to the Public Community.
Can an Admin remove a Skill another Member published?
No. An Admin can auto-assign a Member's published Skill to the workspace, but only the Member who published it can take it down.
Does Plaud review what my team publishes to the Team Community?
Plaud runs automated safety checks on everything in the Team Community, but content there belongs to your team, so it isn't reviewed by a person the way Public Community submissions are.
Disclaimer: The information in this article is for reference only and may change as Plaud product features continue to update. Please refer to the latest version of the product for the most current experience.