read thedocs.

[ docs // guides & reference ]

Connector setup guides, tool references, auth flows, and platform concepts — everything you need to run StackJack, in one place.

Browse the Docs All Connectors
34 connectors documented // 6,712 tools referenced // setup, auth & platform guides
↓

No pages match that search. Clear it

← All documentation

Your personal connector sign-ins (for Team Members)

Your personal per-user connector access now lives inside the Connectors page (/connectors), in a section called Your personal sign-ins. There is no separate "My Connectors" page in the sidebar any more — everything below appears on the one Connectors page, tailored to your role.

The old /my-connectors address still works — it forwards you to /connectors (keeping any sign-in result in the address so a completed authorization still shows its success or error message). Update any saved bookmark to /connectors when convenient.

Where your section appears

Open Connectors in the left sidebar. What you see depends on your role:

  • Members see only the Your personal sign-ins section — the per-user connectors that need your own account, plus a note about the ones that already work automatically.
  • Co-owners and Administrators see the organization-shared connector grid and, below it, the same Your personal sign-ins section — because your Halo / NinjaOne / N-central actions can attribute to you even while you manage the shared connection above.
  • The organization's primary owner doesn't get a personal section at all: their sign-in is the shared connection, so a personal per-user credential would be redundant.

You'll see one card in this section for each connector that (a) your organization has activated, (b) you have at least one assigned tool for, and (c) supports a personal sign-in. Connectors that run entirely on shared credentials are summarized in a single line rather than shown as cards, so the ones that actually need you stand out.

Card statuses and what to do

Status What it means What to do
Connected Your own personal connection is active. Nothing — or Reconnect (OAuth) / Update JWT + Test (N-central) if you need to refresh it.
Authorization Required This connector supports personal sign-ins and you haven't connected yet. Select Connect (HaloPSA / NinjaOne) or Set JWT (N-central).
Re-authorize Required Your personal connection stopped working (for example, your access was revoked or your sign-in expired in the vendor). Select Re-authorize and sign in again.

Connectors that use your organization's shared credentials don't get an action card — they're rolled up into a line like "3 more connectors use organization-shared credentials and work automatically — nothing for you to do." That's expected: shared connectors already work for you without a personal sign-in.

Connecting with your own account (HaloPSA / NinjaOne)

  1. Select Connect on the card. You're sent to the vendor's own sign-in page.
  2. Sign in with your own HaloPSA or NinjaOne account and approve access.
  3. You land back on the Connectors page. A one-time credentials view shows the MCP endpoint URL, your new personal Client ID, and your new personal Client Secret.

Important — the secret is shown exactly once. It is available briefly and is deleted the moment it's been viewed. Copy the values into your AI tool right away. If you miss the window, no harm done — just select Reconnect on the card to run the flow again and mint fresh credentials.

Connecting also creates a personal MCP client for you (named "your name's connector key") and retires any older personal clients you had for the same connector — so the credentials you just copied are the ones that work.

Connecting N-able N-central (personal JWT)

N-central doesn't use a browser sign-in. Instead:

  1. Select Set JWT on the N-central card.
  2. In the dialog, confirm the server URL (pre-filled from your organization's setup) and paste your personal User-API Token (JWT) — generated in N-central under your own user's API Access settings.
  3. Save. StackJack validates the token immediately and tells you whether it works.

Use Update JWT later if you regenerate your token in N-central (regenerating invalidates the old one), and Test any time to live-check your token.

Note: personal connections require your organization's connector subscription to be active (any plan, including Free) and require your admin to have assigned you tools for that connector. If a Connect button doesn't work for you, ask your administrator.

Your own AI tool's catalog

The same section carries a My AI tool catalog card, where you choose how many tools your AI connection (claude.ai, Claude Desktop, Cursor, and so on) loads when it signs in with your StackJack account. It overrides the organization default. See Catalog modes for what the modes mean.

If the section is empty

  • "Your administrator hasn't assigned you any connector tools yet" — ask your admin to assign tools to you on the Team page.
  • "Nothing here needs your personal sign-in" — every connector your organization has activated for you uses shared credentials, so there's nothing for you to authorize. Only HaloPSA, NinjaOne, and N-able N-central ever ask for a personal sign-in.