> For the complete documentation index, see [llms.txt](https://docs.11x.ai/llms.txt).
> Use it to discover all available pages before exploring further.

# 11x Admin guide

The ongoing admin reference: users and access, keeping the knowledge base current, tuning qualification, watching deliverability, and a monthly review cadence.


This is the **ongoing** admin reference, for after you are live. If you are setting up for the first time, use [Getting started as an Admin](/help-center/get-started/getting-started-as-an-admin) instead - that covers the first week end to end.

<Callout kind="info">
**Who this applies to:** 11x workspace Administrators running a live deployment. Most of what follows is light but recurring - the failure mode is not difficulty, it is drift.
</Callout>

## The five things that need ongoing attention

| Area | Cadence | Why it drifts |
| --- | --- | --- |
| **Knowledge base** | On every product or positioning change | Output stays fluent while becoming subtly wrong |
| **Qualification thresholds** | Monthly, against rep feedback | Market and product change; thresholds do not |
| **Deliverability** | Weekly glance, act on any dip | Reputation degrades gradually and repairs slowly |
| **CRM hygiene** | Quarterly | Stale ownership breaks exclusions silently |
| **User access** | On every joiner and leaver | Access outlives employment |

## Users and access

<Steps>
  <Step title="Add receiving reps with calendars connected" icon="calendar">
    A rep routed a meeting without a connected calendar produces a booking failure. Make calendar connection part of onboarding.
  </Step>
  <Step title="Remove access promptly when people leave" icon="user-minus">
    Also check whether they authorized any integration. A CRM connection made with a personal account breaks when they go - see [cannot connect CRM](/help-center/troubleshooting/cannot-connect-crm).
  </Step>
  <Step title="Review who holds admin rights" icon="shield">
    Quarterly. Admin can change targeting and messaging for the whole workspace.
  </Step>
</Steps>

## Keeping the knowledge base current

Update it when any of these happen:

- Positioning or messaging changes
- You launch or sunset a product
- A new competitor becomes relevant, or an existing one changes their pitch
- You win a notable customer worth citing
- A recurring objection emerges that is not yet covered
- Pricing posture changes

<Callout kind="alert">
A stale knowledge base degrades quietly. Output stays fluent while becoming subtly wrong, which is much harder to catch than an obvious failure. Assign it an owner and a review trigger, not just a review date.
</Callout>

Use **version history** to change one thing at a time. If you rewrite positioning, differentiation, and proof points in the same week, a drop in reply rate tells you nothing about which change caused it. See [knowledge base](/alice/knowledge-base).

## Tuning qualification

The signal that matters is **rep disagreement**.

<Steps>
  <Step title="Collect flagged meetings formally" icon="thumbs-down">
    Ask reps to flag any meeting they would not consider qualified. Unflagged bad meetings mean the threshold stays wrong and trust erodes quietly.
  </Step>
  <Step title="Read disqualified transcripts monthly" icon="file-search">
    This is where the expensive mistakes hide. A wrongly disqualified good lead disappears without anyone reporting it.
  </Step>
  <Step title="Separate data problems from criteria problems" icon="git-compare">
    A lead disqualified for a missing attribute the company actually has is a data issue, not a scoring one.
  </Step>
  <Step title="Change one criterion at a time" icon="sliders-horizontal">
    So you can attribute the effect.
  </Step>
</Steps>

## Watching deliverability

| Metric | Act when |
| --- | --- |
| Inbox placement | Declining - hold volume immediately |
| Bounce rate | Above near-zero - fix the data source |
| Complaint rate | Any sustained level - tighten the ICP now |
| Domains in rotation | Several at once - a targeting problem, not a domain problem |
| Call connect rate | Declining - check number reputation and region match |

Rotation and cooldown protect you from symptoms, not causes. If domains rotate repeatedly, stop increasing volume and check complaint rate first. See [mailbox health](/analytics/mailbox-health) and [connection boosts](/julian/connection-boosts).

## Monthly review

<Steps>
  <Step title="Pipeline per play, not reply rate" icon="trending-up">
    Compare motions on influenced pipeline. A revival play with a lower reply rate and higher pipeline per reply is the better play.
  </Step>
  <Step title="Average deal size" icon="dollar-sign">
    If it is drifting down, the ICP is reaching too far down-market.
  </Step>
  <Step title="Rep feedback themes" icon="message-square">
    Not individual complaints - patterns.
  </Step>
  <Step title="Read a sample of auto-sent replies" icon="inbox">
    Especially objection-category replies. See [smart replies](/alice/smart-replies).
  </Step>
  <Step title="Check the changelog" icon="clock">
    New capabilities worth enabling. See [changelog](/changelog).
  </Step>
</Steps>

## Quarterly

- **Audit CRM ownership and opportunity state** - the data exclusions depend on
- **Review admin access**
- **Re-read the knowledge base end to end** - not just the parts you edited
- **Revisit tier sizing** against actual volume and peak concurrency

## Next steps

<Columns cols={2}>
  <Card title="Getting started as an Admin" icon="shield-check" href="/help-center/get-started/getting-started-as-an-admin" horizontal>
    The first-week setup walkthrough.
  </Card>
  <Card title="Analytics overview" icon="chart-line" href="/analytics/overview" horizontal>
    Where the monthly review numbers live.
  </Card>
  <Card title="Security and data handling" icon="shield" href="/security/overview" horizontal>
    Access scoping and credential hygiene.
  </Card>
  <Card title="Getting started as a User" icon="user" href="/help-center/get-started/getting-started-as-a-user" horizontal>
    Share with new reps.
  </Card>
</Columns>

## Need help?

Email [support@11x.ai](mailto:support@11x.ai), or [book time with the team](https://www.11x.ai/demo).
