Creating Administrator Accounts
The system creates a First Administrator account. This administrator must sign into the system, create a password, and add other administrators. Until then, no other administrator can have access to the system. As part of the process, the First Administrator (and only the First Administrator) can create an Auditor account, separating the administrator and auditor. This can be done as part of the deployment process or the First Administrator can create an Auditor by using (Auditor Role for more information.) ) to modify the role. (See
Before you begin
A mail server for the system to use to send emails to administrators must be configured. See Configuring an Email (SMTP) Server for instructions.
Procedure
Step 1 |
Enter the first and last names of the administrator. |
Step 2 |
Enter the complete administrator email address and confirm it by entering it again. |
Step 3 |
(Optional) Select Create an auditor account to add an Auditor to the system. |
Step 4 |
Select Next to create the initial password. |
Step 5 |
Enter a password and confirm it by entering it again. |
Step 6 |
Select Submit to sign in to the Webex Site Administration site. |
Step 7 |
Sign into the system and add administrators and users. Upon creation of each new account, the system sends an email to that person, welcoming them and asking that user to sign in and change the initial password. Upon initial sign in, each administrator is offered a tutorial of the system. The administrators can view the tutorial immediately or view it on demand. |
Auditor Role
Auditor Role
The Auditor role is added by using Adding Users.
The Auditor role is a special role created for environments that need to audit sign-ins and configuration changes made by administrators. An auditor can configure log settings and generate Application Audit logs to meet company security and JITC-compliance requirements.
The First Administrator has Auditor privileges by default, and is the only one who can activate the Auditor role for another user. When doing so, the Auditor privileges are taken away from the First Administrator. If an Auditor is also a System Administrator, that person has a System Auditing role.
The Auditor role separates administrative actions from system monitoring as follows:
-
Turn auditing on or off.
-
Configure CWMS to synchronize with the remote syslog servers.
-
Perform log purging.
-
Configure alarms for the log partition.
-
Generate log captures.
-
An Auditor does not have Host privileges and cannot schedule meetings by using the Auditor account. An Auditor can attend meetings as a participant.
-
If the Administrator and Auditor roles are not separated, only the Administrator role exists.
-
If the Administrator and Auditor roles are separated when the system is deployed, a First Administrator role is created (described as the emergency account). After system deployment, only the First Administrator emergency account can create an Auditor. The First Administrator can create as many auditors as desired after the system has been deployed by using the Adding Users procedure..
-
The Auditor is local only; it cannot come from synchronization with any external user base.
-
Auditor parameters (such as the name) can be modified, but once created the Auditor role cannot be deactivated or reassigned to another user ID.
-
An Auditor cannot modify user parameters. An Auditor can only see and configure settings on the Auditor tab.
The Auditor role is a unique role with the following aspects:
![]() Note |
If an Auditor is not configured, all administrators have access to and can configure the Application Audit Log settings on the page and the Log Memory Usage alarm on the page. If an Auditor is configured, administrators can view these pages, but they cannot modify them. |