Skip to content
Interface language: English
Design / Signal

Two company accounts, one user: which company are you working in?

Design organisation switching around the active company, draft ownership, two browser tabs and links that return people to the right project.

Article language: English

Aeneia world concept: a designer tests movable wall modules and benches on open terraces overlooking the water.
In this article

Olga works with two clients in the same portal. Both have a project called “Autumn Stand”, both are waiting for a quote, and both like a reply before noon. Olga opens two tabs. After a phone call, she returns to the first one and adds a discount. The button works and the form is valid. The company is wrong. The system has carried out the instruction perfectly. Unfortunately, it was not the instruction Olga meant to give.

This is a fictional design scenario with a very specific task: one person needs to know which organisation they are acting for at any moment. A list of companies under an avatar is only part of it. The context must survive opening a link from a message, using a second tab, saving a draft and taking a coffee break. A name in the header helps the person. The system's backend must independently enforce data isolation and access rights.

Our two fictional clients are Brzeg and Półka. Olga has access to both, but each has its own projects and contacts. We are not making one shared bag of records with two coloured labels. We are designing a move between separate workspaces so that an otherwise correct action does not reach the wrong recipient.

First decide what actually changes

In one product, choosing a company changes all the projects, contacts and settings. In another, it affects only a report on the current page. The two behaviours may use similar dropdown menus, but people expect different consequences. If the orders list still shows the previous company after the header changes, the user needs to understand whether that is the intended scope or a transition still in progress.

PatternFly distinguishes a context selector from a filter: a filter narrows a set, while a context selector changes it to a different set. The guide also distinguishes an effect across the application, within navigation or on a single page.

For Olga's portal, we choose the application-wide model: Brzeg and Półka are separate workspaces. Choosing Półka changes where she works; it does not merely hide some of Brzeg's rows. That choice puts the switcher close to the main navigation and keeps the company name visible after the menu closes. List filters can remain lower down, beside the results they affect.

Sort out the names of things before drawing screens. Does “company” mean a client, a branch, the entity issuing a document or an internal team? Two entries called “Head office” with no further detail are a poor choice even in a beautiful menu. A short distinguishing detail can help: the legal name, a city or an agreed account label. Choose something the user actually recognises instead of displaying an unexplained technical identifier.

This is part of the portal's information architecture, and it affects every action. The map should show what belongs to an organisation, what belongs to a person and what remains shared. Olga's language preference may travel with her. That should not turn Brzeg's employee list into Półka's employee list. The article on information architecture for a B2B website (in Polish) examines a public B2B site.

Bring the company name to the point of decision

A persistent name in the header is a good start. In a long form, though, it may scroll out of sight; on a phone it may be shortened to two letters. At an action with a significant consequence, name the recipient again: “Send quote for Brzeg” or “Save in Brzeg's project”. The full name does not need to appear beside every field. It needs to be available where the recipient could be confused.

Colour is a supporting cue. Olga should not have to remember that green means one client and teal another, especially as the list of companies grows and teal starts negotiating with turquoise. A logo can also be unfamiliar to a new colleague. A text name and a clear project title should work without knowledge of corporate heraldry.

The browser tab title can include the company and the task. Olga can then distinguish two open quotes before switching windows. Within the portal, the order should remain consistent: company, place in its structure, item. Do not suddenly turn an organisation's name into a team name in settings if the user has not made that change.

The company list may show a role when it helps people anticipate which tasks are available. Olga might prepare quotes for Brzeg but only view them for Półka. A label such as “Administrator” without the organisation could suggest broader access than she actually has. Favourites make a frequently used company easier to select, but they should not remove the route to the others. A new invitation must still be findable before it has been added to favourites.

The switcher also needs to handle long and similar names. “Studio...” does not settle much when there are ten studios. Prepare realistic examples of name length, not only “Company A”. Search can help someone with many accounts, but the results still need to distinguish two organisations with similar names.

A draft belongs somewhere, even before it is sent

Olga starts a quote for Brzeg and chooses Półka before saving it. The interface has to decide what happens to the work in progress. It could keep the draft in Brzeg, ask for a decision before she leaves, or block the transition while a specific operation completes. The choice depends on the product. Accidentally moving the filled fields into Półka is not a convenient shortcut.

If the draft saves automatically, the message should connect the save with its location: “Draft saved in Brzeg”. “Saved” alone does not say where Olga will find it later. When she returns, she should find the same project, with its data intact and its organisation recognisable. She should not have to reconstruct the sequence of switches from memory as if solving a mystery from her own Wednesday.

A product without automatic saving might ask: “You have unsaved changes in Brzeg. Save them before switching to Półka?” The buttons must match the real choices: save and switch, discard changes, or stay. If saving fails, do not present Półka's workspace as ready with a green success message. Show what actually happened and a way to preserve the work.

