How Faberiq is Organized
Before you build anything, it helps to know how Faberiq structures your data and your team. This page explains the three ideas everything else builds on: your organization, your projects, and member roles.
The organization: your workspace
An organization is your company's tenant in Faberiq. Everything you create belongs to exactly one organization, and nothing in it is visible to any other organization.
You do not create an organization manually. The first time you sign in to the studio without an existing membership, Faberiq creates one for you automatically, named after you (for example, "Jordan's Org"), and makes you its admin. The new organization comes with:
- A starter project named Portal, which is also the organization's default project.
- A credit wallet with a one-time grant of 1,000 trial credits (see Billing & Credits).
The organization is the boundary for:
- Members and roles: who can sign in and what they can do (managed under Account, then Users in the sidebar).
- Billing and credits: usage anywhere in the organization draws from one wallet.
- Collections: structured data tables are shared across all projects in the organization (see Collections).
- AI provider settings: admins can point the organization at their own LLM provider under Settings.
- The customer portal: branding, custom domain, and customer accounts belong to the organization.
- Lifecycle: an admin can permanently delete the whole organization (see Account Deletion).
Projects: where you build
A project is the working unit inside an organization. Each project isolates its own:
- Workflows and agents
- Connectors
- Knowledge bases, folders, and documents
- Chat sessions and conversations
Use separate projects for separate assistants, business units, or environments. Work in one project cannot see the workflows, connectors, or knowledge bases of another project.
To switch projects or create a new one, use the project selector in the top bar of the studio; it has a search box and a New project button. You can also manage projects under Account, then Projects, where you rename or delete them.
Two project-level settings matter later:
- Default project: the organization's default project (the starter Portal project unless changed). New customer accounts are automatically granted access to it, so workflows placed there are available to every customer who signs in to your portal.
- Default workflow: inside a project, you can mark exactly one workflow as the project's default (a checkbox in the workflow's Edit Workflow dialog labeled "Default workflow for this project"). Marking a workflow default clears the flag from any other workflow in the project. Chat / Cowork preselects this workflow when you have not chosen one.
What is scoped where
| Resource | Scope | Notes |
|---|---|---|
| Members, roles, invites | Organization | Managed on the Users page by admins. |
| Billing and credits | Organization | One wallet for the whole workspace. |
| Collections | Organization | Shared across all projects on purpose, so one project can ingest data that another reads. |
| LLM provider settings, secrets, branding | Organization | Admin-only settings. |
| Workflows and agents | Project | One workflow per project can be the default. |
| Connectors | Project | Connect channels and services per project. |
| Knowledge bases, folders, documents | Project | Retrieval is further filtered by knowledge base and folder selection. |
| Chat sessions | Project and user | Your chat history in a project is private to your account. |
Member roles
Every member of an organization has one role. There are four:
| Role | Who it is for | What it can do |
|---|---|---|
| Admin | Workspace owners | Everything. Builds like a developer, plus manages members and invites, changes roles, edits the organization profile and branding, manages customers and workflow assignments, configures the AI provider, manages billing and secrets, installs starter bundles, and can delete the account. |
| Developer | Builders | Creates and edits projects, workflows, agents, connectors, knowledge bases and documents, collections, appointments, and invoices. Cannot manage members, billing, or organization settings. |
| Standard | Everyday users | Signs in to the studio, uses Chat/Cowork, and views work. Cannot create or edit workflows, connectors, or knowledge, and cannot administer the organization. |
| Customer | Your customers | Portal only. Customers sign in to your customer portal to chat and complete tasks. A customer account that tries to use the studio is rejected with "Customer users are restricted to the customer portal." |
To add teammates, open Account, then Users, and invite them by email with a role of admin, developer, or standard. Admins can change a member's role or remove members and pending invites on the same page.
Customer accounts are not created on the Users page. Customers appear when they sign up through your portal, or when you invite them from customer management. See Customer Management and Customer Portal.
There is also a platform-level super admin role used by Faberiq operators to run the platform itself. It is separate from organization roles; see Super Admin.
Studio and customer portal contexts
Faberiq runs two separate applications against the same organization:
- The studio (this documentation's main subject) is for your team: admins, developers, and standard members.
- The customer portal is for people with the customer role. It shows your branding, offers chat with the workflows you assign, and lists onboarding tasks.
Every request identifies which application it comes from, and access rules differ by context. Your team members use the studio; customer accounts are restricted to the portal. A customer who authenticates on your portal for the first time is enrolled into your organization automatically as a customer, and Faberiq unifies their identity by email address, so the same person invited by email and signing in with Google ends up as one customer record.
Signing in
The studio supports two sign-in methods:
- Email and password. Create an account with your email and a password. Faberiq emails you a verification code; enter it on the verify page before your first sign-in. Password changes and resets are available from the sign-in page (Forgot password) and in the studio under Account, then Password.
- Google. Choose Continue with Google on the sign-in or sign-up page to authenticate with a Google account. No password or verification code is needed.
Both methods lead to the same account when they use the same email address.
Personal API tokens
Besides interactive sign-in, you can create personal API tokens for scripts and integrations. Tokens are created, rotated, and revoked on the API & Integrations page, act with your identity and permissions, and start with the prefix af_pat_. See API & Integrations for how to create one and call the API.
Related pages
- Quickstart: put all of this into practice in one sitting.
- Workflows: what lives inside a project.
- Billing & Credits: how the organization wallet works.