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 HaloPSA, NinjaOne, Microsoft Azure, Microsoft Graph and 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: their sign-in is the shared connection, so a personal per-user credential would be redundant. The one exception is an Old personal sign-in: when the organization's connection is a separate shared connection and a personal sign-in the owner made under an earlier setup is Disabled, it is listed under Your personal sign-ins with Remove.

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, or still holds a personal sign-in of yours from an earlier setup (the Old personal sign-in card below). 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.

Where your organization holds several named connections of one connector — one HaloPSA per acquired company, one N-central server per customer — you get one card per connection, each named after that connection. Sign in to each one separately: connecting to "Acme Manufacturing" does nothing for "Contoso Ltd". A connection your administrator has disabled does not get a card, because there is nothing you could use it for.

Card statuses and what to do

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: a shared API key is the organization's credential and already works for you without a personal sign-in.

If the dashboard reports one of these connectors as Disabled (your personal connection), that is a personal sign-in left from an earlier setup. It does not stop your tool calls, which use the organization's credential. Remove it from the Old personal sign-in card here, or ask an owner or administrator to remove it from Team.

If the dashboard reports one as Authentication failed (your personal connection) or Can't reach it (your personal connection), and its card here reads Old personal sign-in, your tool calls are still using that old sign-in and they are failing. Select Remove on the card, and your tool calls then use the organization's credential.

The one case where "connected" isn't enough. A connector configured by signing in rather than with an API key stores the authorizing person's own identity. StackJack will not run your tool calls under it, because that would give you their permissions and record your actions as them in the vendor's audit log. What you see on the card depends on one further thing: whether that connector offers a per-member sign-in of its own.

• It does — you get Authorization Required (or Re-authorize Required) and a Connect button, and you sign in with your own account. HaloPSA, NinjaOne, Microsoft Azure and Microsoft Graph work this way today.
• It doesn't — the connector is authorized once for the whole organization, there is no personal sign-in to add, and the card reads Owner Sign-in Only. Reddit Ads is one example.

Either way the organization's shared connection is untouched and keeps working for its owner. If this connector is the only one your organization subscribes to, the refusal reaches your AI as an HTTP 403 carrying personal_sign_in_required rather than as a tool result — the same message, one layer earlier.

The full rule set is on one page: Who can use which identity.

Connecting with your own account (HaloPSA, NinjaOne, Microsoft Azure, Microsoft Graph)

1. Select Connect on the card. You're sent to the vendor's own sign-in page.
2. Sign in with your own HaloPSA, NinjaOne or Microsoft account and approve access.
3. The first time you connect, a one-time credentials view shows the MCP endpoint URL, your new personal Client ID, and your new personal Client Secret. When you sign in again later (Re-authorize or Reconnect), you land back on the Connectors page with a message that your sign-in is renewed: you keep the key you already have, and nothing changes in your AI tool.

For the two Microsoft connectors there is nothing for an administrator to prepare first: they authorize against StackJack's own registered Microsoft application, so you can connect even where your organization has no shared Microsoft connection. What you can then reach is whatever your own Microsoft roles allow, and nothing more.

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, select Revoke my key on the card and confirm; your next Reconnect then creates a new key and shows it once. (An owner or administrator can also revoke it on Team.) Signing in again without revoking does not show a new key. If you connect your AI app by signing in with your StackJack account (Claude, ChatGPT, Microsoft Copilot), you don't need the key at all.

Your first connection also creates a personal MCP client for you (named "your name's connector key"). Signing in again later renews your sign-in and keeps that client, so the key already in your AI tool keeps working, and StackJack updates the client's tool list to your current tools at the same time. If you were given a new tool or role since you first connected, select Reconnect once and the new tools reach your key.

Revoke my key on a card switches off your own personal StackJack key for that connection, after a confirmation. Any AI tool that uses the key stops working at once; your sign-in itself stays connected. Your next Reconnect (or Re-authorize) creates a new key and shows it once.

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 that connection's setup) and paste your personal User-API Token (JWT) — generated in N-central under your own user's API Access settings. Two N-central connections are two different servers, so check the address before you paste a token minted on the other one.
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 a shared API key, so there's nothing for you to authorize. Only HaloPSA, NinjaOne, Microsoft Azure, Microsoft Graph and N-able N-central ever ask for a personal sign-in.