Organisations, users, and permissions
Structure organisations, invite users, assign roles, and manage direct access.
Understanding the hierarchy
All organisations belong to the platform hierarchy. A reseller organisation can manage child organisations within its quota limits. Creating a new root organisation is not supported.
Create a user
From Users or an organisation's details page:
- select Create a user;
- enter their details and email address;
- assign only the necessary roles and set the initial password;
- optionally add tags;
- open Profile preferences to customise the picture, language, or time zone.
When user creation begins from an organisation’s details page, cancelling or completing the process returns to that organisation.
For an existing user, Change the password brings together the two update fields. Leave them blank to keep the current password.
Finding organisation options
Identity, parent organisation, direct access, and billing details remain directly accessible. Appearance and language groups visual preferences; Reseller options and limits contains quotas and options reserved for authorised administrators. Detailed pricing is available under Prices excl. VAT, and alert settings under Alert threshold and recipients. The balance and credit actions remain visible.
Under visual customisation, the domain, support, main logo, and previews remain visible. Open Colors, Icon and dark theme logo, or White label and sign-in to fine-tune the settings you have access to. Closing these panels alters neither the values nor the permissions.
In Application background, select a pattern and then check the light and dark previews before saving. Each background covers the screen with a large continuous design, without small tiling seams; its colours adapt to your branding and theme. Plain keeps a solid background.
For your own visual styling, add a Custom background image in PNG, JPEG, or WebP format, up to 10 MiB. The image cannot exceed 8192 pixels per side or 8 388 608 pixels in total; resize larger photos before uploading. The local preview selects Custom image and displays the light and dark result without uploading the file. The background covers the screen: its edges may be cropped. Dark mode dims the image to preserve readability.
Click the single Save button in the top right to apply your changes. The floating banner appears after any change, including selecting a file. A new upload replaces the previous image and activates the custom background. You can then select an existing pattern and save to keep the image without displaying it. To delete it, tick Remove the current background image and then save; if the custom background was active, Contours replaces it. A rejected file displays an error and preserves other inputs as well as previous files; reselect files after a form error if the browser cleared them.
These settings remain restricted to authorised administrators of the relevant organisation and platform administrators. The image is uploaded locally; no external URL is accepted. The same permissions, formats, and limits apply to the public visual customisation API.
Roles and scope
Roles determine permitted actions. The home organisation determines the standard scope. A platform administrator can also add a user to Direct access for another organisation without altering their primary assignment.
Tags
Start typing a tag. Existing tags are suggested immediately. If the label does not exist, a Create tag action appears after a brief pause; Enter remains available to create it immediately when your permissions allow.
Quotas
Quotas for bots and child organisations can be configured by authorised administrators. A value of 0 means that no specific limit is applied. When the quota is reached, creation flows are disabled in the portal and rejected identically by the API.
Identifying web subscriptions
In the Organisations list and within organisation details, the globe icon indicates its web subscription. Its tooltip specifies the assigned plan and its status: active (green), awaiting first payment (orange), suspended (red), or terminated (grey). Without a subscription, the tooltip displays No web subscription. The existing calendar remains reserved for credit subscriptions.
Use the Web subscription filter to display all organisations, those with or without a subscription, or a specific status. With a web subscription also includes pending, suspended, and terminated contracts; select Active to view only active contracts. The filter combines with search and other filters, and the reset button clears it. It respects your visibility scope; a reseller cannot access Beone direct clients.
The API provides the same filter: GET /api/v1/organisations?website_subscription=active. Accepted values: any, none, pending, active, suspended, ended. Omit the parameter to display everything. The website_subscription field is null without a contract; otherwise, it contains notably status and the plan's terms. An unknown filter value is rejected (HTTP 400).
Using lists
The lists for organisations, users, and visual customisation share the same layout. Search and result counts are on the left of the table bar; row count, actions, and column selection are on the right on large screens and rearrange on mobile. Common filters remain visible. Advanced filters provides access to additional criteria without clearing selections when closed.
In Organisations, Active is the initial selection for the archive filter; it does not count as an added advanced filter. Archived and All remain available. The Create a user and New organisation labels clarify the creation action. The base role is displayed as User; this label grants no additional permissions. Organisation roles retain their labels and scope.
Archive an organisation and its resources
Only platform administrators can archive an organisation. In Organisations, choose Archive, optionally enter a reason and confirm. This also archives descendant organisations, their bots and users whose primary organisation is affected. Users of an active organisation keep their account when they only had direct access to the archived client.
Affected bots and users disappear from working lists in both the portal and API. Accounts are locked, existing sessions and API keys become unusable, and SIP registrations are removed from all call servers. Allocated BeAI numbers are released and stop renewing. Personal SIP numbers are not cancelled with their operator. Conversation, invoice and credit history is retained. The platform root and your own organisation cannot be archived. Website subscription contracts must be ended first.
Optional, irreversible anonymisation only clears the selected organisation’s identity and billing details. It does not anonymise descendants. Archiving alone retains these details.
If a call server is unavailable, the archive remains saved and a warning identifies pending telephony cleanup. A platform administrator can retry it. A number remains reserved until all call servers acknowledge its release.
Restore only makes the selected organisation visible. Descendants remain archived; accounts must be unlocked and SIP connections reactivated explicitly. Released numbers are not automatically recovered. Existing history links remain available subject to permissions.
API equivalent: POST /api/v1/organisations/{id}/archive, for example with {"reason":"Fin de contrat","anonymize":false}. meta.archive reports organisation, bot and user counts, complete, pending_bot_ids and pending_lease_ids. complete: false means cleanup needs retrying, not that archival was cancelled. The root, your own organisation and non-ended subscriptions return HTTP 409; a reason longer than 255 characters returns HTTP 400. Restore uses POST /api/v1/organisations/{id}/unarchive. Bot and user detail responses expose archived without extending read permissions.
Use Retry telephony cleanup on the archived organisation to retry pending unregistration and number release. Restore the parent before restoring a descendant.
Change history
From an organisation record or a user edit page, open Change history. Authorised administrators can review creations, changes and deletions within their scope, including the date, actor, source (interface, API, connected assistant or system), and before/after values. Impersonated actions distinguish the real actor from the account used.
Filter by actor, source, operation and date range. Dates are displayed in Brussels time; API bounds use ISO 8601 with a timezone, including the start and excluding the end. Subsequent pages retain the same results snapshot.
Events are retained for two years. Collection starts on the date shown: only previously recorded pricing changes can be imported, with their provenance. Unknown history is never reconstructed. Passwords, keys and tokens remain masked. Credit consumption and login counters are excluded. Permissions are checked on every read; only platform administrators can view records for deleted resources.
GET /api/v1/users/{id}/audit-logs · GET /api/v1/organisations/{id}/audit-logs