Open a Support Case My Support Cases
Welcome
Login

4.C Creating CoreView Operators

You create a CoreView Operator in the same manner as you created a TenantAdmin, following the instructions found in 4.B Create CoreView Tenant Administrators.  However, the difference between the two is that generally, an organization doesn't create Operators unless they plan to implement some form a delegation.  


I.  Definition of an Operator

An Operator is anyone in your organization who has a need to log in to CoreView, regardless of the reason.  Te identity of an Operator is sourced from among your active Office 365 account.  This is know by CoreView as an Organizational Account.  You do have the ability to create an Operator account for someone who does not have an Organizational Account, but this is not viewed as a best practice.


An Operator's activities are logged into an Audit Log to which any TenantAdmin has access.  Moreover, through Manage Operators, a Tenant Admin can see an inventory of all Operators and access the details of their operator account.  Please review the video below for a quick tutorial on Operators and delegation of access and control.


II.  Operator Use Cases

Below are a handful of examples of when a CoreView Operator account might be assigned to someone in your organizations.  


Office 365 AdministratorsCreating Operators as TenantAdmins is a common practice to allow full management of Office 365.
Help Desk StaffHelp Desk staff may benefit from access to CoreView for a variety of reasons.
Delegated Exchange AdministratorsIf your organization's IT services are delegated, you may chose to delegate access to CoreView's exchange management capabilities.
Legal StaffYou may provide members of your legal department access to CoreView to allow them to place or, or remove accounts from, legal hold.
CIO/CTOYour CIO or CTO may desire access to CoreView to view the executive-level dashboards, license optimization or chargeback reports.

III.  Dependencies

Any implementation of an Operator account would typically depend other aspects of your CoreView configuration.  Your implementation of Operators depends on your looking at the whole of CoreView and how you want to take advantage of CoreView's power to achieve your organization's business goals.


Therefore, you may need to defer the creation of Operators, until other configurations upon which an Operator may relay, such as:

  • Virtual Tenants - Virtual Tenants allow you to segment your business data and then restricting an Operator's span of control to only a a particular set of business data.
  • Permissions - The creation of role-based access controls (permissions) is essential to ensure that any Operator has the appropriate access to perform the activities required of them.  
  • License Pools - An Operator's access to license pools allows them to manage the assignment or recovery of licenses, but only within the scope defined by the organization.

IV.  Creating Operator Accounts

Operator accounts are created in the same manner as that found in the Knowledge Resource titled 4.B Create CoreView Tenant Administrators.  Below, please find a short video that walks you through the steps to delegate access to a Help Desk.  This this video refers to an older version of CoreView, the information and concepts are still relevant.


---

Published: 02/25/2019

Updated: 02/25/2019

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.