What is your role?
As an admin you are the first point of contact for your organisation inside FixControl. Your responsibilities:
- Connect at least one intake channel — email (Gmail or Office 365), Slack, or Microsoft Teams
- Connect at least one code host — GitHub, GitLab, or Bitbucket — so agents can open pull/merge requests
- (Optional) Connect an issue tracker — Jira or Linear — to mirror approved issues
- Invite colleagues and assign roles
- Upload customer-specific knowledge (FAQs, product docs) to the Knowledge store
You do not manage servers, set up Postgres, configure AI keys, or run schema migrations — FixControl runs as a cloud service and we handle the infrastructure. You configure only what belongs on your side: your support channels, your repositories, your team.
Day one: four steps
1. Connect an intake channel (5 minutes)
In Settings → Integrations pick the channel where your customers currently report problems. Most teams start with email.
| Channel | Detailed guide |
|---|---|
| Gmail | Gmail OAuth |
| Office 365 / Exchange | Communication channels |
| Slack | Communication channels |
| Microsoft Teams | Communication channels |
From that moment, customer messages land in the Inbox. You can connect more channels later.
2. Connect a code host
If you want FixControl to automatically open pull or merge requests for bug fixes, connect a Git provider in Settings → Integrations. For production we recommend the App or OAuth flow; a personal token is fine for a single-repo install.
| Provider | Detailed guide |
|---|---|
| GitHub | GitHub |
| GitLab, Bitbucket Cloud, Bitbucket Server | Git providers |
3. Link a codebase to a project
A codebase is a specific repository (your GitHub/GitLab/Bitbucket repo, for example) attached to a project. The Codebase Agent reads it so each issue knows where the fix should land.
Do this in Settings → Codebases. One project can have multiple codebases attached when a fix may span repos.
4. Invite colleagues
Go to Settings → Users and invite your team. Assign a role per user:
| Role | What they can do |
|---|---|
| admin | Everything — settings, connections, users |
| manager | Assign issues, review, approve replies |
| operator | Handle issues and send replies |
See Users & Companies for details.
Next: teaching the agents what you know
Once the basics are in place, the next step is giving context to the AI:
- Knowledge — upload your product documentation, FAQs, and customer-specific manuals. The Support Agent uses these when drafting replies. See Knowledge.
- Memory — write behavioural rules specific to your organisation, e.g. "escalate every PAYMENT flag directly to finance@...". See Memory.
Without these the AI falls back to generic knowledge. With them, it produces answers that match your product.
Account & subscription
Your subscription is billed monthly. There is no self-service billing page yet — for plan changes, invoicing, or usage questions, reach out via /contact. Plan limits (seats and monthly AI actions) are enforced in-product once they are provisioned for your workspace.
Optional: tracker, webhooks, API
Once intake and code hosting are wired up, three optional surfaces broaden what FixControl can do:
- Issue tracker — mirror approved issues to Jira, Linear, Freshdesk, Odoo Helpdesk, or TOPdesk so PMs, engineers, and support agents see them in their normal workflow. See Issue trackers.
- Outbound webhooks — push FixControl events into your own systems. See Webhooks.
- Public API — automate against FixControl from your own scripts. See Public API.
Skip any you don't need today; they can be added later without re-onboarding.
FAQ
Do I need to provide a Claude API key? No. AI access is included in your subscription. We pick the provider, you pay monthly.
Can I connect multiple inboxes or chat workspaces? Yes. Add them one by one. For email, use recipient routing to direct incoming mail per address to the right workspace. For Slack/Teams, every workspace or tenant connects independently.
Can I use more than one Git host at the same time? Yes. A FixControl tenant can have, for example, GitHub for production repos and GitLab for an internal monorepo. Each codebase points at exactly one provider; agents pick the right one automatically.
Will my customers also see FixControl? No. Your customers don't see FixControl — they send messages to your support address or chat channel and receive a reply from your team. FixControl sits behind that surface.
What about privacy? Every tenant is fully isolated. Other FixControl customers cannot see your data. See Security & audit for details.