Aeneia conceptual photography

If the portal lets a user return to a saved form, the draft list should identify the company too. A global “My drafts” list may bring Olga's tasks together, but each row needs its own recipient. Opening an item should restore its context rather than assign the draft to whichever company is currently named in the header. The guide to returning to a saved form (in Polish) examines saving and resuming a draft.

Not every context switch needs another dialog. During a quiet review of a list, a deliberate choice of the new company and a clear result may be enough. A warning should address a risk of losing a draft or another specific consequence. Asking for confirmation on every switch quickly teaches people to press the button without reading it.

Understanding WCAG 3.2.2 concerns predictable effects when the setting of a control changes. If that change automatically causes a change of context as defined by the criterion, the user should be advised beforehand. W3C distinguishes activating a link from changing a setting. For a button, it gives toggling its state or becoming disabled after activation as examples of changing a setting. Submitting a form and navigating to a new page is an example of activating a control. A state change does not necessarily change the context. The criterion does not require a separate confirmation for every company switch.

Describe what the control actually does. Does selecting an item immediately move the user to the organisation, or does a “Go” button start the change? Where does focus go after the transition? Where does a failed save appear? These answers are more useful than a single general requirement that “the switcher must be accessible”.

Two tabs should not negotiate the company behind Olga's back

Olga views Brzeg in one tab and Półka in another. That is a natural way to compare tasks. The design needs to decide whether each tab keeps its own context or an organisation change applies to every open view. There is no single answer for every system. One result is clearly wrong: the first tab's header says Brzeg, but the save goes to Półka, selected moments earlier in the second tab.

If context belongs to the tab, returning to the first one should keep Brzeg. If the product requires one active organisation, the old view must respond honestly to the change: refresh, ask the user to move, or stop the action and explain why. Remembering a choice under an avatar does not by itself describe what happens to open forms.

This is different from simultaneous editing of one record. There, two people or tabs may compete over a version of a quote. Here, the correct version may be assigned to the wrong organisation. Both tests are needed, with separate expected results. A separate article on simultaneous editing conflicts (in Polish) explains how to preserve competing changes.

Similarly, when handing a step from a computer to a phone, the recognisable company needs to travel with the specific task. A successful sign-in on the second device does not mean the project from which the handoff began has opened. Olga should be able to confirm the recipient before adding a photo to the quote. The guide to handing a step from a computer to a phone (in Polish) follows the handoff and its result.

A switch can also get stuck halfway. Olga chooses Półka, but no response arrives. The header should not announce a successful change while Brzeg's projects remain on screen. Design a waiting state and an error that makes it clear whether she is still in Brzeg or needs to open Półka again. The company label and displayed data must refer to the same stage of the transition.

When the new workspace is empty, name it in the message: “Półka has no projects yet”. A generic “You have no projects” could suggest that Brzeg's work has disappeared too. If creating a project requires a different role, show the appropriate next step rather than a non-functioning add button. An empty view should confirm where Olga has arrived.

A message's destination takes precedence over a guess

In the morning Olga opens the portal from a bookmark. In the afternoon she follows a message about Półka. These entries carry different amounts of information. A bookmark may lead to a chosen starting workspace or a company selector. A link to a specific project, however, should preserve that destination even when sign-in is required along the way.

Azure portal settings distinguish the current organisational directory from the startup directory. For startup, a person can choose the last visited directory or a specific one. It is an example of separate decisions about present work and the next entry.

In our portal, a message pointing to Półka should not open a Brzeg project merely because Brzeg was used most recently. If Olga no longer has access to the destination, the screen should say that she cannot open the requested item. Silently returning her to a similarly named project belonging to the other company is particularly misleading: everything appears to have worked.

Accepting an invitation adds the question of the person's account. Choosing an organisation is not automatically a change of user identity. Show who is accepting the invitation and which company the link leads to. Do not merge two accounts simply because their owner recognises both addresses. Account identity and invitation status are covered in the article on accepting a collaboration invitation (in Polish).

Returning after a break is part of switching

For acceptance, prepare two companies with similarly named projects but clearly different test data. Ask a person to start a quote in the first, look at the second and return to the draft. Observe how they recognise their workspace. If they have to reopen the menu every time, the persistent indication is too weak.

Next, leave one tab open for a longer period and change the account's access in an agreed test environment. On return, the user should be able to understand the state without seeing data they can no longer access. Technical acceptance must verify that the operation is actually denied; a mockup only confirms the intended message and next step. One piece of evidence does not replace the other.

You can discuss the feature, user needs and the possible scope of work with Aeneia Design. Good documentation also answers Olga's ordinary question after a phone call: “Am I still writing to Brzeg?” If she can see the answer before sending the quote and the save result confirms it, the switcher has done its job.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear