Four steps. Name the client, add its sources, set the team, then create it. Nothing reaches the client until a lead approves.
Client details
The name and slug set the vault folder. The slug cannot change after creation
The name people see across the OS
Used as the vault folder slug: client-name
Signs off the canon
First day of the engagement
Renewal review 60 days out
Where it lives
Created in the Oracle vault when you create the client
Sources
Every note in the knowledge base traces to a source. Add at least one
New files here become sources
Pages become sources after the crawl
Drop a file, connect the drive folder, crawl the site or paste links. Every note in the knowledge base traces back to one.
Files stay on the client drive. The Oracle keeps a pointer and a checksum, and registers each source when the client is created.
What the client gets
What appears on the client hub once the client is created
Team and access
Members work in the client's knowledge base. Guests read approved notes only
No guests yet. Guests see approved notes and shared artifacts for this client only.
Super admins always have access: Maya Okafor, Elias Brandt and Rhea Kapoor.
Who can open this client
Everyone listed, plus every super admin
Review and create
Check the details. The client is created when you confirm
Vault folder
Created in the vault when you create the client. Nothing is shared with the client yet
Client created
Paste links
One link per line. Each link becomes a registered source with its own review state. Public pages are read, private docs need the drive connector.
Brand guides, pricing pages, competitor pages, investor decks