Administrators and managers: configuring your Client Portal
SECURITY Client Portal Manager, Taskfire Resource, or Taskfire Administrator to create and manage users. Taskfire Administrator for all other configuration settings
Configuration tasks for standard Client Portal Managers
If your organization Your Client Portal instance may be configured to use one fo the following terms instead: Account, Business Unit, Client, Company, Customer, Site. will not be using the Taskfire An extension of the Client Portal that lets you manage your own internal help desk. internal help desk, you will only need to make sure that the people in your organization who will be accessing Client Portal A branded web portal through which you and your service providers can collaborate on tickets and projects. have a user account with the right security level and configure your Quick Ticket The Autotask entity that tracks service requests, incidents or problems that were added to Autotask by your customers, internal employees, or remote monitoring software. settings.
Refer to Managing Client Portal users and Enabling and configuring Quick Ticket settings.
Configuration tasks for Taskfire Administrators
If you will be managing your internal help desk using Taskfire, you will need to configure the Client Portal to support the shared ticket workflow that we have agreed upon. You will also need to let us know which users will be assigned Taskfire security levels and who will be the Taskfire Administrator who will configure the Client Portal for Taskfire.
NOTE You cannot assign Taskfire security levels yourself. You must contact us to assign them for you.
Refer to the following topics:
- Managing Client Portal users
- Taskfire: managing request types
- Taskfire: managing ticket queues
- Enabling and configuring Quick Ticket settings
- Taskfire: setting scheduled business hours
- Taskfire: Out of Office
- Taskfire: managing vendors
- Two-factor authentication (2FA)
- If you will be sharing ticket work with contacts at other locations (a parent organization/sub-organization Previously: Subsidiary. Your Client Portal instance may be configured to use one fo the following terms instead: Sub-Account, Sub-Business Unit, Sub-Client, Sub-Company, Sub-Customer, Sub-Site. setup in Autotask is required), refer to Taskfire: setting up work sharing between sub-organizations for an overview and recommended steps for configuration.