StackJack 0.1.0.7178+75abd4c

This release lets a single AI-tool registration serve an entire organization rather than one person. Tools such as Copilot Studio, which present one registration for every connection, can now be used by every member of your team, with each person's access controlled individually.

New features

• Shared AI-tool connections for the whole team. When an AI tool registers itself with StackJack automatically (for example, Copilot Studio), a second member of the same organization can now sign in through that same registration and use it. Previously the second person was refused. Each person gets their own authorization on the shared connection; a connection always acts as the person who signed in on it.
• Per-person control on shared connections. From the Team page, a team administrator can turn an individual off a shared connection and back on again without affecting colleagues who use it.
• Owner notification on first authorization. The account owner receives an email the first time each person authorizes an app through this lane, including when a colleague joins a connection a teammate set up. Re-authorizations by the same person do not send another email.

Improvements

• Access to a shared connection is checked on every request, so turning someone off takes effect on their very next request rather than after a delay.
• When a team member is deactivated, only their own access to shared connections is removed; the connection stays live for everyone else who uses it. If that member is later reactivated or re-invited, their access is restored.
• A person whose access to a shared connection has been turned off now sees a clear explanation when they try to connect, instead of a generic failure.
• The Endpoints and Team pages now show every person authorized on a shared connection, and the onboarding wizard no longer prompts a member to set up a connection when they already have access through a colleague's shared registration.
• The Copilot Studio documentation page has been rewritten: it no longer tells you to avoid reusing a connection, and it now states that every connection runs as the person who signed in on it.

Bug fixes

• The "new app connected" email sent to the account owner now identifies the owner by their account email address instead of an internal identifier.
• If an administrator's permissions are removed while they still have the Team page or the shared-connections view open, attempting an action now shows a plain message that the permission is no longer available, rather than an internal error message.