Onboarding
What the onboarding plan does, who runs it, and how long it takes.
Onboarding is the product: in about 15 minutes your AI turns the places your team already keeps its information into a task board and a set of company rules, with nothing for you to type up.
Who does what
Gorila conducts and your AI works. Gorila hands the AI a plan with steps; the AI reads your sources (Notion, Drive, Slack, your website, whatever it is connected to) with its own connections, distills what it finds, and submits only short structured text. Gorila never receives your files and calls no model to read them. Everything the AI finds is saved as a proposal a person approves, or as a draft on the person's own board.
Start it by telling your AI: Set up Gorila for my organization (or /mcp__gorila__gorila-setup in Claude Code).
The video guide
A new account starts with a short video: press Set up Gorila and it opens in a small window that floats on top of your other windows, with sound, also while you are in your AI. It introduces the setup (about 10 minutes, most of it in the AI you already use), then tells you what to do at each step and why. Each step is said once, and you can replay it.
It moves on by itself: it follows what Gorila already knows (the organization exists, your AI is connected, how far the setup has got), so no AI runs it and Gorila records nothing about it. It is a recorded video with a recorded voice. It is available in Chrome, Edge and Safari; in other browsers, or if you choose to continue without it, the page has the same steps.
The welcome page moves on by itself too: once you create the organization, connect your AI or finish the setup, it opens the next step and tells you what just got done. When the setup is complete it opens your board.
The organization plan
Run once by an owner or admin:
- Sources. Which connectors the AI can use, and the company's website.
- Company. What you do and for whom, mission and values, who owns what, glossary, goals, products and the main projects.
- Brand and tone. Voice in a few adjectives, do and don't, vocabulary, formality, emojis.
- Copy, product, marketing and sales, support, operations, decisions. The rules and facts found in your documents, in the right category.
- Your tasks. The one stop with you: bring your own open tasks, or start with a blank board. Only your own, never a teammate's. Nothing about you yet: your profile and how you work are your personal onboarding, right after this one.
- Daily run. Optionally, a scheduled run of your AI that prepares your day.
- Always on. The instruction block for your AI client, so it keeps using Gorila in every chat.
- Review. Closes the run and tells you what is now in Gorila, what to double-check and the one next step, such as inviting your team.
The AI does not ask questions step by step: it reads first and asks once, at the end, only what no source answered.
Personal onboarding
Every member runs their own short plan, built to take a few minutes: their AI finds out what it can on its own and asks only what nothing told it.
It starts with About you. If the AI can read the member's past chats, it asks once for permission. Then it drafts everything from what it already knows (its memory of them, those chats, its connectors, and what Gorila has: their areas, the tasks assigned to them), and shows it in one message:
- Their profile: a title and a few concrete lines on what they handle, meaning what they own by name, which tasks and approvals go to them, and what isn't theirs. It also keeps a one-line version, which is what teammates' AIs see when they create a task. This is the one part their team sees: it is what every teammate's AI reads to decide who a piece of work goes to.
- Their private rules: what they keep repeating or correcting, written as short rules ("Always write to me in Spanish").
- The tools they use and the work they do every week.
They answer with a yes or a correction. When the AI doesn't know what their job is, it asks that one thing instead of guessing from their areas or tasks.
Then come their own tasks (bring them, or start with a blank board), the scheduled daily run and the instruction block for their AI. When Gorila already has the daily run or the block in place, those steps show as done from the start and the AI asks nothing about them.
Whenever the AI asks something, it suggests the answers: two to four options with its best guess first, plus one to write your own.
Everything but the profile is private to the member. Sharing a rule with the team is a later, separate proposal that an admin approves.
Whoever runs the organization onboarding does their personal one afterwards: the board offers it as soon as the company's is done. Anyone can change theirs later by telling their AI ("I also handle support now"), and members who onboarded before profiles existed are offered it once.
Time and quality
The target is 15 minutes or less for a typical startup, whatever connectors it has, and every step is timed. Re-running onboarding does not duplicate what is already there. Work the AI is unsure about is marked to double-check, and a correction is one sentence away.
The tools behind the plan are in the onboarding reference.