Skip to main content

Company knowledge

Company knowledge is the shared, curated guidance that the Orbis Assistant injects into every session for your organization. It captures the things that should be true for everyone building flows — preferred components, naming and design conventions, domain rules, how credentials should be handled, and known gotchas — so the assistant gives consistent, company-aware help instead of generic answers.

A tenant admin curates this knowledge from the Company Knowledge page in Settings.

info

The page is restricted to tenant admins, and the tenant is derived on the server from your RBAC context. Every entry is secret-scanned on save, so credentials never reach shared memory and nothing leaks across tenants.

Add a knowledge entry​

  1. In the Orbis Studio header, click your profile icon and select Settings.
  2. Click Company Knowledge.
  3. Click Add, then choose a kind for the entry — for example, a preferred component, a convention, a domain rule, or credential-handling guidance.
  4. Write the guidance and save.

The entry becomes active immediately and is included in future assistant sessions for your company. You can edit or delete any entry later from the same page.

Review suggested knowledge (candidates)​

Orbis Studio can learn from how your team actually works. Reflection scans recent, settled sessions and distills recurring patterns into candidate entries.

Candidates are inert — they do nothing until an admin approves them. This keeps the shared knowledge base intentional rather than accumulating noise automatically.

  1. On the Company Knowledge page, open the review queue to see pending candidates.
  2. For each candidate, click Approve to promote it (it is then shared with your company) or reject it.
  3. Use Reject all to clear the queue at once.

To generate fresh candidates, trigger a reflection scan. If there is nothing new to learn, the page reports No new knowledge found in recent sessions. You can also baseline the current state so that only sessions going forward are considered, and ignore past sessions when you do not want historical activity to produce candidates.