Private Team Libraries
Create and manage private tool libraries for your organization.
Business Feature
Private libraries are available on the Business/Enterprise plan. They enable teams to share proprietary tools internally without publishing to the public community.
What are Private Libraries?
Private libraries allow your organization to maintain an internal catalog of tools that are only accessible to team members. This is ideal for:
Proprietary Workflows
Share tools that implement company-specific processes without exposing them publicly
IP Protection
Keep algorithms and techniques confidential while enabling internal collaboration
Client Projects
Create project-specific tools that stay within your organization
Quality Control
Test and refine tools internally before deciding to publish publicly
Creating a Private Library
Initial Setup
- 1
Navigate to Team Settings → Libraries
- 2
Click "Create Private Library"
- 3
Name your library and optionally add a description
- 4
Choose access permissions (see Access Control below)
Publishing to Private Library
- 1
Select a tool from your workspace
- 2
Click "Share" → "Publish to Private Library"
- 3
Select the target private library from the dropdown
- 4
Add tags and documentation, then click "Publish"
Access Control
Fine-grained permissions control who can view, use, and manage tools in your private libraries.
Permission Levels
Team-Based Access
Grant access to entire teams or departments:
Discovering Private Tools
Team members can browse private libraries alongside the public community library.
- 1
Open the Library browser in PegBoard
- 2
Use the filter dropdown to switch between Public and your organization's private libraries
- 3
Private tools show a icon to distinguish them from public tools
- 4
Clone to your workspace just like public tools
Version Management
Private libraries support versioning to ensure teams stay synchronized.
Publishing Updates
When you update a tool that's published to a private library:
- • Previous versions are preserved automatically
- • Team members receive update notifications
- • Users can choose to update or stay on current version
- • Admins can deprecate old versions
Rollback Support
If an update causes issues, admins can rollback the library to a previous version, and all team members will be notified to revert their cloned copies.
Best Practices
- • Create separate libraries for different departments or project types
- • Use consistent tagging conventions across your organization
- • Document tools thoroughly - internal users benefit from context
- • Regularly review and archive unused tools to keep libraries clean
- • Consider graduating mature internal tools to public community