When your customers are companies, several of their staff write to the help desk. A client organisation brings them together: on the portal, each person follows their own requests or those of the whole organisation, contact persons follow everything, and sign-in can go through the organisation’s directory. All of this works with or without the CRM. This article is for the help desk administrator and for agents.
Before you start #
- Setting up client organisations: the Administer the help center right (Execute level; Access to read them).
- Only external people belong to a client organisation: those of the portal, incoming e-mail, the widget and the tickets an agent files for them. An employee does not.
- The CRM is not required. The organisations are Illizeo’s organisations: when the CRM is installed, they are the same as its accounts (see The help desk and the CRM).
Adding a client organisation #
- Open Settings › Help center › Client organisations.
- Under Add an organisation, type at least two letters of its name.
- Choose an existing organisation from the list, or click Create “…” to create one.
The organisation’s page opens. In the list, badges show sign-in through the Directory and Joined by domain; Filter by name finds an organisation.
What each contact sees on the portal #

In the On the portal block, choose What each contact sees:
- Each their own tickets (default): each contact only follows the requests they filed. Contact persons always see everything.
- All the organisation’s tickets: each contact follows all the organisation’s requests and can reply to them. Confirming, reopening and rating stay with the person who filed.
E-mail domains #
In E-mail domains, enter the organisation’s domains, separated by commas (for example lumen-optique.ch). A public mailbox (Gmail, Outlook, Bluewin…) is never accepted.
- With Link new requesters from these domains automatically, a person who writes from one of these domains joins the organisation as soon as they file their first request.
- Without this option, the domain is only suggested to the agent, who confirms on the ticket page.
Click Save.
Members and contact persons #

The Members block lists the people linked to the organisation, with their number of tickets and their last visit to the portal. A person linked by their domain, by an agent or through the directory appears there automatically.
- To add a member, enter their E-mail address and, if you wish, their Name (optional).
- Tick Contact person to appoint them straight away, then click Add.
- Appoint contact person and Remove contact person role change a member’s role. A contact person sees and follows all the organisation’s tickets on the portal, whatever the setting; they are told by an e-mail that contains their link to the portal.
- Removing a member (icon at the right of the row) immediately removes their access to the others’ tickets. Their own requests stay theirs.
- A member added from another organisation leaves it. Their open tickets take the new organisation and its contract.
Sign-in through the organisation’s directory #

Without any setting, an external person signs in to the portal with a link received by e-mail. If the organisation has an OpenID Connect directory (Microsoft Entra ID, Google Workspace or another provider), its contacts can also sign in with their work account.
- In the Sign-in through the organisation’s directory block, copy the Redirect address to register with the provider, then register it in the application your customer’s IT team created with their provider.
- Enter the Issuer, the Client ID and the Client secret that this application gave them.
- Turn on Offer sign-in through the directory on the portal, then click Save.
- Only an address from one of the organisation’s domains can sign in this way. The e-mail link always remains available.
- The secret is never shown again: the field says Saved — leave empty to keep it.
- A person who signs in through the directory is linked to the organisation, just as by their domain.
On the portal #
On the portal home page, under Follow my requests, the person enters their address, then chooses Sign in with my organisation’s directory or receives a link by e-mail. Once signed in, they see the name of their organisation, and the words contact person if they are one.

- When they see the organisation’s tickets (full sharing, or contact person), My requests offers Mine and The whole organisation. The list is then titled “Requests of” followed by the organisation’s name, and each row says who filed the request.
- On a colleague’s request, a banner says who filed it: the person can read it and reply. Confirming the resolution, reopening and rating stay with the person who filed.
On the ticket page #

The Requester card shows the person’s organisation and how they were linked (automatically by the domain of their address, through their organisation’s directory, or by an agent). It also flags an Organisation contact person, and says Their colleagues see this ticket on the portal when the organisation shares all its tickets.
- An agent can link the person to an organisation (Search for an organisation), Link to another organisation or Remove the link.
- Without the CRM, this block is called Client organisation. With the CRM, it is called Customer in the CRM and also shows the contact (see The help desk and the CRM).
- Customer contracts (service levels) apply to client organisations, with or without the CRM.
Good to know #
- A ticket keeps the organisation it was filed under. A person who changes organisation does not take their old requests to their new colleagues.
- Remove the settings clears the organisation’s sharing, domains, directory and contact person roles. The organisation, its members and its tickets stay.
- Uninstalling the CRM changes nothing for client organisations or their members’ links.
- Erasing an external person’s data (GDPR) removes their link to the organisation and their contact person role.
- Every setting, every member added or removed and every contact person appointed is recorded in the help desk log.
