Ownership rules
PromptsVault separates viewing from editing. Sharing a prompt or folder never lets someone else change it. Only the owner does.
The rule
You own a prompt if you created it. You own a folder if you created it. Ownership is checked on the server using your authenticated user ID, not anything stored in the browser.
This gives you four roles in practice:
| Source | You can view | You can copy | You can favorite | You can edit | You can delete |
|---|---|---|---|---|---|
| Prompts you created | yes | yes | yes | yes | yes |
| Team-shared prompts | yes | yes | yes | no | no |
| Prompts inside a shared folder | yes | yes | yes | no | no |
| Pack prompts you purchased | yes | yes | yes | no | no |
Why this matters
Prompts get refined over time. Letting any teammate rewrite a shared prompt would silently change it for everyone else. By keeping ownership tight, the original author always knows what's in the folder.
If you want a teammate to take over a prompt, the simplest path is:
- They favorite the prompt.
- They create their own copy by clicking Duplicate in the three-dot menu.
- They share their copy back with the team.
Pack folders
Premium pack folders enforce ownership at the database level: even the schema rejects edits that target a pack folder. See Pack folders for how those protections work.
Account-level enforcement
If someone tries to call an edit API directly, the database denies it with a permission error. The UI just hides the action so you do not see options you cannot use.