Sharing and Collaboration
Share AI prompts and collaborate with teams in PromptOwl using role-based permissions, team sharing, and JSON import/export.
This guide explains how to share prompts, artifacts, and conversations with team members and collaborate effectively in PromptOwl.
Table of Contents
Collaboration Overview
PromptOwl enables collaboration through multiple sharing mechanisms:
Sharing Methods
Method
Description
Best For
Share with specific individuals
What Can Be Shared
Item
Email Share
Team Share
Export
Sharing Prompts
Share prompts with colleagues so they can use or collaborate on them.
How to Share a Prompt
Open the prompt you want to share
Click the Share button (or share icon)
Choose sharing method:
Enter email addresses, OR
Screenshot: Share Prompt Dialog Adding Recipients:
Type email address in the input field
Press Enter or Space to add
Add multiple emails as needed
Removing Recipients:
Click the X on any email badge to remove
Sharing Indicators
Number of people with access
Someone else shared this with you
Email Notifications
When you share a prompt:
Recipient gets an email notification
Email includes prompt name and your email
Contains direct link to the prompt
Styled with your organization's branding
Sharing Artifacts and Folders
Share knowledge base content with your team.
Sharing an Artifact
Open the artifact in Data Room
Add email addresses or select teams
Sharing a Folder
Share an entire folder to give access to all artifacts within:
Open the folder in Data Room
Click Share on the folder
All artifacts in folder become accessible
Shared Item
What's Accessible
Parent folder access doesn't grant child access
Share Notifications
Recipients receive email notifications with:
Item name (folder or artifact)
Sharing Conversations
Share valuable AI conversations with colleagues.
How to Share a Conversation
Find the conversation in the sidebar
Click the menu icon (or right-click)
Add email addresses or teams
Screenshot: Share Conversation Prompt Access Required
Important: Recipients need access to the underlying prompt to view shared conversations.
Automatic Handling:
System checks if recipient has prompt access
If not, shows confirmation dialog
You can choose to share both conversation AND prompt
Viewing Shared Conversations
Shared conversations appear in your sidebar:
Shows "Shared by: [email]" indicator
Full read access to conversation history
Cannot modify the original conversation
Team-Based Sharing
Teams provide group-based access management.
What Are Teams?
Teams are groups of users who share access to resources:
Share once, all team members get access
New team members automatically get access
Centralized permission management
Creating a Team
Assign roles (Owner, Editor, Viewer)
Team Member Roles
Full control, can manage team
Adding Team Members
New members receive email notification with:
List of accessible prompts
Sharing with Teams
When sharing any item:
Check the teams to share with
All current and future team members get access.
Enterprise Teams
In enterprise environments:
Teams can be auto-created
Users auto-added based on organization
Admin controls team membership
Cross-team sharing may be restricted
Permission Levels
Different roles have different capabilities.
Role Comparison
Capability
Owner
Editor
Viewer
User
How Roles Are Assigned
For Prompts:
Creator is automatically Owner
Shared recipients get role based on sharing settings
For Teams:
Other members assigned roles when added
Can be changed by team Owner
Permission Inheritance
Scenario
Resulting Permission
Import and Export
Transfer prompts between accounts or environments.
Exporting Prompts
Export all your prompts to a JSON file:
Go to Settings or prompt list
JSON file downloads automatically
What's Exported:
What's NOT Exported:
Screenshot: Export Button Importing Prompts
Import prompts from a JSON file:
Go to Settings or prompt list
Prompts are created in your account
Import Notes:
Creates new prompts (doesn't overwrite)
Uses your default LLM settings if missing
No sharing settings imported
Share with external party
Collaboration Workflows
Common patterns for team collaboration.
Workflow 1: Prompt Development
Solo Development → Team Review → Production:
Developer creates prompt (Owner)
Shares with reviewers (Viewer)
Reviewers provide feedback
Workflow 2: Shared Knowledge Base
Centralized Knowledge:
Create team for department
Create folder in Data Room
Team members add artifacts
All prompts can use shared knowledge
Workflow 3: Template Distribution
Standard Prompts:
Admin creates standard prompts
Distributes to team members
Members import and customize
Original remains unchanged
Workflow 4: Conversation Review
Quality Assurance:
Shares interesting/problematic conversation
Team reviews conversation
Feedback incorporated into prompt
Prompt improved for everyone
Enterprise Sharing Controls
Administrators can control sharing behavior.
Feature Toggles
Enable/disable all sharing
Branded sharing notifications
Disabling Sharing
When sharing is disabled:
Attempts show: "Sharing is disabled for this organization"
Existing shares remain active
Enterprise Team Controls
New users join enterprise team automatically
Users must be in organization team
Limit sharing between teams
Custom Email Templates
Enterprises can customize sharing emails:
Variable support ({inviter_email}, {prompt_name})
Sharing Strategy
Do:
Use teams for group access
Share folders, not individual artifacts
Set appropriate permission levels
Review shared items periodically
Don't:
Share everything with everyone
Give Editor access when Viewer suffices
Share sensitive prompts widely
Forget to remove departed users
Team Organization
Suggested Structure:
Tips:
Permission Guidelines
Anyone who needs to use prompt
Collaborators on prompt development
Knowledge Base Sharing
Organize first - Create logical folder structure
Share folders - Not individual artifacts
Set permissions - Viewers for most, Editors for contributors
Review access - Periodic audit of who has access
Troubleshooting
Shared Item Not Visible
Check email address - Ensure correct email was used
Refresh page - May need to reload
Check team membership - If team-shared
Verify sharing saved - Sharer should confirm
Check permissions - May have view-only access
Can't Share Item
Check your role - Only Owners/Editors can share
Check enterprise settings - Sharing may be disabled
Verify you own the item - Or have Editor access
Check error message - May indicate specific issue
Team Members Not Getting Access
Check team membership - Ensure they're in the team
Check team role - May need higher permission
Verify sharing saved - Re-share if needed
Check email delivery - Notification may be in spam
Import/Export Issues
Export Problems:
Check browser download settings
Ensure you have prompts to export
Import Problems:
Verify JSON format is valid
Check file isn't corrupted
Ensure file contains prompt array
Email Notifications Not Received
Check spam folder - Often filtered
Verify email address - Must be exact match
Check enterprise email settings - May be blocked
Contact administrator - Email system may have issues
Permission Conflicts
If user has multiple access paths (direct + team):
Highest permission level applies
Direct shares can't reduce team permissions
Owner status always takes precedence
Quick Reference
Sharing Checklist
Before Sharing:
After Sharing:
Number of individual shares