Sophea Nous Platform - Admin Guide
Welcome
This guide explains how workspace admins and IT staff operate Sophea Nous as it behaves today. It focuses on the real setup path for connectors, document sets, search configuration, and chat-side verification.
0.1 Who This Guide Is For
- Workspace administrators responsible for content onboarding and search validation
- IT staff operating Sophea Nous for internal company use
- Platform owners maintaining search quality, AI configuration, and connector health
0.2 How Nous Works Today
The most important workflow concepts for admins:
- Connectors index content into the workspace search index.
- File connectors do not automatically create starter document sets. Admins create document sets explicitly on the Document Sets page to group indexed sources.
- Searchable connector content is available through All sources or its connector source. Admins create document sets when users or workspace-created agents need a reusable curated scope.
- Projects group chats with shared instructions and files, giving teams a persistent context space separate from one-off sessions.
Admins may also enable published Sophea agents for a workspace from the Portal. Those published agents are different from the workspace-created agents that admins build inside Nous.
A connector and its document set are related, but they are not the same thing. A connector brings content into Nous. A document set is an optional saved scope for search and workspace-created agents.
0.3 Platform Architecture
Sophea Nous is one service in a multi-service platform. The key services relevant to workspace admins are:
- Portal: Organizations, workspace creation, authentication, people and Team access, plans and billing, Digital Employee control, LLM routing, and managed connector credentials.
- Nous: the AI search and chat interface, connector management, document processing, agents, and actions.
- RAG service: the retrieval pipeline that powers search and agent knowledge lookups. Managed by Sophea; no direct admin configuration required.
- Agent Service: hosts published Sophea agents (Deep Research and others). Enabled per workspace from the Portal.
Language model configuration (which models are available, rate limits, and billing) is managed entirely in the Portal. The Nous admin panel does not expose a dedicated LLM configuration page.
0.4 Navigation Overview
The main rail is entitlement-aware. It can show:
- Chats for chat history and new conversations.
- Projects for chats with shared instructions and files.
- Agents for the agent gallery and member-created agents when the Agents product is enabled.
- Knowledge for connectors and document sets.
- Integrations for service accounts, Slack Integration, and related tools.
- Digital Employees for employee chat and status when that product is enabled.
- Automations for the workspace automation builder when that product is enabled.
- Settings for workspace administration. Personal settings are available from the avatar menu.
Workspace admins see the sections they are authorized to manage. Product-specific entries appear only when Portal enables that product. For example, an enabled Agents product adds Agents and exposes MCP Actions and OpenAPI Actions in the Knowledge sidebar.
0.5 Recommended Reading Order
0.6 Coming Soon
These features are tracked for a future release and are not part of the current admin workflow:
- Standard Answers: pinned Q&A pairs (UI in development).
- Appearance and Branding: tenant-side theming (currently managed in Portal).
- SCIM: managed via Portal; no tenant-side configuration today.
0.7 Conventions Used
Throughout this guide:
- Bold text indicates UI elements (buttons, menus, fields).
Code formattingindicates API endpoints, environment variables, or terminal commands.- Screenshots show the interface in the language of the guide you are reading. Diagrams are still labelled in English in both languages.