Skip to main content
Connector basics

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…

Written By Christopher Scaminaci

Last updated 2 days ago

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 actions on HaloPSA, NinjaOne, N-central, ConnectWise and the Microsoft connectors (Microsoft Azure, Microsoft Graph, Microsoft Defender for Endpoint, Microsoft Exchange Online, Microsoft Purview, Microsoft SharePoint Admin, Microsoft Teams Admin and Microsoft Power Platform Admin) 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

StatusWhat it meansWhat to do
ConnectedYour own personal connection is active.Nothing — or Reconnect (OAuth) / Update JWT + Test (N-central) if you need to refresh it. Revoke my key switches off your personal StackJack key for that card (see below).
Authorization RequiredThis connector supports personal sign-ins and you haven't connected yet.Select Connect (HaloPSA, NinjaOne and the Microsoft connectors) or Set JWT (N-central).
Re-authorize RequiredYour personal connection stopped working (for example, your access was revoked or your sign-in expired in the vendor). This status also appears while the sign-in is still switched on but the vendor refuses it.Select Re-authorize and sign in again.
Administrator Action Required (HaloPSA, NinjaOne and the Microsoft connectors)The vendor refuses your sign-in until an administrator acts. For HaloPSA and NinjaOne, the organization's application has a problem (for example, its client secret changed) that an owner or administrator of your StackJack organization fixes. For Microsoft, StackJack needs admin consent or admin approval in your Microsoft organization, or your account is not assigned to the StackJack application there. The card shows the reason and who can fix it.Ask that administrator to act; signing in again does not fix it on its own. Afterwards, select Re-authorize if your tools have not started working again.
Token Refused (N-able N-central)N-central refuses your personal token (JWT), for example because it was regenerated or revoked.Generate a new User-API token in N-central, then select Update JWT and paste it.
Can't reach it (the Microsoft connectors and N-able N-central)StackJack has not been able to complete a check of your sign-in for several days. It has not been rejected.Nothing to re-enter. StackJack keeps checking, and your tools start working again on their own. On N-central, Test checks again now.
Owner Sign-in OnlyTwo things are true at once: your organization's only credential for this connector is a shared sign-in that carries the account owner's own identity, and this connector has no per-member sign-in — it is authorized once for the whole organization. StackJack never runs your calls under someone else's sign-in, so this connector's tools will refuse for you with personal_sign_in_required. A connector that does have a per-member sign-in never shows this status; it shows Authorization Required with a Connect button instead.Nothing you can do on your own. Ask an owner to run this connector's tools, or to make you an owner of the workspace. Reddit Ads is one connector in this shape.
Old personal sign-in (with an Active, a Disabled, or a failure badge such as Authentication failed or Can't reach it)A personal sign-in you made under an earlier setup, on a connector your organization now runs on its own shared credential. While it is Disabled, your tool calls use the organization's credential. While it is Active or shows a failure badge, your tool calls still use it instead of the organization's credential, and with a failure badge those calls fail.While it is Disabled or shows a failure badge: select Remove, and your tool calls then use the organization's credential. While it is Active: an owner or administrator removes it from Team. Co-owners and Administrators can remove their own there: select Personal Sign-ins on your own row.

ConnectWise PSA: your own API keys

ConnectWise gets a card for each of your organization's ConnectWise connections, because you can add your own ConnectWise API keys there. Your own keys are optional: without them, your ConnectWise changes are recorded under your organization's API member.

BadgeWhat it meansWhat to do
Shared KeyYou have no own keys on this connection, so your calls use the organization's key.Optional: in ConnectWise, open My Account > API Keys and select +, then select Add my ConnectWise API keys and enter the key pair.
Your Own KeysYour calls use your own keys, and ConnectWise records your changes under your own member. Your own ConnectWise security role decides what they can do.Nothing. Replace keys, Test and Remove are there when you need them.
Keys RefusedConnectWise refuses your own keys, so your ConnectWise calls fail.Select Replace keys, or Remove to go back to the organization's key.
Keys Switched OffYour own keys were switched off, for example because your organization moved its ConnectWise connection. The card says why. Your calls use the organization's key meanwhile.Select Replace keys and save your keys again, or Remove them.
Member ID (Experimental)Your organization turned on the experimental member ID option for this connection, and an owner or administrator set your ConnectWise member ID. The card shows it but you cannot change it: the member ID makes StackJack act with that member's own security role, so only an owner or administrator sets it.Nothing. Ask an owner or administrator to change it on the Team page. Your own keys take precedence if you also add them.

If your organization requires each person's own ConnectWise API keys, the card says so: without them you can read from ConnectWise but not change anything. See ConnectWise PSA for the details.

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 and the Microsoft connectors 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)

  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 Microsoft connectors there is nothing for an administrator to set up in StackJack first. You can connect even where your organization has no shared Microsoft connection. You sign in through the same Microsoft app your organization uses: StackJack's own app, or your organization's own app if it connected with one. Microsoft may still need an administrator's approval in your directory first. If it does, ask an owner or administrator of your StackJack organization: they arrange it from Set up Microsoft. 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, N-able N-central and the eight Microsoft connectors (Microsoft Azure, Microsoft Graph, Microsoft Defender for Endpoint, Microsoft Exchange Online, Microsoft Purview, Microsoft SharePoint Admin, Microsoft Teams Admin and Microsoft Power Platform Admin) ever ask for a personal sign-in.