8 items
AUTHENTICATION
Authentication and external access are token-based, not generic SSO platform marketing
The implemented access model centers on agent API keys, signed or encrypted tokens, origin controls, and agent/context resolution.
ENTERPRISE FEATURES
Agent management controls built around the PrintSpeak enterprise workflow
The real admin surface centers on agent creation, versioning, import/export, scope controls, and operational configuration inside the enterprise UI.
These are the builder and governance features clearly exposed in the PrintSpeak AI agent management screens.
8 matrix itemsFamily detail page
Feature family placeholder
Reserved for a dedicated interface preview, workflow diagram, or annotated screenshot.
MATRIX
Capability breakdown
Agent builder workspace
Includes
Dedicated enterprise pages for creating, editing, and organizing AI agents.
Why it matters
The admin flow is centered on `/enterprises/ai_agents`, not a hidden config file or developer-only interface.
Version history
Includes
PaperTrail-backed create, update, and destroy history for agent records.
Why it matters
Editors can inspect prior changes instead of treating each prompt edit as ephemeral.
Import and export
Includes
Base64-backed export/import for agent configs, including prompts, tools, facets, and category settings.
Why it matters
Makes it practical to clone or move agents between enterprises without rebuilding them by hand.
Enterprise and global scope
Includes
Agents can be enterprise-scoped, global, or marked for external use.
Why it matters
This matches the actual `enterprise_id = 0`, external toggle, and scope logic in the model/controller layer.
External-use validation
Includes
Warnings when externally available agents depend on non-external routed assistants.
Why it matters
The builder surfaces configuration issues before an embed is pushed live.
Category assignment
Includes
Prompt categories with single-agent or multi-agent behavior by category.
Why it matters
The category system is part of the real agent model and determines how agents are used in the app.
Bulk model edits
Includes
Enterprise users can update the selected model across multiple agents.
Why it matters
This is more grounded than claiming rollout policies or release orchestration that the code does not show.
Translated names and descriptions
Includes
Agent name and description translation fields are generated and rendered in the UI.
Why it matters
That is a concrete multilingual capability in the admin layer, unlike broader claims about full platform localization.
| Capability | Includes | Why it matters |
|---|---|---|
Agent builder workspace | Dedicated enterprise pages for creating, editing, and organizing AI agents. | The admin flow is centered on `/enterprises/ai_agents`, not a hidden config file or developer-only interface. |
Version history | PaperTrail-backed create, update, and destroy history for agent records. | Editors can inspect prior changes instead of treating each prompt edit as ephemeral. |
Import and export | Base64-backed export/import for agent configs, including prompts, tools, facets, and category settings. | Makes it practical to clone or move agents between enterprises without rebuilding them by hand. |
Enterprise and global scope | Agents can be enterprise-scoped, global, or marked for external use. | This matches the actual `enterprise_id = 0`, external toggle, and scope logic in the model/controller layer. |
External-use validation | Warnings when externally available agents depend on non-external routed assistants. | The builder surfaces configuration issues before an embed is pushed live. |
Category assignment | Prompt categories with single-agent or multi-agent behavior by category. | The category system is part of the real agent model and determines how agents are used in the app. |
Bulk model edits | Enterprise users can update the selected model across multiple agents. | This is more grounded than claiming rollout policies or release orchestration that the code does not show. |
Translated names and descriptions | Agent name and description translation fields are generated and rendered in the UI. | That is a concrete multilingual capability in the admin layer, unlike broader claims about full platform localization. |
RELATED FAMILIES
Continue exploring the rest of the platform
8 items
SDK
SDK and embedding capabilities are script-tag and helper based
The implemented surfaces are a standalone widget script, a JS API, trigger elements, and internal Rails/Stimulus helpers.
8 items
WHITE LABEL
White-label embedding is theme-driven and widget-focused
The external widget supports multiple themes, title overrides, display modes, and custom theme builds for branded deployments.