Skip to content

Connectors

See what's connected, what it costs, and what you've used — nothing more.

Every figure here is server-owned: the state, the price, this workspace's own usage, and a fixed monthly ceiling shared across every workspace. Today, this build has no connectors available at all.

What Connectors is

Connectors lists every outside service this workspace could use: its price, its terms, and this workspace's own usage against a fixed monthly ceiling. No connector is connected in this build today.

Nothing is fetched or spent until a provider's terms are agreed and it is connected. While terms are unresolved there is no credential form, no connect button and no test-call action — not disabled ones, absent ones.

An administrator can pause a connector for the whole workspace at any time; while paused, nothing further is spent.

Work it supports today

Each of these starts on a real page in the product. Nothing here is planned or promised.

  • Check whether there's room to use a connector right now

    The connector's state and the shared allowance's availability, read exactly as the server computed them.

    1. Open Connectors.
    2. Read the state word and the explanation beneath it.
    3. Check "Availability right now" under the shared safeguard.
  • See what a connector would cost and what its terms allow

    The provider's list price, included credit, query retention and whether results may be stored.

    1. Open Connectors.
    2. Read "Price and terms" on the connector's card.
    3. Check whether storing search results is permitted.
  • See this workspace's own usage

    Exactly how many searches this workspace has used today and this month, and their gross cost.

    1. Open Connectors.
    2. Read "This workspace" on the connector's card.
    3. Compare searches used against your daily and monthly limits.
  • Pause a connector for this workspace

    The connector paused for everyone in this workspace, reversible at any time.

    1. Open Connectors.
    2. Find the connector's card.
    3. Use the workspace pause control, if you hold tenant.admin.

By hand: check the shared safeguard before you rely on it

Devon Okafor at Larkspur Analytics wants to know if there's room left in the shared allowance before running more research today.

  1. Devon opens Connectors.
  2. He finds the connector's card and reads its state and the explanation beneath it.
  3. He checks "Availability right now" under the shared safeguard.
  4. He reads "Searches today" and "Searches this month" under this workspace's own usage.

Fictional names. Start here: /connectors

Or let Noc do it

Noc plans the steps, previews every effect, asks before anything irreversible, and hands back one receipt. Autopilot is off by default.

Kept with a person, on purpose. Connecting a provider, changing what it may spend, or pausing it is an administrator's decision about money and data leaving this workspace. No Noc capability may take it — this stays a person's own action, every time.

What stays in your hands

  • Only an administrator may pause it

    The workspace pause control is only offered to a person holding tenant.admin; reading connector status needs only connectors.read, which every member holds.

  • Your own usage is exact; everyone else's is deliberately coarse

    This workspace's searches, cost and limits are shown exactly. What every other workspace has used is never published, only whether there is room right now — so one workspace's numbers can never be used to infer another's.

  • A credential's value is never shown

    The page states only whether a credential is bound; its value is never stored here or shown anywhere on this page.

The honest states

What the product really shows when there is nothing yet, when it refuses, and where this build stops.

  • What you see first

    No connectors are available

    Nothing is configured for this environment. This is the complete list, not a partial one.

  • When something is refused

    A refusal names the exact permission

    A person without connectors.read sees "You don't have access to connectors" and is told which permission to ask for, not an error page.

  • Not available in this build

    Every connector reports unavailable today

    Every metered connector in this build reports temporarily unavailable until its provider is approved and connected; nothing is fetched or spent.

Next

To see Connectors you need a membership in a workspace. Acting needs the permissions your administrator grants.