Connect by JBRH Open Connect

Your profile

Your profile in Connect is short by design: the email address Google verified, how you signed in, the workspace you resolved to, your role in it, and the sessions you currently hold. Almost everything people expect to find here — the signature, the tone, what Connect knows about a customer — belongs to the workspace instead, and is edited where it is used.

Status
Available What this means
Audience
both
In the app
#/account, #/mailboxes
Last verified
Product version
6.3.2

What is yours#

Your email address
Comes from Google, verified there. It is the key your Connect user hangs from and it is not edited inside Connect.
How you signed in
Recorded on the session, so the account screen can say what authenticated you rather than assuming.
Your workspace and role
Resolved at sign-in from your membership. Read-only here: it is a consequence of the membership, not a setting.
Your sessions
Every signed-in browser you currently hold, with a device description, when each started and when it was last used.

Everything on that list is a stored row rather than a computed impression, which is why the screen can be short and still be complete. There is nothing behind it that it declines to show you.

What is the workspace's#

ThingBelongs toEdited on
The signature on outgoing mailThe mailboxThe mailbox screen — a signature is a property of the address it is sent from, not of whoever approves the message
How Connect writes and behavesThe workspaceConnect Rules, and the standing instructions beside it
What Connect knows about a customerThe workspace, at four memory tiersThe memory viewer, from the mailbox row, the channel screen or the contact panel
What Connect may send without askingThe workspaceWhat Connect May Do
The plan and its allowancesThe workspacePlan & Usage
Files and recordsThe workspaceTheir own screens; nothing is filed under a person

What is deliberately absent#

  • Two-step verification. Yours lives on your Google account, where you sign in; Connect adding a second, weaker factor of its own would be theatre.
  • A lock screen. There is no in-app lock, and the honest control for stepping away is signing out.
  • Language and region settings. Connect handles multiple languages in conversations without a personal preference deciding it.
  • A team-access panel. Memberships exist as records; granting one is not self-service today, which workspace administration covers in full.

These are absent rather than hidden. A control that appears in an interface and changes nothing is worse than no control at all, because somebody will set it and believe they are protected by it.

Common confusions#

  1. The name on a reply is the mailbox's identity, not your account's. Changing who you are signed in as does not change how mail signs off.
  2. What Connect remembers about a person is workspace memory, editable and forgettable at every tier, and it is not a note attached to your profile.
  3. Your role decides what you may change; the plan decides how much the workspace may do. Neither is stored on the other, and mixing them up produces the wrong screen.
  4. Approvals are recorded against the person who made them, permanently. That record is part of the workspace's audit trail rather than of your profile, and it does not move or vanish if your access does.

Questions#

How do I change my display name or email?

Both come from your Google account. Changing your name at Google is fine — the binding is to the account's stable identifier rather than to the text — but a genuinely different Google account for the same address is a mismatch, which identity binding explains.

Where do I set my email signature?

On the mailbox, not on your profile. Each mailbox carries its own signature along with its role, so a support address and a sales address can sign off differently without anybody having to remember which is which.

Does Connect keep a personal profile of me for the AI to use?

No. What it knows is stored as workspace memory about the business and the people it deals with, readable and erasable at every tier. There is no separate personal model of a signed-in user driving behaviour behind the screen.