Before you start
Three things, one person
You need a NOAN workspace with a General API key, a Slack workspace you can add apps to, and, if you use Granola, a workspace API key from your Granola admin. Pick one person to be the owner: they install, connect the key, and decide what is saved unless they hand a client to its lead. Everyone else just uses Slack.
Nothing is written to NOAN without a named person approving it. Verity proposes; people decide. That rule holds for facts from meetings, from conversation, and from anything anyone types.
How to think about channels
A channel is a place with a purpose
Each channel she is in gets three settings: what it is for, who decides facts there, and which stacks she may not see there. For a services team that gives you a simple shape: the team channel is her home and sees everything, each client channel is bound to that client and sees only its own stack plus what you share with all clients, and the lead on the account is the decider.
#delivery
- Sees
- Everything
- Decides
- You, the owner
Where the team asks her things and where the weekly digest lands. Set this one up first.
#client-ledgerline
- Sees
- Customer: Ledgerline, plus your shared stacks
- Decides
- The customer success lead
Bound to ledgerline.io. Their meetings arrive here as proposed facts, and what the team says here about them is harvested once a day.
#client-cardinal
- Sees
- Customer: Cardinal, plus your shared stacks
- Decides
- The lead on the account
Same shape, different customer. Ledgerline's stack is hidden here automatically, so nothing crosses between clients.
#ledgerline-shared
- Sees
- Customer: Ledgerline, plus your shared stacks
- Decides
- The lead on the account
Shared with the client's own people. Verity answers here in the open, so the client reads her answers, but only your own people can ask her anything. Their people are ignored, and she says so to whoever invites her.
#leadership
- Sees
- Whatever you leave visible
- Decides
- You
Client stacks are hidden here on their own; show one with /verity scope show if leadership should see it. Scope limits seeing, never contributing: a note about a client still reaches you privately.
In a Slack Connect channel shared with a client, she answers in the open but only for your own people; the client reads her answers and cannot trigger her. Scope limits what she reads and shows in a channel, never what the team can contribute. Someone mentioning a client in the wrong channel does not leak that client's facts, and what they said still reaches the owner privately.
Set up, in order
Six steps, a few minutes
- 01
Install her
Open the install link as the person who will own approvals and approve the permissions in Slack. The owner is whoever installs and connects; teammates never need keys of their own.
slack.getnoan.com/install - 02
Connect NOAN
In any channel, run the connect command and open the private link she replies with. Paste your NOAN General API key on that page. The key is stored encrypted and never shown in Slack; what each channel may see is decided per channel, never by the key.
/verity connect - 03
Set up the team channel
Invite Verity to the channel the team works in and mention her with nothing else. The setup form opens: choose The team, leave the decider empty, hide nothing. The first save makes it her home channel and switches everything on. No interviews start; those stay optional.
@Verity - 04
Create one channel per client, shared or not
Invite Verity and mention her. In the form choose A customer's channel, give the customer's name and their email domains, and pick the lead on the account as the decider. That is all: the client's stack is visible in this channel and in the team channel, and hidden in every other channel on its own.
/verity customerThe decider becomes the delegate for that customer's stack: they review and save its facts without you. You still see everything in your inbox. A Slack Connect channel shared with the client works the same way: on by default, her answers visible to the client, and only people from your workspace signed in with your company email can trigger her. /verity shared off keeps her out of one; /verity scope show Customer: Ledgerline lets another channel see a client on purpose.
- 05
Connect Granola
Ask your Granola admin for a workspace API key (Settings, Connectors, API keys; Business or Enterprise plan). Run the connect command and paste it on the page that opens. From then on every meeting with a client's domain is proposed as facts in that client's channel within fifteen minutes, and the people you met become contacts with the meeting memo.
/verity granola connectPrivate Granola notes are never seen by the API. Keep client meetings public in the workspace, or in a space granted API access.
- 06
Tell the team
Post the three lines below in the team channel. That is the whole onboarding for everyone else.
Verity is in our Slack. Mention her with a question and she answers from what we know. Start a message with fact: to add a fact about how we work. In client channels, say Looks right on her cards and the account owner saves them.
What to say to her
Plain words, in the channel
There is no syntax to learn beyond one word. Mention her to ask or to hand off work, and start a message with fact: to add a fact about the customer.
One practice per fact
Present tense, specific, one thing. "Ledgerline runs Postgres 15 in production" is a fact. "We should look at their database" is a plan, and she will leave it alone.
Let the harvest do the typing
In a client channel you do not have to write fact: at all. Durable statements are held and proposed once a day, or when five have gathered. Say things plainly in the channel and decide on the cards.
Say Looks right, do not rewrite
If a card is close, confirm it and the decider adjusts the wording on save. If it is wrong, Not quite and say what to change. See full wording shows the evidence she used.
Contradictions are a feature
When someone says something that conflicts with a saved fact, she replies once with Draft an update. That is how facts stay true. Anyone can switch checks off for their own messages.
The first week
What you will see happen
Within fifteen minutes of a client call, one message appears in that client's channel: the meeting, and a card per fact in its thread, each quoting the summary it rests on. The people on the call are in your NOAN network with the meeting attached. A call that matches no client comes to the owner as a question with a button per client; nothing lands in a channel by guess.
Once a day, the durable things the team said in each client channel arrive the same way. The lead on the account says Looks right or Not quite, and saved facts land in that client's stack. The owner has one direct message that lists every fact still waiting, updated in place, plus a weekly nudge for anything nobody has looked at in ninety days.
When someone in a channel says something that contradicts a saved fact, she replies once with Draft an update. When the owner wants a quiet day, /verity pause stops every write until resumed; she still answers.
Everything above, with the exact command for each, is in her reference at slack.getnoan.com/how .
Put Verity in your Slack
Install as the owner, connect your NOAN key once, set up the team channel and a channel per client. The rest is your team talking.