{"id":113,"date":"2026-10-13T10:45:00","date_gmt":"2026-10-13T10:45:00","guid":{"rendered":"https:\/\/np.themestate.com\/promptpress\/?p=113"},"modified":"2026-10-24T14:49:19","modified_gmt":"2026-10-24T14:49:19","slug":"private-team-public-prompts","status":"publish","type":"post","link":"https:\/\/demo.themnific.com\/promptpress\/private-team-public-prompts\/","title":{"rendered":"Private, Team or Public: Deciding Which Prompts to Publish"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Not every prompt belongs on the public web. Some are personal drafts, some contain client details, and <strong>a few are good enough to share with everyone<\/strong>. Every template in our public <a href=\"\/prompts\/\">prompt library<\/a> went through the same three-step path before being published.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This post covers how to decide <strong>which level a prompt belongs to<\/strong> and what to strip out before it goes public. It is a follow-up to our guide on <a href=\"\/sharing-prompts-across-a-team\/\">sharing prompts across a team<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Three levels of visibility<\/h2>\n\n\n\n<figure class=\"wp-block-table alignwide\"><table class=\"has-fixed-layout\"><thead><tr><th>Level<\/th><th>Who sees it<\/th><th>Typical content<\/th><\/tr><\/thead><tbody><tr><td>Private<\/td><td>Only the author<\/td><td>Drafts, experiments, personal shortcuts<\/td><\/tr><tr><td>Team<\/td><td>Everyone in the team<\/td><td>Client work, internal processes, project context<\/td><\/tr><tr><td>Public<\/td><td>Anyone visiting the site<\/td><td>Tested, general-purpose templates<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The default should always be <strong>private<\/strong>. Moving a prompt up a level is a deliberate decision, never an accident.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">When a prompt is ready for the team<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>It has been used successfully at least a few times.<\/li>\n\n\n\n<li>The title and variables make sense to someone who didn&#8217;t write it.<\/li>\n\n\n\n<li>It has an owner who will maintain it.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">When a prompt is ready to go public<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Public prompts need a higher bar. Before publishing, check for anything that shouldn&#8217;t leave the company:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Client names, internal product names and project codes.<\/li>\n\n\n\n<li>Real data in examples: emails, numbers, customer quotes.<\/li>\n\n\n\n<li>Internal URLs, file paths and API details.<\/li>\n\n\n\n<li>Persona or context text that only makes sense inside your team.<\/li>\n<\/ol>\n\n\n\n<pre class=\"wp-block-preformatted\">Before: Summarise the Q3 complaints from Hartwell Logistics\n        (account #4471) and suggest replies.\nAfter:  Summarise the {{period}} complaints from {{client_type}}\n        and suggest replies in {{tone}}.<\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Shared parts need checking too<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A public prompt that includes a team-only persona or project context can leak that text when someone copies the prompt. Check every included piece, or replace it with a public version.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\">Publishing a prompt is like publishing code: assume someone will read every line.<\/p>\n<cite>Security lead<\/cite><\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Publish less, but better<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A public library with twenty well-tested prompts is more useful than one with two hundred drafts. Mark tested prompts clearly, include a sample output and keep the rest in the team.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Some prompts are personal drafts, some belong to the team, and a few are good enough to publish. Here&#8217;s a simple way to decide, and what to remove before anything goes public.<\/p>\n","protected":false},"author":2,"featured_media":8163,"comment_status":"open","ping_status":"closed","sticky":false,"template":"template-fullwidth-narrow.php","format":"standard","meta":{"footnotes":""},"categories":[58],"tags":[],"class_list":["post-113","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-team-workflows"],"_links":{"self":[{"href":"https:\/\/demo.themnific.com\/promptpress\/wp-json\/wp\/v2\/posts\/113","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/demo.themnific.com\/promptpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/demo.themnific.com\/promptpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/demo.themnific.com\/promptpress\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/demo.themnific.com\/promptpress\/wp-json\/wp\/v2\/comments?post=113"}],"version-history":[{"count":1,"href":"https:\/\/demo.themnific.com\/promptpress\/wp-json\/wp\/v2\/posts\/113\/revisions"}],"predecessor-version":[{"id":8139,"href":"https:\/\/demo.themnific.com\/promptpress\/wp-json\/wp\/v2\/posts\/113\/revisions\/8139"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/demo.themnific.com\/promptpress\/wp-json\/wp\/v2\/media\/8163"}],"wp:attachment":[{"href":"https:\/\/demo.themnific.com\/promptpress\/wp-json\/wp\/v2\/media?parent=113"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/demo.themnific.com\/promptpress\/wp-json\/wp\/v2\/categories?post=113"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/demo.themnific.com\/promptpress\/wp-json\/wp\/v2\/tags?post=113"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}