WHAT DOES THIS FEATURE SOLVE?
Account Settings gives account admins full control over who has access to the platform and how it is configured for your organisation. From here you can add and manage users, review your contract, tailor the platform's AI features to your organisation, and manage touchpoint colleagues who are not platform users.
HOW TO - STEP BY STEP
Users
Go to Account Settings via menu under your avatar in the top right corner.
You are now on the Users tab. Here you see all current users, their role, and license expiry date.
To add a new user, click + Add user in the top right corner. Fill in the relevant details and confirm.
To edit an existing user, click Edit next to the relevant user. Update details and save.
To deactivate a user, click Deactivate next to the relevant user. The user will lose access to the platform.
Contracts
Click the Contracts tab to view your organisation's contracts with Ulobby. This tab is read-only.
AI Settings
On the AI Settings tab, you can add a description of your organisation in the text field. This description is used across the platform's AI features - for example to determine relevance in document summaries and email digests.
Save your changes.
Touchpoints
Here you can add colleagues who are not platform users but should be recognised when logging touchpoints. This is sometimes referred to as whitelisting.
Add a colleague by entering their name and confirming. They will now be automatically registered on your touchpoints in the same way as users.
Contact us
Click the Contact us tab to find contact details for your account contacts and Ulobby support.
GOOD TO KNOW
Account Settings is only visible to account admins. Regular users do not have access to this page.
The organisation description in AI Settings affects AI features across the entire platform for all users in your account - keep it accurate and up to date for the best results.
Deactivating a user is reversible. Contact Ulobby if you need to reactivate a user.
Colleagues added under Touchpoints are not platform users and cannot log in. They are only available for selection when logging touchpoints.