Give every workspace a clear information boundary

An organization-managed account represents the connection, credentials and canonical collected information. Administrators explicitly grant people access to that source. Several authorized users can work over the same source without creating separate copies of its synchronization history. The account remains a source boundary, rather than becoming whichever user's chat most recently opened a mail.

Those operational grants answer questions such as who may read or administer the account. They do not answer which private notes, assistant conversations or analysis a person may inspect. A shared account should not turn an administrator into an automatic reader of every private workspace. Personally added accounts also require their own ownership and sharing rules; they are not silently converted into organization-wide sources just because they are connected to the same installation.

A personal workspace holds the context in which a user and explicitly delegated assistants work. Notes, preferences, classification choices and private analysis can remain separate from other people's treatment of the same mail. A personal mail record can carry notes and a work state without becoming a discussion thread. Privacy is an ownership boundary, not simply a count of how many readers happen to be present.

A private workspace can also host collaboration among several of that user's authorized assistants. Their discussion is still collaboration, even though it is not shared with colleagues. Each assistant retains its own work, focus and reading state. Having only one current reader does not turn an existing discussion into a personal record or authorize copying its comments into personal notes.

A user can organize work into spaces for a project, a work area or an AI assistant. Each space receives explicit account capabilities within the user's current source rights. A project assistant can be limited to the information and context needed for that project rather than inheriting everything its owner can read. A second assistant can have a different role without changing the original source.

The application's authority matters too. A connection is bound to the represented user, workspace and application, rather than trusting a workspace name supplied in a prompt. Display filters can narrow what appears on screen but cannot widen access. For calendars, a project view likewise must stay within its permitted sources; an incomplete collection indicates unknown availability rather than proving that someone is free.

A metadata collection is an organized set of annotations or working context attached to information. Same-user sharing can target selected workspaces owned by that user. It is useful when two work areas need a common vocabulary or selected notes while retaining separate private work. Choose the material the spaces will use together and keep their other histories, dictionaries and derived decisions under their existing ownership.

Content sharing and source authority remain separate checks. Each receiving workspace uses its current rights to open the underlying mail. A structured source reference or a published excerpt needs the appropriate source and disclosure authority as well as a permitted destination. Together, these checks let useful context travel along an intentional route while keeping the company source and private conversations within their respective audiences.

A team discussion should be an explicit shared context over the relevant mail or topic, alongside existing private conversations. Enabling it does not widen old private threads in place. Selected earlier material can be published only with the right authority and audience. General comments follow that shared context's permitted readers, while an author can choose a narrower audience within the allowed boundary.

An independent topic has its own participants, and each linked mail still has its own source rights. This supports collaboration when one colleague can discuss the decision but cannot inspect every original. Unreadable comments remain hidden. The topic's limited notice that inaccessible linked material exists must not become a hidden-mail list, a preview or a grant of access.

Mail-body summaries can be shared among the same user's assistants and workspaces, subject to current account rights at each access. Organization-managed accounts can also have organization-owned embeddings so the same mailbox need not be embedded by every person. Those are preparation choices. Personal spam or classification judgments can still differ, and neither summary nor embedding reuse merges work status, discussion or another user's private analysis.

Reading evidence has a different boundary. The same verified assistant may reuse eligible knowledge of the exact canonical body without pretending it fetched the body again. Another assistant does not inherit that reading simply because it sees the same summary or works for the same person. Reuse also creates no local participation and does not satisfy an outstanding recheck by itself. Similar text across separate mail occurrences is not a universal permission to share computation or state.

Rights change when people leave a project, an application is disconnected, a workspace is retired or an account grant is withdrawn. Current access follows the workflow through listing and retrieving information, continuing a paginated search, delivering events and applying delayed work. Rechecking it keeps earlier cursors, cached results and queued analysis within today's authorized scope. Regranting access is a fresh choice, with retired private audiences kept separate.

Retained records also need a deliberate policy. Removing a source or purging an original leaves an explicit choice about authorized discussion and classified work records. A retained decision has its own scope rather than carrying permission to preserve every source byte. When setting up a workspace, choose its purpose, source grants, assistant delegation, shared audience and retention responsibilities together so future changes have a clear boundary.