How to share an AI workflow with your teammates (Claude, ChatGPT, Lovable, Base44, v0)
You built something that works — a Claude skill or project, a custom GPT, a routine, or a small app in Lovable, Base44 or v0 — and now your teammates are asking for it. How you share it depends on one question: does it only need instructions, or does it need to act in other apps?
If it's just instructions: share it inside your AI tool
A prompt, a skill, a project or a custom GPT that only works with what people paste or upload into it is the easy case. Most AI assistants let you share these inside your company's team workspace, and each teammate then uses them with their own account. Check your plan's sharing options first — if that covers it, you're done.
If it acts in other apps: this is where sharing gets hard
The moment your workflow reads a CRM, sends from Gmail or Outlook, books meetings or updates records, sharing stops being about the instructions and starts being about access. That's usually true of:
- small apps built in Lovable, Base44 or v0 that connect to company systems;
- routines and automations that run on a schedule;
- anything that works because it has your login or an API key saved inside it.
The quick fixes all go wrong in the same way:
- Sharing your login or key means everyone acts as you — your customers, your mailbox — and nobody can tell who did what.
- Everyone making their own copy means ten versions drifting apart, each with a saved password inside.
- Asking IT to rebuild it can take months, and the result often isn't what made yours useful.
What good sharing looks like
- Each teammate signs in as themselves with their company account.
- Each connects their own apps once, so the tool only sees what they can already see.
- The tool holds no passwords or keys.
- Drafts first — new users can prepare, not send, until someone allows it.
- A record of every action, with the person's name and the tool's version.
- Your name stays on it as the builder.
How to do it without rewriting anything
This is what Cresec is for. It sits on top of what you already built — in Claude, ChatGPT, Lovable, Base44, v0 or anything else — and, with a small change rather than a rebuild, makes it available to everyone at your company, each person as themselves, in a way IT can approve. You keep building where you build today; Cresec handles sign-in, access, permissions and records.
Access to Cresec is by request for now. Request access and tell us what you built.