A small team in one environment: each person signs in as themselves

[Morriz]

We run a small team on T3. Everyone works with agents all day — on desktop, iPad and phone — and everyone works on the same machines and projects. T3 has become the cockpit for all of it.

There is one thing we cannot do yet: let each teammate sign in as themselves. Today an environment links to exactly one T3 Connect account. Anyone else either borrows the owner's sign-in (and everything they do looks like the owner) or loses the native experience (no notifications, no Live Activities).

What this looks like in practice

• Ana asks an agent to prepare a database migration. Bas reviews it an hour later from his phone. To the agent — and in the thread history — both are "user".
• An agent finishes a long task. The notification goes to the environment owner, not to the person who asked for the work.
• Months later someone asks "who approved this plan?" The record says user.
• Each person has their own preferences and responsibilities. The agent cannot tell whose they should follow.

What we'd like

1. Several T3 Connect accounts per environment. The owner keeps control of the environment; additional people link their own accounts to it and get the same native experience — sign-in, notifications, Live Activities — on their own devices.
2. Know who is speaking. Keep the signed-in person on each message they send (T3 already verifies who connects, and already records the origin of threads started by outside agents), and let the agent see who it is talking to in the current turn.

What we are not asking for

Isolation. In #12283 people ask for separate credentials and execution per user; that's a bigger change and a different trust model. Our team trusts the machine and shares it. What every variant in #12283 needs first, though, is the same thing we need: knowing which person did what. We think that step is valuable on its own.

Happy to help

If the direction makes sense to you, we'd like to contribute it in small, reviewable steps — starting with recording who sent each message, which is additive and changes no permissions. We'll follow your guidance on scope and shape.