Docs

Security and control in Foundable

Foundable helps operators move faster with authenticated access controls, scoped autonomy settings, and a clear separation between public and signed-in product routes.

Published · Published by Foundable

Overview

Public clarity, authenticated product routes.

Public pages explain Foundable, while dashboards, chats, settings, and internal APIs require authentication and purpose-specific authorization.

Quick answers

Practical answers for the next decision.

How does Foundable keep operator control?

Foundable surfaces supported outputs, permissions, run status, and connected integrations while letting operators choose review or autonomy settings for supported motions.

Are signed-in Foundable routes publicly accessible?

No. Dashboards, chats, settings, invites, and internal APIs require authentication and purpose-specific authorization. Public discoverability settings are an additional boundary, not a substitute for access control.

Public pages are intentional

Marketing, docs, legal, security, guides, templates, and use-case pages are public because they explain Foundable.

Signed-in routes require access control

Dashboards, chats, settings, invites, and internal APIs require authentication and purpose-specific authorization.

Autonomy is scoped

Operators choose supported review or autonomy modes, scopes, budgets, schedules, and connected accounts. Completed actions use the connected provider's available edit, recall, refund, or reversal controls.

What you leave with

Control surfaces operators can trust.

Public trust resources
Public and signed-in route boundaries
Reviewable outputs and permissions
Clear separation between public marketing and authenticated foundable data

Workflow

How Foundable keeps control visible.

Review public trust pages

Use security, privacy, terms, AI disclosure, and responsible disclosure pages for public due diligence.

Control connected context

Manage integrations and tool access from the product surface.

Inspect important outputs

Inspect supported outputs and choose review or autonomy settings before enabling customer-facing motions.

Protect signed-in routes

Authenticated pages use access controls that are independent of public discoverability settings.

Continue to footer navigation