This is an in depth explanation of what the platform considers to be a "User".
A 'User' is a feature that is essentially a selection of smaller features wrapped up together into a singular entity. A User is how you setup devices and access to the platform.
If you want to know how to create your own Users, see How do I configure a user?
Take the below examples:
- A person named "John Smith", he has: 3 phones, a SIP desk phone, a mobile soft client, a Web RTC client, a voicemail inbox that sends his voicemails to his work email, custom routing rules set up that make it so that his phones don't ring when he finishes work, as well as time based configurations that forward calls to his colleagues when he's on annual leave.
- A cordless phone sat on the reception desk of a hair salon, set to ring during the day and divert to the owner's mobile number after hours.
- A voicemail inbox called "Out Of Hours Voicemail" where all voicemails for the business get forwarded to after hours and then redistributed to a shared email inbox.
All of the above are examples of how you might setup a user.
Features
All users have bundled in the below features:
- A user profile
- Voicemail Inbox
- Answering Rules
- Multiple Devices/SIP Accounts
- Online Portal Account
- Web App and Mobile App Accounts
- Presence
System Users
Probably one of the most complex yet important parts of the platform is the concept of how everything is a user. As an administrator you have access to create your own users, usually for individuals or devices to use, however the platform itself creates what is called a "System User" whenever you create nearly any kind of other object in the platform.
IMPORTANT: System Users are not billable.
The below features will create a system user whenever you create the feature:
- Auto Attendants
- Queues
- Ring Groups
- Conferences
- Time of Day DDIs
- Sites
To view any system users, from the "Users" tab under the domain view you can untick "Hide System Users" at the bottom.
From here any system users you have will become visible with a grey tag next to the name indicating what type of feature it is attached to.
WARNING: We highly advise against deleting system users from the user tab, if you have a feature that uses a system user that needs to be deleted, delete the feature from it's own tab and it will automatically wipe the system user for you.
Deleting the system user from the user tab will not delete the feature itself and instead just leave it inoperable as it requires the system user to function.