A customer workspace needs a reason to exist.

A customer using a software product asks to add a colleague to its workspace. The invitation, the organisation's permission and the colleague's first successful task are separate steps. For a hypothetical product business in Israel, a customer workspace can make that access request easier to follow.

Start with the customer's organisation

The current administrator identifies the organisation and the requested colleague. The product owner supplies the actual edition, account and access rules; a request should not quietly grant a paid feature or wider permission. A person can belong to more than one organisation, so the selected workspace must remain apparent.

The business chooses the languages needed for invitations and setup instructions. A Hebrew-speaking administrator and an English-speaking colleague may require different reviewed messages. The interface should carry the same organisation and requested task through those versions, including any unavailable-language alternative.

Follow an invitation that needs attention

Suppose the administrator corrects the address after an invitation was prepared. Agree which invitation remains valid and how the colleague recognises it. An expired or revoked invitation should explain the next step without exposing another customer's information.

Keep invited, awaiting organisation approval, active and removed access understandable. Opening an invitation is different from establishing an active membership. If someone leaves the customer organisation, removing that relationship should not delete their legitimate access to a different customer.

Try the returning customer task

Acceptance can include adding a colleague, correcting an invitation, selecting the right organisation and removing access. The staff view needs to show unresolved requests without creating another list to retype. Existing identity or customer software may already support the process; we assess that before proposing a custom workspace.

Discovery uses invented accounts. Privacy, account ownership, supported interfaces and recovery are agreed before live use. Discuss a customer access task →