EasyManua.ls Logo

Aastra 415 - Authorization Profiles

Aastra 415
270 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Configuration
169
Aastra 415/430 as of R3.2
syd-0344/1.6 – R3.2 – 09.2014
Other predefined user accounts
The predefined user account AMCC is meant for operating an Aastra Mobile Client
Controller.
The two predefined user accounts blustar and bucs are meant for BluStar terminals
and for a BluStar server.
You can see the predefined user accounts in the User account ( =a7) view.
Note:
The predefined user accounts cannot be deleted.
Personal user accounts
Subject to the administration right for user access control, personal user accounts
can be created in user access control ( =a7) and assigned some authorisation pro-
files. The following rules apply to user names selection and spelling:
An user name must consist of a minimum of 1 and a maximum of 25 alphanu-
merical characters.
Unlike the passwords, the user names are not case sensitive.
The following special characters can be used: ?, /, <, >, -, +, *, #, =, full stop,
comma and space.
German umlauts (e.g. ä, ö, ü) and other diacritical characters (e.g. é, à, â) are not
permitted.
User names must be unique throughout the system.
The user name and password must not be identical.
5. 3. 1. 2 Authorization profiles
Predefined authorization profiles
The predefined authorization profiles are assigned administration rights and inter-
face user rights. An overview of all predefined profiles with their administration
and access rights is available in the WebAdmin help on the Authorization pro-
file( =u5) view.
Personal authorisation profiles
Subject to administration right for the administration right for user access control,
no personal authorisation profiles can be protected and assigned the desired

Table of Contents

Other manuals for Aastra 415

Related product manuals