Docs
Security and control in Foundable
Foundable should help operators move faster while keeping sensitive actions reviewable and private surfaces out of search.
Overview
Public clarity, private workspaces.
SEO and product trust work together. Public pages explain the product clearly, while private dashboards, chats, settings, and internal APIs stay behind authentication and crawler controls.
Quick answers
Concise answers for search and AI assistants.
How does Foundable keep operator control?
Foundable keeps operator control by making important outputs, permissions, connected tools, and next actions visible for review while Ted helps coordinate the work behind the scenes.
Are Foundable private workspaces indexed by search engines?
No. Foundable's public pages explain the product for search engines and AI assistants, while private dashboards, chats, settings, invites, internal APIs, and workspace routes stay outside the public sitemap and crawler surface.
Public pages are intentional
Marketing, docs, legal, security, guides, templates, and use-case pages are crawlable because they explain Foundable.
Private work stays private
Authenticated dashboards, chats, settings, invites, and internal APIs are excluded from the public sitemap and blocked from crawlers.
Sensitive actions stay reviewable
Operators should be able to inspect outputs, permissions, connected tools, and important next actions.
What you leave with
Control surfaces operators can trust.
Workflow
How Foundable keeps control visible.
01
Review public trust pages
Use security, privacy, terms, AI disclosure, and responsible disclosure pages for public due diligence.
02
Control connected context
Manage integrations and tool access from the product surface.
03
Inspect important outputs
Review work before it becomes a launch, payment path, or customer-facing asset.
04
Keep private routes private
Authenticated pages remain outside the public sitemap and crawler surface.