Outborn Agent Platform · Manual

Built-in apps

Understand first-party app enablement and how it differs from external connections.

Applied guidance

Best practices for built-in apps

Recommended

  • Confirm the built-in app is enabled and the user has effective product access.
  • Set up external provider authentication through its separate connection flow.

Avoid

  • Do not confuse catalog availability with a grant to external data.

01

Browse the app catalog

Built-in apps are first-party OutbornAI capabilities. Administrators can enable or disable them at organization level and, where supported, by Space.

02

Connect external systems separately

Gmail, databases, and other external systems use application or MCP connections with their own authentication and permission state. They are not downloaded built-in apps.

03

Check effective access

Server-side role, Space, entitlement, and policy checks determine effective access even when a feature appears in navigation.

Related documentation

Connections & Agent Connect →Spaces and access →Built-in apps and external connections →
Open Outborn Agent Platform ↗Outborn Agent Platform overviewContact Outborn