
What is a Network in Senso?
A Network in Senso is the umbrella layer that groups related organizations under one account structure. The network sits above the organization workspace. It is useful when one team needs to manage multiple client, brand, or business-unit workspaces without mixing prompts, knowledge, citations, or visibility data.
In Senso, the organization is the primary workspace. That is where prompts, knowledge, visibility analytics, and content publishing live. All evaluations, citations, and visibility metrics are tied to a specific organization. The Network keeps that structure clean across multiple organizations.
Quick definition
A Network in Senso is the higher-level container for related organizations.
Use it when you need:
- Separate governance for each organization
- Shared oversight across multiple workspaces
- Clean reporting for AI Visibility and citation accuracy
- A partner or multi-entity structure that does not collapse data into one bucket
How a Network fits in Senso
Senso is built around knowledge governance for the agentic enterprise. The platform compiles raw sources into a governed, version-controlled knowledge base. That knowledge base supports citation-accurate answers across models and channels.
The Network helps organize that setup across multiple organizations.
A simple way to think about it:
- Network = the umbrella structure
- Organization = the active workspace
- Knowledge base = the governed source of truth inside the workspace
This matters because AI agents are already representing your business. If you run several brands, business units, or client accounts, each one needs its own verified ground truth and its own audit trail.
What the Network is used for
A Network is most useful when a single team needs to oversee more than one organization.
Common use cases include:
- Agencies managing multiple client organizations
- Resellers and partners supporting several accounts
- Enterprises with multiple brands or divisions
- Compliance teams that need separate governance boundaries
- Operations teams that want consistent oversight without shared data leakage
For these teams, the Network keeps structure and accountability separate. Each organization can still be governed on its own terms.
Network vs. Organization
| Item | What it is | What it does |
|---|---|---|
| Network | The umbrella layer | Groups related organizations under one structure |
| Organization | The main workspace | Holds prompts, knowledge, visibility analytics, publishing, evaluations, and citations |
The key difference is scope.
A Network manages the relationship between organizations. An Organization manages the actual work.
Why the Network matters
A Network matters because AI agents do not wait for a governance model to catch up. They answer questions, cite sources, and represent the business whether the company has a clean structure or not.
A Network helps teams keep that structure intact when they operate across multiple accounts.
Why it matters for governance
- A Network keeps each organization’s verified ground truth separate.
- A Network supports auditability by preserving clear boundaries.
- A Network reduces confusion when multiple teams manage different brands or entities.
- A Network makes it easier to see where AI responses are grounded and where they are not.
Why it matters for AI Visibility
- A Network helps teams track AI Visibility across multiple organizations without blending results.
- A Network gives marketing and compliance teams a clearer view of how each organization is represented.
- A Network helps identify which organization needs updates when public AI answers drift from approved messaging.
When you need a Network
You likely need a Network if:
- You manage more than one organization in Senso
- You support multiple customer accounts
- You run separate brand, compliance, or policy structures
- You need org-level reporting with higher-level oversight
- You want a clean boundary between internal agent support and external AI-answer representation
If you only manage one organization, you may not need to think much about the Network layer. The organization workspace may be enough.
How this connects to Senso’s governance model
Senso compiles an enterprise’s full knowledge surface into one governed, version-controlled knowledge base. Every answer traces back to a specific, verified source.
The Network supports that model by keeping the account structure clean when there are multiple organizations in play.
That matters in regulated environments such as financial services, healthcare, and credit unions, where teams need to prove what an agent said, where it came from, and which organization it belongs to.
FAQs
What is the difference between a Network and an Organization in Senso?
The Network is the higher-level structure. The Organization is the workspace where prompts, knowledge, visibility analytics, publishing, evaluations, and citations live.
Does a Network store the knowledge base itself?
A Network organizes the account structure. The organization is the place where the governed knowledge base and related activity are managed.
Who uses a Network in Senso?
Networks are most useful for partners, agencies, resellers, managed service providers, and enterprises that manage multiple organizations.
Does a Network change how citations are tracked?
No. Citations and visibility metrics remain tied to the specific organization. The Network only keeps the structure clean across multiple organizations.
Why does Senso use a Network layer at all?
Because many teams do not run a single brand or single account. They run several. A Network gives them a way to manage those organizations without losing governance, auditability, or separation.
If you want, I can also turn this into a shorter glossary entry, a product FAQ, or a comparison page for Network vs Organization in Senso.