You built a custom GPT that drafts member-facing emails in your credit union's tone. Your loan ops team would save an hour a day using it. So why is it still sitting on your personal OpenAI account?
Sharing a custom GPT is easier than most executives expect. There are a few things worth getting right before you roll it out—but none of them require an IT project.
Personal GPTs vs. Team GPTs: What's the Difference?
When you build a custom GPT in ChatGPT, it lives on your personal account by default. Only you can see it, use it, and edit it. That works fine for personal productivity. It doesn't scale to a team.
A ChatGPT Team workspace (as of 2024—verify current pricing and plan details at openai.com) changes that. Inside a Team workspace, you can publish a custom GPT to everyone in the workspace. Your member services team, your loan ops team, your marketing coordinator—they all get access to the same GPT, with the same instructions, the same tone guidelines, and the same uploaded reference documents.
The distinction matters for three practical reasons:
- Personal GPTs are tied to one account. If that person leaves, the GPT goes with them.
- Team GPTs live in a shared workspace. The organization controls access, not the individual.
- Team workspaces don't use your conversations to train OpenAI's models by default—which matters if your team is discussing anything member-adjacent.
Consult your compliance team before uploading any member data or nonpublic personal information into any AI tool, even a private workspace.
How Do I Share a Custom GPT in a ChatGPT Team Workspace?
Once your Team workspace is set up, the publishing process takes about five minutes.
- Open your GPT editor. Go to chatgpt.com, click your profile icon in the top right, and select "My GPTs." Find the GPT you want to share and click the pencil icon to edit it.
- Go to the "Configure" tab. This is where your GPT's name, description, instructions, and uploaded files live. Make sure everything is finalized—your team will see whatever is here.
- Set the access level. Scroll to the publishing settings. You'll see options like "Only me," "Anyone with a link," or "Everyone in [your workspace name]." Select the workspace option.
- Save and publish. Click "Update" or "Save." The GPT is now visible to everyone in your Team workspace inside the GPT library.
- Point your team to it. Team members can find shared GPTs by clicking "Explore GPTs" or browsing the workspace library. Send a quick Slack message or email with a direct link when you first launch—don't assume people will find it on their own.
Publishing a GPT to your Team workspace takes about five minutes. The harder work is the five minutes before that: making sure the instructions are actually ready for someone else to use.
Who Can Edit a Team GPT?
This is where a lot of credit unions trip up. By default, the person who created the GPT is the only one who can edit its instructions. If your CTO built it and then went on vacation, no one else can update the system prompt while they're gone.
A few things to know here. Workspace owners and admins have broader access controls, but editing a specific GPT's instructions typically still requires the original creator's account—or for the creator to transfer ownership. This area of the product evolves quickly, so verify with OpenAI's current documentation before you assume.
The practical fix: designate at least two people at your credit union who have the technical access to edit each GPT you deploy. Treat it like a shared credential in your password vault. And keep a copy of every GPT's system prompt in a shared Google Doc or SharePoint folder. That document is your source of truth regardless of what happens inside the tool.
How to Version Your GPT Instructions
AI tools don't come with version history the way Google Docs does. If you edit your GPT's instructions and something breaks, there's no "undo" button that shows you what changed.
A simple versioning habit solves this. Keep a running document—a basic table works fine—with columns for version number, date changed, what changed, and who approved. Before you touch the live instructions, paste the current version into the doc and increment the version number.
For anything that touches member-facing language or regulatory topics, have your compliance officer review the new version before you publish.
Treat your GPT instructions like a policy document: date-stamped, stored outside the tool, and reviewed before any major update goes live.
This isn't bureaucracy for its own sake. If an examiner ever asks how you're controlling AI-generated content, a version log shows intentional governance—not a wild west rollout.
What Do Team Members Actually See?
When a team member opens the GPT library, they'll see the GPT's name, description, and the chat interface. They do not see your system prompt or uploaded files—those stay hidden behind the scenes.
What they can do:
- Start conversations and get responses shaped by your instructions
- Upload their own files within a conversation (if you've enabled that capability)
- Reference any knowledge documents you've built into the GPT's configuration
What they cannot do, unless they're the creator or an admin with edit rights:
- See or edit the system prompt
- Add or remove uploaded knowledge files
- Change the GPT's name or description
This means you can publish one GPT for drafting board memos, another for member complaint responses, and a third for comparing vendor proposals—and your team just picks the right tool for the job without needing to understand what's running underneath.
What This Looks Like in Practice
Say your marketing team needs to produce consistent member newsletter copy. You build a custom GPT with your brand voice guide uploaded, a system prompt that enforces tone and required compliance disclaimers, and a clear description of when to use it. You publish it to the Team workspace. Now anyone on the marketing team—even a new hire—can draft newsletter copy that sounds like your credit union.
The compliance officer reviews the GPT instructions quarterly. You keep a version log in SharePoint. If OpenAI updates something that changes the GPT's behavior, you have the original instructions ready to restore from.
That's a real, manageable AI workflow. No IT project required.
What's the Risk?
For most internal use cases—marketing copy, member FAQ drafts, internal training materials—the risk profile of a ChatGPT Team workspace is relatively low. Conversations aren't used to train OpenAI's models by default, which is a meaningful step. But "low" isn't "zero." You're still sending data to a third-party cloud service, and your data governance policy and vendor agreements should reflect that. If your credit union hasn't formally assessed OpenAI as a vendor, that step belongs on your compliance team's list before you roll this out broadly.
The bigger risk is operational, not regulatory. Without a designated backup editor and an external version log, one person's departure or one accidental edit can break a GPT your team has come to rely on. If you're using a GPT in any workflow that touches member-facing language, lending decisions, or complaint handling, apply the same change-control discipline you'd use for any policy document. For pure internal productivity work—drafting agendas, summarizing meeting notes, structuring board presentations—you can move faster. Just keep the version log.
This post was drafted with AI assistance and reviewed by a human at CU 2.0. AI makes mistakes; verify any specific claim before acting on it.
Frequently Asked Questions
Do I need a paid ChatGPT plan to share a custom GPT with my team?
Yes. Sharing GPTs within a team workspace requires a ChatGPT Team or Enterprise plan—the free and Plus tiers are individual accounts only. Verify current plan options and pricing at openai.com, as plans and features change.
Can team members see the system prompt inside a shared GPT?
No. Team members see the GPT's name, description, and chat interface, but the system prompt and uploaded files are not visible to them. Only the creator—and workspace admins, depending on settings—can view or edit the instructions.
What happens to a shared GPT if the person who built it leaves the credit union?
That depends on your workspace settings and whether ownership was transferred before they left. Designate a backup editor for every GPT you deploy, and keep a copy of each GPT's instructions in an external document so you're never locked out.
Is there a built-in version history for GPT instructions?
No. ChatGPT does not offer version history for custom GPT instructions. Keep a dated copy of your current instructions in an external document—such as a SharePoint file or Google Doc—before making any changes.
Can different departments at my credit union have access to different GPTs?
Within a single Team workspace, all members can see all published GPTs. ChatGPT Enterprise offers more granular access controls. If you need strict separation—for example, keeping a compliance-only GPT away from general staff—verify what your current plan supports or consult OpenAI's documentation on Enterprise options.
Want to Dig Deeper?
CU 2.0 works with credit union executive teams—at institutions of all sizes—to build practical AI workflows that actually stick. Whether your team is just getting started with ChatGPT or you're ready to build custom GPTs and automate entire back-office processes, we'll meet you where you are. We've helped credit union leaders go from "I've heard of this" to "we're running it in production." If that sounds useful, let's talk.
This post was drafted with AI assistance and reviewed by a human at CU 2.0. AI makes mistakes; verify any specific claim before acting on it.
