The display of contact information in Favorites or on the monitor is dependent on what information the user is allowed to see. To be able to control this, authorizations are necessary.
Additionally to the visibility the authorizations defines the availability of contact related functions which are accessible for the user throu the ActiveContacts
Each user can give other users or contact, who are connected to the system via federation, authorizations on the own contact or phone lines. These authorizations are strongly additive to already given adminitrative rights. You cannot remove already given rights.
Authorizations can be awarded through the context menu of the ActiveContacts (in Favorites or monitor), menu point customize authorizations.
Autorizations apply to contact data of the user and to dynamic informations and functions, which are provided by the estos UCServer. The authorizations on the contact have a fixed definition.
If a user adds a contact to his or her Favorites or in the monitor but was not yet granted permission to do so, the newly added contact will receive a corresponding authorization request.
The dialog shows a list with the current authorization inquiries. Every line contains the name and/or the identity of the contact requesting authorization. One or several contacts can be selected from the list.
Below the list is a drop down menu where the authorization level can be selected. The authorizations are applied for the selected contacts via a click on Apply. These contacts are then immediately placed in the first contact group in Favorites on the main window.
It can be determined that selected contacts will receive no presence information with Reject. This corresponds to the authorization level "Blocked". This definition is applied immediately but the contacts do not appear in Favorites.
If a contact who was blocked should later receive authorization, then the users identity has to be added first via "Add contact..." to the Favorites context menu (or monitor).
The allocation of authorizations can also be carried out via the context menu which can be displayed by right clicking on contacts.
Close closes the authorization allocations dialog.The Favorites or the monitor will be able to view and change the authorizations once granted simply by using the context menu under Authorization Level:....
To revoke authorizations from a contact, this is also done in the context menu with the option Blocked. Thereby the contact receives no status updates or other information like names or e-mail addresses.
If a contact from Favorites / monitor is completely deleted, it can be decided whether the contact is set to Blocked. If this is not desired, the authorization level is completely reset so that a new authorization inquiry can start.
The authorizations which can be given to other users are differentiated in 5 levels:
The overview displays by which authorization level what contact data is transmitted to other users:
Information | Blocked | Public | Business | Team | Personal |
---|---|---|---|---|---|
Contact picture | X | X | X | X | |
Display name | X | X | X | X | X |
Job title/position | X | X | X | X | |
Company | X | X | X | X | |
Department (Active Directory® only) | X | X | X | ||
Office | X | X | X | ||
Business address | X | X | X | ||
Work phone | X | X | X | X | |
Business telephone 2 | X | X | X | X | |
Mobile number | X | X | X | X | |
Pager | X | X | X | ||
Private phone | X | ||||
additional phone numbers (Active Directory® only) | X | ||||
Business fax number | X | X | X | ||
E-mail address | X | X | X | X | X |
SIP address | X | X | X | X | |
SharePoint/Webseite | X | X | X |
The permission levels restrict only the contact data exchanged via presence information, i.e. primarily presence information transmitted via Federation. The permission level does not affect the contact search. Contact data, such as the mobile phone number, is still visible via a contact search, regardless of the permission levels. | |
X* In these authorization levels the notice will only be transmitted unrestricted within the users of UCServer. Contacts via Federation receive the notice only if at least the authorization level Team member is allowed in the domain authorizations. |
In estos UCServer further information and functions are available to give authorizations to a contact.
The following definition is valid for standard authorization levels:
Authorization | Description | Blocked | Public | Business | Team | Personal | |
---|---|---|---|---|---|---|---|
View contact picture | A contact image stored for the user is visible | X | X | X | X | See presence | The other user is allowed to see the presence (Present, Absent...). | X | X | X | X |
Set presence | The other user is allowed to change the presence. This right should be set only in the case of special positions of trust. |
X | X | ||||
See note | The other user is allowed to see the note. | X | X | X | X | ||
Set note | The other user may enter a note. | X | X | ||||
See private appointments | The other user is allowed to see the appointments marked as private from the calendar, if the user has released his appointments. This right should be set only in the case of special positions of trust. |
x with the note "Private" |
x with the note "Private" |
X with subject and place |
|||
See public appointments | The other user is allowed to see the appointments marked as public from the calendar, if the user has released his appointments. | X | X | X | |||
Phone: | |||||||
See existing phone numbers | The phone numbers assigned to the user (phone number/extension of all lines) are displayed when the mouse pointer is moved to the presence display. | X* | X* | X | X | ||
See line status (free/busy) | The other user can see if the phone line is free or busy | X* | X | X | |||
First line (Business 1) | See outgoing numbers | The other user is allowed to see who the user is calling with his primary phone. This right should be set only in the case of special positions of trust. |
X* | X | X | ||
See incoming phone numbers | The other user is allowed to see who the user is currently being called by on their primary phone. | X* | X | X | |||
See diversions | The other user is allowed to see that call forwarding is enabled on the phone. | X* | X* | X | X | ||
See the number of a set call forwarding | The other user may see to which destination number call forwarding is activated on the phone. This right should be set only in the case of special positions of trust. |
X* | X | X | |||
set Call forwarding | The other user is allowed to set up call forwarding on the line. | X | |||||
Pickup call | The other user is allowed to pick up incoming calls on the first line. | X | X | ||||
Second line (Business 2) | See outgoing numbers | The other user is allowed to see with which caller the user is calling with his second phone. This right should be set only in the case of special positions of trust. |
X | X | |||
See incoming phone numbers | The other user is allowed to see who the user with his second phone is currently being called by. | X | X | ||||
See diversions | The other user is allowed to see that call forwarding is enabled on the phone. | X* | X* | X | X | ||
See the number of a set call forwarding | The other user may see to which destination number call forwarding is activated on the phone. This right should be set only in the case of special positions of trust. |
X | X | ||||
set Call forwarding | The other user is allowed to set up call forwarding on the line. | X | |||||
Pickup call | The other user is allowed to pick up incoming calls on the second line. | X | |||||
additional lines | See outgoing numbers | The other user is allowed to see which dialog partner the user is calling. This right should be set only in the case of special positions of trust. |
X | X | |||
See incoming phone numbers | The other user is allowed to see who the user is being called by. | X | X | ||||
See diversions | The other user is allowed to see that call forwarding is enabled on the phone. | X* | X* | X | X | ||
See the number of a set call forwarding | The other user may see to which destination number call forwarding is activated on the phone. This right should be set only in the case of special positions of trust. |
X | X | ||||
set Call forwarding | The other user is allowed to set up call forwarding on the line. | ||||||
Pickup call | The other user is allowed to pick up incoming calls. | ||||||
Audio/Video: | |||||||
See line status (free/busy) | The other user can see if the AV line is free or busy | X* when busy, the AV icon is grayed out |
X when busy, the AV icon is grayed out |
X when busy, the AV icon turns red |
X when busy, the AV icon turns red |
||
see Conversation participants | The other user can see who is being talked to about AV. | X | X |
(*) These authorizations only apply within the estos UCServer service responsible for the user. Federation contacts or contacts from other estos UCServer services will not see this data! |
The administrator is able to allocate authorization levels or single authorizations. In this case, the administratively pre-set authorization levels cannot be minimized anymore. This means that the lowest authorization level "Blocked" cannot be selected anymore for the contacts concerned. This is because the lowest authorization level allocated by the administrator always applies.
If single authorizations are administratively given instead of authorization levels, the authorization level can only be changed by the administrator. | |
For contacts already authorized by administration settings there will be no authorization inquiry dialog. |
Version 8.1