All data is scoped to a workspace (also called a project). Each user has one of two roles.Documentation Index
Fetch the complete documentation index at: https://docs.foggyhq.com/llms.txt
Use this file to discover all available pages before exploring further.
Roles
| Role | Can do |
|---|---|
| Owner | Everything: invite members, add and remove connectors, edit the knowledge base, manage automations, rotate the license key, delete the workspace. |
| Member | Investigate: run chats, read results, read the knowledge base and automations. Cannot change configuration. |
Invite teammates
- Go to Settings → Team.
- Enter the teammate’s email and pick their role.
- Foggy sends an invite link. Invites expire after 7 days; re-send from the same page if it times out.
Workspaces
Connectors, knowledge base, automations, and chat history are scoped to the workspace — nothing crosses over.- Cloud: you can create multiple workspaces and switch between them from the workspace picker in the sidebar.
- Self-hosted: a single workspace per install. If you need hard data isolation between environments (e.g.
prodvsstaging), run two Foggy installs.
First-login setup (self-hosted)
On first open, enter the email the founder-team recorded when issuing your license, set a password, and you’re in as the workspace Owner. This email gate runs once — subsequent logins use your chosen credentials.Troubleshooting
- “Invite already used” on the invitee’s click — the invite was accepted from a different browser, or it has been claimed. Check the Team page to see if the user is already a member.
- Invitee sees the wrong workspace — the invite is workspace-scoped; double-check you invited them from the workspace you intended. Cloud users can switch workspaces from the sidebar picker.
- Cannot demote the last owner — every workspace must have at least one Owner. Invite a second Owner first, then demote.
Next steps
Security
Data isolation, encryption, and the LLM data flow.
Kubernetes RBAC
How Foggy accesses your cluster. Separate from workspace roles.