Venny Knowledge Base
ONBOARD VENNY
Build the intelligence your programs run on.
Onboard Venny like a new colleague. Give it the company, supplier, worker, market, and ways-of-working context that defines how your program actually runs.
Company information
Policies, code of conduct, locations, org structure, operating rules, and internal documentation.
Supplier information
Supplier agreements, terms and conditions, rate cards, discounts, rebates, volume agreements, and service scope.
Worker information
Experience, skills, interests, ambitions, program history, assignments, and worker context.
Ways of working
Preferences, permissions, workflows, controls, escalation paths, regional exceptions, and operating habits.
Market intelligence
Country regulations, employment rules, rate-card benchmarks, market conditions, and regional requirements.
SOURCE-GROUNDED ANSWERS
Answers that show their source.
Venny retrieves the relevant company source, answers from that context, and keeps the evidence attached so users can check where the answer came from.
Ask Venny
ORGANIZATION KNOWLEDGE
Can this supplier submit clinicians in Germany under our current agreement?
VENNY
No. The supplier’s current agreement only covers UK clinical staffing. German clinician submissions require the DACH addendum before Venny can route candidates.
Supplier agreement — DACH clinical staffing
OPEN SOURCE ↗
SOURCE ARTICLE
ENABLED
Supplier agreement — DACH clinical staffing
SUPPLIER / CONTRACTS · UPDATED BY PROCUREMENT
RELEVANT PASSAGE
The supplier may provide clinical staffing services in the United Kingdom. Services in Germany, Austria, or Switzerland require execution of the DACH staffing addendum before candidate submission.
View exact source
↗
CONTROLLED COMPANY CONTEXT
Venny only uses what you allow.
Keep material scoped to the active organization, control who can manage it, and choose which sources Venny is allowed to retrieve, cite, and use when taking action.
01
Organization scoped
Policies, contracts, supplier material, and workflow notes stay isolated to the organization they belong to.
02
Permissioned management
Users can retrieve approved knowledge. Creating, editing, uploading, or deleting sources requires dedicated authority.
03
Retrieval control
Enable or disable a source without destroying its record, structure, or history.
KEEP THE LAYERS CLEAR
Three different sources of intelligence. One Venny.
KNOWLEDGE BASE
What your organization has documented
Company, supplier, worker, market, and ways-of-working material managed by your organization.
ORGANIZATION MANAGED
VENNY MEMORY
How Venny should work with you
Preferences, operating rules, and learned behaviors configured or learned per user and organization.
LEARNED OR CONFIGURED
HELP CENTER
How the venpor product works
Platform documentation, interface guidance, and product instructions managed by venpor.
VENPOR MANAGED
CONFIGURATION HEALTH
Configuration health shows when Venny is ready to work.
Like onboarding a colleague, you give Venny the information it needs before it begins. Configuration Health shows what is uploaded, verified, still open, or missing—so teams know when Venny has enough context to work.
Verified
Required program knowledge is present, structured, and confirmed by the right owner.
Open questions
Venny flags referenced suppliers, policies, contracts, or workflows that have not been provided yet.
Missing inputs
Venny shows which required policies, agreements, rules, or reference data still need to be provided.
Stale sources
Outdated documents and aging reference material can be surfaced before they create bad answers.
TRUST STARTS WITH COMPLETE CONTEXT
Don't put AI to work with missing information.
Configuration Health makes gaps visible before Venny relies on incomplete, outdated, or unverified context.
FAQ