Skip to content
← Back to blog
Company BrainArticle

Company Brain access after a role change

Suppose an employee moves from procurement to another department. She keeps her company account and assistant conversations but no longer has access to negotiated supplier terms. Later, she opens an old chat and asks it to update a comparison. Does the Company Brain account for her new role when the conversation began before the change?

Author

Syntalith

Published Updated 4 min read

Syntalith can address this situation through a review and further development of your Company Brain. The proposed scope covers an existing application's connection to current employee permissions and its use of earlier conversations and saved work. Together with the information owner, we establish what an employee may still read after changing roles. Your team can see what happens when someone who has left procurement returns to an old chat and agree on any changes needed. The scope depends on the application's features and its ability to connect with company systems.

An old conversation does not preserve old permissions

In this example, the employee previously asked the assistant to compare supplier terms. The answer remains in the conversation history. She now writes in the same thread: "Add the information from the latest negotiations to the table." The new question should be handled according to her current access. If supplier terms are no longer available to her, the application should not retrieve them simply because she previously took part in that conversation.

The content already in the chat matters too. Without opening another document, the assistant could work with the old comparison if it still received that text as material for its answer. A role change therefore calls for decisions about both document access and further use of earlier answers. The employee should understand why she cannot continue the task and whom to contact if her new responsibilities do require that information.

What happens to a saved summary?

A company may need to retain an earlier conversation as a record of completed work while limiting access for the person who changed departments. The information owner determines who may subsequently open and use it. An administrator compares that decision with what the application supports.

A summary may also exist outside the conversation, for example as a document saved in a team workspace. Access then depends on the rules for that location. Include these documents in the review if employees regularly create them with the assistant. Otherwise, restricting the chat can leave the same information available in a folder people use every day.

Revoking application access will not erase a copy previously downloaded to a computer or information the employee has already learned. The company can define further access to content it still controls and make sure new answers use the appropriate information.

Start with the current tool's capabilities

A change does not always require a new assistant. The existing platform may already connect knowledge access to company accounts and offer ways to manage history. Find out how those features fit the rules your company applies when people move between departments.

Microsoft describes Microsoft 365 Copilot as using organizational data the user may access and storing activity that includes prompts, responses, and citations. This does not establish what will happen to every earlier answer in a particular application after a role change.

If the available settings meet the company's needs, the work may be limited to making their use consistent when employees change roles. An integration or application change is worth considering when permissions change in one system but the Company Brain uses different employee information or retains earlier material in a conversation. Understand that connection before commissioning another search feature.

What you can commission from Syntalith

An initial scope can cover a selected role change and the materials that employee used. We examine how people sign in, how the application connects to documents, and where it saves answers.

The person responsible for permissions explains how the company records role changes, while the information owner defines what the employee may continue to use. This lets us discuss which capabilities are already available and where the connection or application needs to change.

Before expanding the work, your team should be able to see how the proposed solution handles a resumed conversation and a saved summary. The review uses a situation the information owner understands, without requiring them to know how a model is built.

For an initial conversation, describe the move between roles and name the assistant you use. Talk with us about Company Brain and which materials should become unavailable when responsibilities change. See Syntalith's pricing page.

Make company knowledge easier to use

Tell us what employees need to find and where the information lives. We will discuss Company Brain’s scope, source access and how it would fit the team’s work.

Explore Company Brain
Discuss Company Brain