Documentation / Account and organisations
Account and organisation: what belongs where
In short: The account is your whole company in aishaa. An organisation is one brand, webshop or business unit within that account, with its own channels and its own tickets. Some settings apply to the whole account, others only to one organisation. If your account has only one organisation, you will hardly notice this distinction.
Where to find this
Account-wide settings are in the navigation menu under the Account group: Account > Account settings and Account > Users. Settings per organisation are under the Organisation group, divided over the sections Channels, Organisation (with General and Business hours), Intelligence and Topics. For an account with multiple organisations, the name of the active organisation appears in the title of the Organisation group.
For an account with multiple organisations, you see at the top of every settings page which level it applies to: the All organisations (account-wide) chip on an account page, or a chip with the name of the organisation on an organisation page. You also use that organisation chip to switch organisations.
Who: the Account admin manages account-wide settings. The Organisation admin of an organisation manages that organisation’s settings.
The navigation menu with the two groups Account and Organisation expanded, for an account with multiple organisations, so the name of the active organisation is visible in the group title.
The two levels
An account always has at least one organisation. Users belong to the account and are given access to one or more organisations. Each organisation has its own channels (mailboxes, WhatsApp numbers, phone numbers) and therefore its own tickets and conversations.
This is how it works in practice:
- When you work in aishaa, you always work in one active organisation. The tickets, channels and AI settings you see belong to that organisation.
- Settings at account level automatically apply to all organisations. You set them up once.
- An organisation can override a few account settings for itself: the way of working, the opening hours and, per channel, the writing style. For the way of working and the opening hours this is all or nothing per organisation.
What belongs to the account
| Item | Explanation |
|---|---|
| Users and roles | One user base for the whole account. For each user you decide which organisations they can access. See Manage users. |
| Contacts | Customers and contact persons are account-wide. See The contact overview. |
| Cases | Customer cases and case templates (only with the Cases feature). |
| Labels | Labels and sublabels on tickets. |
| External parties | Addresses of suppliers and other third parties. |
| Incoming email rules | Rules for incoming email. |
| Allowed senders and spam filter | The spam threshold and the list of allowed senders. |
| Ticket actions | The catalogue of follow-up actions (only with the Ticket actions feature). |
| WhatsApp templates | Approved WhatsApp templates. |
| Customer groups | Groups of customers with their own rules, such as no AI analysis or never as spam. See Customer groups. |
| Agents, skills and library | The AI agents and their skills apply to the whole account. An Organisation admin can see them; only an Account admin creates, changes or installs them. |
| Workflows | A workflow created by an Account admin applies to the whole account (Whole account). A workflow created by anyone else applies to the active organisation. See What are workflows. |
| Notices | Short facts that apply for a while. A notice applies to all organisations or to the organisations you choose. See Notices. |
| Features | Cases, Telephony, Ticket actions and Extra signatures. See Features per account. |
| Account logo | The primary logo. It stays the same when you switch organisations. |
| Default ticket tabs | The default layout of the tabs on a ticket for everyone in the account. |
| To do | After how many days a proposal nobody decided on disappears from To do. See To do. |
| Customer data from connected systems | Whether aishaa automatically merges customers based on data from connected systems. |
| Way of working | Automatic closing, reopen windows, the reply-needed ladder, the quiet window and the inbox counter. See Way of working: webshop or service provider. |
| Policy | Redaction of sensitive numbers and transcription of WhatsApp voice messages. See Policy: sensitive data and voice transcription. |
| How many minutes aishaa waits after the last WhatsApp message before it reads the conversation, and the read receipt. | |
| Telephony routing | Who rings when a customer calls (only with the Telephony feature). |
| Ticket and case numbers | Numbering continues across all organisations in the account. |
What belongs to the organisation
| Item | Explanation |
|---|---|
| Channels | Mailboxes, WhatsApp numbers and phone numbers. Each organisation also has its own aishaa Mail address. |
| Tickets and conversations | A ticket always belongs to exactly one organisation. |
| Organisation logo | Small logo on tickets and in the organisation switcher (only visible with multiple organisations). |
| Name, email, phone | The contact details of the organisation. |
| Language and time zone | The default language and the time zone of the organisation. |
| Domain profile | The type of business (for example E-commerce or Mortgages). |
| View library | Views you use in tickets. |
| Shipping method and webshop connection | The carrier and the connected webshop plugin. |
| Intelligence | Organisation information, changes, writing style per channel (its own style or the account’s), AI knowledge base and macros. |
| Topics | What aishaa knows, the organisation’s topics and the support groups. |
| Sending by itself | Per agent and topic, a person can turn on Let it send by itself; the Emergency stop puts all of the organisation’s replies back to proposals in one click. See Trust and letting an agent send by itself. |
| Customer satisfaction and review email | Whether aishaa records satisfaction and prepares review emails. |
| Signature for automatic messages | The signature under messages that go out without a human sender, such as a reply an agent may send by itself or a message a workflow sends directly. |
| Opening hours | By default the organisation follows the opening hours of the account. An organisation can choose its own opening hours. See Opening hours. |
| Own way of working | Optional: an organisation can deviate from the account’s way of working. |
What can exist at both levels
You create macros, knowledge documents and knowledge tags item by item as Shared across account or Only this organisation. Shared items are available in every organisation. Classification rules, automatic acknowledgements of receipt and triage rules no longer exist as separate settings; you now do that with workflows. Only an Account admin can edit shared items; an Organisation admin sees them as read-only and by default creates new items for their own organisation.
Good to know
- If your account has one organisation, you will not see an organisation switcher, a scope chip on settings pages or an organisation logo. The distinction is then deliberately invisible. The Account settings page does still exist.
- An Account admin automatically has access to all organisations in the account, including organisations added later.
- You cannot add an extra organisation or archive an organisation yourself. Contact the aishaa team via the aishaa support chat in aishaa (menu Chat, conversation aishaa support) or via support@aishaa.nl.
- There is no page in aishaa for invoices, subscription or usage. Invoicing is handled outside the application.
