Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
The User Management section is where you can:
View lists of Service Agents, Robots and Self Service Users
Create, edit and delete Service Agents, Self Service Users and Robots.
Create, edit and delete User Groups to control permissions
Create and maintain User Roles
Reset user passwords and remove users and Robots.
You can access User Management from the toolbar link:
User Management is made up of the following sections:
Service Agents - this section is where you can create and manage the service agents in your system. Service agents are the people who in your service centres and deliver service to your clients, often using Work Manager to do this. Note that the Service Agents page will only appear if you have been given permission to access and edit users.
Robots - this section is where you can create and manage the robots in your system. Note that the Robots page will only appear if you have been given permission to access and edit users.
Self Service Users - this section is where you can create and manage the self service users in your system. Self Service users are the people who you are delivering service to and who are using Enate Self Service. Note that the Self Service Users page will only appear if you have been given permission to access and edit users and if a Self Service instance has been configured.
User Groups - this section is where you can create and manage the user groups in your system. this is a way of grouping together a number of service agents which, when used alongside the permissions feature, can be used to control access to parts of your business operations i.e. you can allow certain user groups to only work on items for a specific customer or contract or service, or even just to work on specific Case & Ticket processes.
User Roles - this section is where you can create and manage the user roles in your system. User roles determine which features service agents can access in Enate.
Application Credentials - this section is where you can create and manage the application credentials in your system. Application credentials allow smoother interaction with third-party systems by effectively granting the logged-in user's account's access levels to the Application Credential record to allow third-party systems using that record to act on this user's behalf.
The Self Service Users page, accessed via the User Management section of Builder, is where you can add, edit and manage your Self Service users. Self Service users are the people who you are delivering service to and who are using Enate Self Service.
Note that the Self Service Users page will only appear if you have a Self Service instance configured.
You can see a list of your existing Self Service users, and information such as their first name, last name, username, email address, company, when they last logged into Self Service, and whether or not they can view community requests i.e. if they can view all of the requests that have been submitted to their company in Self Service.
You can customise the order in which you want to view your Self Service users by clicking on each column header.
Additionally, you can choose to only show Self Service users that belong to a particular company by using the company filter option at the top of the page.
You can also use the search function at the top of the page.
To add a new self service user, go to the ‘Self Service Users’ page in Builder’s User Management section click the '+' icon at the top of the screen. This will bring up the ‘Add Self Service User’ pop-up where you can enter the person's details.
In the General tab you can add the following details:
In the Password tab you then need to set the self service user's password. Please note that passwords:
Should not contain the username, first name or surname of the user.
Should contain at least contain 8 characters.
Should not contain more than 16 characters.
You can edit the details of an existing user by clicking on the menu link on the right-hand side of the contact. All attributes can be modified.
You can also see what edits have been made to a user account and when, as well as when the user account was created, by clicking on the Show Activity button.
You can delete a Self Service user by clicking on the menu link on the right-hand side of the contact.
Note: deleting a Self Service user is a logical delete only; the user account is effectively retired. The account can be reactivated at any point.
You are able to reactivate or "undelete" retired Self Service users by activating the system-wide ‘Show deleted items’ button. This will show you your retired users which will be greyed out in your grid. Clicking on the menu option of a retired user will shows you an option that allows you to reactivate that user account and set them as an active user.
You can reset the password of a Self Service user by clicking on the menu link on the right-hand side of the contact and selecting 'Change password'. You can then give them a new password as per password policy.
User Groups are, as the name suggest, ways of grouping together a number of users - specifically Service Agent type users. User Groups can be used for (see below) for a number service agents to specific parts of your business operations, i.e. for certain Customers, their Contracts, Services or even down to specific Case & Ticket processes.
Watch this video to find out more:
To create a user group, navigate to the 'User Groups' section of User Management, create a new group and add one or more users into it. Once saved, the User group is ready to use with permissions linking.
When creating or editing a User account, you can select which user groups they should be in via their settings on the Access tab.
Link up at the customer/contract/service-level, that User group has access to all work items under that customer/contract/service. Conversely if you set down at the Case-process level, that User Group has access to work items within that Case process specifically within that customer/contract/service combination.
Setting User groups with permissions at customer/contract/service can easily be done by navigating the to Service Matrix screen and clicking to edit the desired customer/contract/service.
Once that has been set, only users within this User Group have access to work items (creation, editing etc.) for that customer, contract or service.
For example, if you link up at the customer-level, that User group has access to all work items under that customer. Conversely if you set down at the Case-process level, that User Group has access to work items within that Case process specifically within that customer/contract/service combination.
To set permissions for a specific customer's Case or Ticket process, go to the Service Matrix, select the Permissions link and add the User Groups you want to be able to access it.
Note that any Permissions set at higher level will show read-only when accessing settings for any item in the Service Matrix.
Once that has been set, only users within this User Group have access to work items (creation, editing etc.) within that Case process specifically within that customer/contract/service combination.
The Application Credentials page gives developers a dedicated way to support how their APIs can be given access to the system.
Application Credential records can be created by an individual user logged into Builder. In creating such a record, the logged-in user effectively grants their own user account's access levels to the Application Credential record, to allow third party systems using that record subsequently to act on this user's behalf. However the user may not wish to grant the access which is available to all of the roles they occupy, so as part of the record creation they can specify a subset of roles which this Application Credential would have the power to use.
Using this Application Credential approach for granting API access has some advantages over using standard user accounts:
A single set of application credentials can have multiple concurrent sessions active.
You can select specific levels of access to grant each set of application credentials, keeping permissions only as expansive as they need to be.
Allows a more appropriate support for system-to-system communication.
Gives better tracking of which APIs are accessed by third party applications.
In technical terms, this feature allows Builder admin users to create sets of credentials, specifically 'OAuth Client Credentials' to access Enate & call APIs. Enate uses OAuth2.0 (Open Authorization) for token-based authentication and authorization. For more information on OAuth2.0, please refer to this link .
The approach is as follows:
An Enate user logs into Builder and creates an application Credential record (a specific 'ClientID & SecretKey' record, which is effectively a username & password).
External to Enate, you must call the Enate OAuth/Token API passing the client id and client secret to obtain a token (specifically a '').
Ensure this Token is included in each API call which is made into the Enate system.
Note that the bearer token will expire if it is not used to make an API call for the length of time set in the 'Idle Session Timeout' setting in the General Settings section of Enate Manager.
If the bearer token does expire, the application credentials can be re-authenticated by using the '/OAuth/Token' Enate API to generate a new bearer token.
Additionally, any changes made to a user's roles (i.e. if a user gets assigned a new role or they are removed from a role) will cause the bearer token to expire.
If a bearer token does expire, the application credentials can be re-authenticated by using the '/OAuth/Token' Enate API to generate a new bearer token. Note that revoked roles will not get assigned to a new bearer token.
To support this feature we've added a new section in the User Management section of Builder to help manage different sets of Application Credentials you may wish to create:
The resulting screen will show a list of any existing Application Credentials which the logged-in user created before (Application Credentials created by other users are not displayed), including the roles the role(s) assigned to the user and the expiry date.
To create a new credential record, click on the '+' link, and fill out the details in the resulting popup:
Enter a name for the credential and add an expiration date. Then select the Operational Role you want the credential to have. If you want the credential to access Builder, select a Builder role too. These roles determine the various access options that a user will have access to.
Then click to generate a key. This will create:
A Client ID
A Secret Key
You should copy these two pieces of data at this point, for use in subsequent steps to create a Bearer Token outside of Enate.
Note: You will only be able to access this secret key once, at this point. Once the pop-up window is closed you will no longer have access to it, and if you have not taken a note and subsequently wish to use this client ID, you would need to generate a new secret key.
Once the Credential record has been generated, it will be saved and stored in the Application Credentials page. You, as the creator of the record, can subsequently edit its name and expiry date and generate a new secret key for it. Credential records can also be deleted if desired.
You should use the copied Client ID and Secret Key as inputs into your third party system, for example the Postman API testing tool. From example above, this would be:
Client ID: eba59171-ac3a-4527-939a-830494c2c5f6
Secret Key: 3@rn0i+0y5jRB8_n
The Third-party system should be making a POST API call to the '/OAuth/Token' Enate API to generate the bearer token.
For the API request, select 'x-www-form-urlencoded' in the body section to pass the three parameters below while making the API call to generate the token.
grant_type - client_credentials
client_id - 0f6c907b-00f4-4e12-8d75-41454b777533
client_secret - TLd55KNez61niSXO
Example:
This generates the Bearer token, which is then used to get authorization for API calls to Enate.
To make a new API call to Enate, select Type as ‘Bearer Token’ in the Authorization section of the API request, pass your generated bearer token and the request URL for the specific API you're looking for.
The Service Agents page, accessed via the User Management section of Builder, is where you can add, edit and manage your service agents. Service agents are the people who in your service centers and deliver service to your clients, often using Work Manager to do this.
You can see a list of your existing service agents and information such as their first name, last name, username, email address, supplier company, when they last logged into Work Manager and their Operational and Builder Roles.
You can customize the order in which you want to view your service agents by clicking on each column header.
Additionally, you can choose to only show service agents that belong to a particular supplier company by using the company filter option at the top of the page.
You can also use the search function at the top of the page.
To add a new service agent, go to the ‘Service Agents’ page in Builder’s User Management section and click on the '+' icon at the top of the screen. This will bring up the ‘Add User’ pop-up where you can enter the person's details.
In the General tab you can add the following details:
Enate allows for a granular level of granting access to people based on their role and business requirements. These settings are defined in the Access tab. Here you have the ability to set the following levels of access:
The details tab lets you add more detailed information for the service agent, including:
In the Password Tab you must set the service agent's password according to your password policy.
See here for more information about setting your password policy:
You can edit the details of an existing user by clicking on the menu link on the right-hand side of the contact. All attributes can be modified with the exception of the company to which they belong.
You can also see what edits have been made to a user account and when, as well as when the user account was created, by clicking on the Show Activity button.
You can delete a Self Service user by clicking on the menu link on the right-hand side of the contact.
If you need to reactivate a service agent you can do this via the 'Service Agents' screen in User Management section of Builder. Once you are on the ' Service Agents' screen go to your settings in the top right and enable 'Show deleted objects'. Once this has been enabled all service agents who have been deactivated will appear in the grid grayed out. Go to the ellipses menu at the end of the row of the service agent you wish to reactivate and select the 'Re-activate' option. This will reactivate that service agent account and set them as an active service agent.
You can reset a service agent's password by clicking on the menu link on the right-hand side of the contact and selecting 'Change password'. You can then give them a new password according to your password policy.
See here for more information about setting your password policy:
There are also further access options within the tab, see the section about here
You can set user Permissions in conjunction with to control levels of access for your Service Agents to the various parts of your business operations (as represented in the Service Matrix screen - who are your customers, what services are you delivering to them).
You do this by linking the user group to the 'Permissions' setting at various points in the Service Matrix. You can either add permissions or .
The integration approach uses a type of tokens called 'Bearer Tokens' to access the Enate APIs. These Bearer tokens use HTTPS security, and the request is not signed or encrypted: possession of the bearer token is considered authentication. For more about OAuth 2.0 access tokens, refer to this link .
If you need to collect further information on a service agent beyond the default data fields, you can create and add in as many data fields as you need via .
Note: deleting a Self Service user is a logical delete only; the user account is effectively retired. The account can be at any point.
Company
The organisation this user works for.
Mandatory. Note that once the user has been added, the company they belong to can no longer be changed.
Username
User’s username, with which they login to all Enate applications
Mandatory
First Name
User’s first name
Mandatory
Last Name
User’s last name
Optional
The user’s work email address
Mandatory
Language
User's preferred language
Optional
Time zone
The user’s local Time zone
Mandatory
Calendar
The working calendar for this user
Optional
Send Welcome Email
If you switch this on, the self service user will receive an automatic emails, such as a 'Welcome to Self Service' email and emails relating to the status of their submitted requests.
Optional
Can view 'My Company Requests'
If this option is switched on, the self service user can see community requests when they are logged into Self Service. This means that they can see requests submitted to their company.
Optional
Supplier | The organisation this user works for. You can add a specific company that the service agent works for OR you can select to make them a 'Global Agent' where they aren't linked to a specific company. Service agents linked to a specific company will not be able to be added as a contact to a work item belonging to a different company. 'Global Agents' agents have much more flexibility - they can be linked to any work item, regardless of company, letting them send and receive communications from them, and they can also be added to any team, regardless of the company the team leader is linked to. This is particularly useful when your organisation has different operations set up as separate customers. | Mandatory |
Username | User’s username, with which they login to all Enate applications | Mandatory |
First Name | User’s first name | Mandatory |
Last Name | User’s last name | Mandatory |
The user’s work email address | Mandatory |
Language | User's preferred language for work Manager. See below for more details. | If a language is not set while creating the User, the system will use the language of the User’s company as its default. The 'Welcome Email' will be sent in the selected language as well. An end-user’s language setting determines which welcome email template to use, and when setting the value for schedule-driven Work Items (which have the name of the schedule as part of the Work Item title and therefore the email subject). If the schedule name has been localised into that language, the system will use the localised term instead. |
Time zone | The user’s local Time zone | Mandatory |
Calendar | The working calendar for this user |
Single Sign-On user | Whether the user can access Enate via single sign-on. | Use only in conjunction with environments which have been set up with Single Sign-on |
Send Welcome Email | Whether to send an automated welcome email upon creating the user |
Attribute | Description | Notes |
Builder Role | This determines which Builder role the user has and therefore which Builder features the user will have access to. User roles are configured in the User Roles section of User Management in Builder. | Select either a standard or custom role from the dropdown. Optional. Note: if you want the user to be able to access Builder, you must give them a Builder role. |
Operational Role | This determines which Work Manager role the user has and therefore which Work Manager features the user will have access to. User roles are configured in the User Roles section of User Management in Builder. | Mandatory. Select either a standard or custom role from the dropdown. Note: if you want the user to be able to access Builder, you must give them a Builder role. |
Allowed Work Types | This determines whether the user can access test work items (via Test Mode) and/or live work items. | Mandatory. Select from:
|
User Groups | This determines the user groups that the user belongs to. | User Groups are used for controlling permissions to access certain types of data, e.g. for certain customers, contracts or services or even for specific Case or Ticket processes . If a user is part of a user group, the user will have permission to access data that has been configured for that User Group. Optional. |
Attribute | Description | Notes |
Know As | What name is the user know by |
Employee ID | Uniquely identifying ID for this user. |
Total Capacity | The number of working hours (and mins) this user works per day. |
Cost Per Hour | The resource cost of this user per hour while they are working | Can be used in costing reporting. Note that this value cannot be negative. |
Service Line | What service line does the user work |
Location | User's work location |
Cost Centre | User's cost centre |
Department | User's department |
Employment Type | User's employment status |
Start Date | User's employment start date |
The Robots page, accessed via the User Management section of Builder, is where you can add, edit and manage your Robots. Robots are the account for RPA bots to let them interact with the system.
You can see a list of your existing Robots, and information such as their name, their farm and whether or not they are externally managed.
You can customise the order in which you want to view your Robots by clicking on each column header.
You can also use the search function at the top of the page.
Please note that if a Robot is Externally Managed (e.g. it is managed via a different robotics platform such as UiPath Orchestrator), you will be able to see the Robot in this list, but you will not be able to modify any of its attributes directly in Enate.
To add a new Robot, go to the ‘Robots’ page in Builder’s User Management section and click on the '+' icon at the top of the screen. This will bring up the ‘Add Robot’ pop-up where you can enter the person's details.
In the General tab you can add the following details:
Enate allows for a granular level of granting access to people based on their role and business requirements. These settings are defined in the Access tab. Here you mu choose which Builder role to assign to the robot by selecting from the dropdown menu. This determines which Builder role the user has and therefore which Builder features the user will have access to. User roles are configured in the User Roles section of User Management in Builder. Select either a standard or custom role from the dropdown.
In the Password Tab you must set the Robot's password according to your password policy.
See here for more information about setting your password policy:
When linking a robot to a farm, you may need to create a new Farm. This can be done by clicking the link in the farm dropdown.
You will be presented with a popup where you can define the name of the farm, a description, and choose the technology which it uses (current options: UiPath, BluePrism, Automation Anywhere).
You can edit the details of an existing Robot by clicking on the menu link on the right-hand side of the contact. All attributes can be modified with the exception of the Robot's username.
You can also see what edits have been made to a Robot and when, as well as when the Robot was created, by clicking on the Show Activity button.
You can delete a Robot by clicking on the menu link on the right-hand side of the contact.
You can reset a Robot's password by clicking on the menu link on the right-hand side of the contact and selecting 'Change password'. You can then give them a password according to your password policy.
See here for more information about setting your password policy:
Enate allows for a granular level of granting access to people based on their role and business requirements.
This is done by . Each role has a configured for it which determine what they can see and do in Enate. Every user must have a Work Manager role, but only the users who need to access Builder need to have a Builder role.
Watch this video to find out more:
Custom roles might be particularly useful in the following circumstances:
In Work Manager: You may wish to create a custom role for your more senior team members which falls part-way between the standard 'Team Leader' and 'Team Member' roles, giving them access to some Team Leader-like features without needing to have them fulfil that role entirely.
In Builder: Custom roles can be very useful in larger organizations where you might want to delegate e.g. user management or localized Case/Ticket maintenance access in Builder to more local resources, while keeping shared configuration activities for master data to a more select few people.
You can assign the relevant roles to a user in the Service Agents section of Builder by:
Clicking to edit a user and then selecting the relevant roles from their access tab OR
Clicking on the user's role directly from the grid of user accounts, on the 'Operational Role' or 'Builder Role' column. This will then bring up the user's access tab:
Users can be given two roles: they must have an Operational role which grants them access to the relevant features in Work Manager and, if they need to access Enate Builder, they can be given a Builder role too. This Builder Role will give them access to build and maintain the data which underpins your business processes in Enate. The majority of your user base will likely be assigned with just an operational role, but your administrators, business analysts and some operational super users will also be assigned a Builder role. If you do not assign a Builder role to a user, they will not be able to access the Builder app.
One thing that is important to note is that a user is not able to edit the access levels of the role they have been assigned, nor are they able to assign themselves a new role. This must be done by another user.
If you change a user's role while they are logged into the system, the user will be automatically logged out with a warning message stating that their user session has ended. When the user logs back into the Enate system, they will be able to see and access the features that have been enabled for the new role they have been assigned.
If you edit the details a user's role while they are logged into the system, they will not be automatically logged out of the system, but they will not be able to use or see the changes to their role until they have logged out and logged back into the system.
You can view, create and maintain your user roles in the new User Roles section of Builder - click on User Management and then select User Roles from the dropdown.
Clicking on a user role will bring up the details for that role, including its name, description and access to which features are enabled for it.
Note that you will not be able to edit the name, description or feature access for standard roles.
Enate provides some standard pre-configured roles to give your users access to the various Work Manager and Builder features that they need, which already have a variety of feature access options enabled. The feature access options for these standard roles cannot be edited.
There are two standard operational roles:
Team Member - this is for Agent users who process Tickets, Actions & Cases
Team Leader - this is for senior members who manage a Team and set Queues they oversee
The table below shows access to which features are enabled for team member and team leader roles
There are three standard Builder roles:
Local Builder - this provides more limited access to configure Ticket & Case processes
Master Builder - this provides users with access to create shareable master data, configure processes and set live
System Administrator - this provides full access to all configuration features in Builder, including integrations
The table below shows access to which features are enabled for the standard Builder roles:
If the standard roles don't quite match your organization's needs, you can create custom roles and customize the levels of access within the role.
You create and maintain custom roles from the User Roles section of Enate Builder.
To create a custom role for Work Manager, click the '+ Create New Custom Role' option in the Operational Roles tab, and to create a custom role for Builder, click the '+ Create New Custom Role' option in the Builder Roles tab.
You can create a brand new custom role in two ways:
Option 1 - From scratch, starting from a blank role where you will need to populate all your desired role data
Option 2 - By cloning an existing role (standard or custom) and adjusting the data accordingly. This option is useful if you only want to make a slight adjustments to an already existing role.
Whether creating from new or cloning from existing, proceed by giving your new custom role a name, description and then select what features you want the role to access. Once you have created your role be sure to save it before exiting the page.
There are a large number of access options available to choose from when you are defining a role's access to the various features in Enate. The full list of operational access options are listed below.
Note that if access to a feature has not been given, the option/button for that feature will be hidden.
The full list of Builder access options are listed below.
Note Builder access options only provide access to edit the relevant information. All information in Builder is still available as read-only. The only exception to this rule is that access to view information about users - service agents, robots and self service users - is dependent on the Builder option for security reasons.
Additionally, all users (who are not robots) who have access to Builder are able to access and edit Application Credentials (found under User Management).
Note: deleting a Robot is a logical delete only; the user account is effectively retired. The account can be at any point.
You are able to reactivate or "undelete" retired Robots by activating the system-wide ‘’ button. This will show you your retired Robots which will be greyed out in your grid. Clicking on the menu option of a retired user will shows you an option that allows you to reactivate that Robot and set them as active.
There are a number of available that give your users various levels of access to Work Manager and Builder.
If a standard role doesn't quite fit the bill, you can create that allow you to fine-tune levels of access to give users the exact combination of access levels they need.
Here you will see the standard roles available in the system, as well as any custom roles you have and this is where you can .
| Feature Access Area | Feature Access Name | Team Member | Team Leader |
|---|
| Feature Access Area | Feature Access Name | Local Builder | Master Builder | System Administrator |
|---|
| Feature Access Area | Feature Access Name | Detail |
|---|
| Builder Access Area | Feature Access Name | Detail |
|---|
Work Item Creation | Can Create Individual Work Items | Yes | Yes |
Can Bulk Create Work Items | No | Yes |
Work Item Assignment | Can Assign to Anyone | No | Yes |
Can Assign to Themselves | Yes | Yes |
Can Unassign | No | Yes |
Work Item Options | Can Override Due Date | Yes | Yes |
Can Split Tickets | Yes | Yes |
Can Merge Tickets | Yes | Yes |
Can Convert to Case | Yes | Yes |
Can Edit Defects Logged by Others | Yes | Yes |
Can Edit Time Tracker Entries Logged by Others | No | Yes |
Can Access Custom Data in Peer Review Actions | Yes | Yes |
Can Delete Email Attachments | No | No |
Queues & Team Members | Can View Queues & Team Members | Yes | Yes |
Can Work on Items Outside their Queues | Yes | Yes |
Can Set Up Team & Queues | No | Yes |
Email View Options | Can Access Email Inbox, Sent Items & Outbox | Yes | Yes |
Can Access Unprocessed Emails | Yes | Yes |
Can View Blocked Email Addresses | Yes | Yes |
Can Edit Blocked Email Addresses | No | Yes |
Contacts | Can Access Contacts Page | No | No |
Advanced Search | Can Access Advanced Search Page | Yes | Yes |
Can Export Advanced Search views to Excel | No | No |
Reports | Can Access Reports | Yes | Yes |
Can Create Custom Reports | No | Yes |
Edit Business Entities | Companies | Yes | Yes | Yes |
Contracts | Yes | Yes | Yes |
Service Lines | No | Yes | Yes |
Services | Yes | Yes | Yes |
Edit Processes | Cases | Yes | Yes | Yes |
Tickets | Yes | Yes | Yes |
Edit Shared Process Data | Action General Settings | No | Yes | Yes |
Action Types | No | Yes | Yes |
Allocation Settings | No | Yes | Yes |
Case Types | No | Yes | Yes |
Due Date Settings | No | Yes | Yes |
Ticket Categories | No | Yes | Yes |
Ticket Types | No | Yes | Yes |
Edit Queues | Queues | Yes | Yes | Yes |
Set Tickets & Cases Live | Set Tickets & Cases Live | No | Yes | Yes |
Edit Scheduling | Fixed Frequency Schedules | Yes | Yes | Yes |
Schedules | Yes | Yes | Yes |
Schedule Structures | No | Yes | Yes |
Edit Calendars | Calendars | Yes | Yes | Yes |
Edit Custom Cards & Data | Custom Cards & Data | Yes | Yes | Yes |
Access User Management | Robot Farms | No | No | Yes |
User Roles | No | No | Yes |
User Groups | No | No | Yes |
Users (Service Agents & Self Service Users) | No | No | Yes |
Edit Mailbox Settings | Email Routes | Yes | Yes | Yes |
Email Connectors | No | Yes | Yes |
Edit Email Content | Canned Responses | No | Yes | Yes |
Email Templates | No | Yes | Yes |
System Settings | System Settings | No | No | Yes |
Edit Integrations | Marketplace Configurations | No | No | Yes |
Edit Localizations | Localizations | Yes | Yes | Yes |
Delete Items | Delete Items | Yes | Yes | Yes |
Attribute | Description | Notes |
Username | Auto-generated username | This cannot be manually set, but is viewable here after robot creation. You can copy the Username by clicking on the copy icon. |
First Name | The robot’s name, for use when tracking in Work Manager | Mandatory |
Total Capacity | The number of working hours per day that the robot can work for. |
Cost per Hour | The cost of the Robot resources |
Allowed Work Types | Whether the Robot is set to work on Live work items, Test work items, or both. |
Time zone | The user’s local time zone | Mandatory |
Calendar | The working calendar for this user | Mandatory |
Farms | The farm(s) this robot belongs to | Note that a robot can belong to more than a single farm. |
Work Item Creation | Create Individual Work Items | This gives the user access to the following features: |
Bulk Create Work Items | Note that the 'Create Individual Work Items' option must be enabled for this 'Bulk Create Work Items' option to be enabled. |
Work Item Assignment | Assign to Anyone |
Assign to Themselves |
Unassign |
Work Item Options | Override Due Dates |
Split Tickets | Note that the 'Create Individual Work Items' option must be enabled for this 'Split Tickets' option to be enabled. |
Merge Tickets |
Convert to Case | Note that the 'Create Individual Work Items' option must be enabled for this 'Convert to Case' option to be enabled. |
Edit Defects Logged by Other | Note that even without this access option, users are still able to add a new defect and edit, mark as resolved and delete defects that were added by themselves. |
Edit Time Tracker Entries Logged by Other | Note that a user will always be able to modify their own time entries regardless of this access option. |
Access Custom Data in Peer Review Actions | Note that even without this permission, users are still able to view custom card data and to choose if the review was a Pass, Fail or was Unable to be completed. |
Delete Email Attachments |
Queues & Team Members | View Queues & Team Members |
Work on Items Outside Their Queues | This gives a user access to work on items assigned to any Queue (permissions permitting), as opposed to only being able to work on items which are specifically assigned to Queues that they are a part of. Note that users will still be able to work on items that are not assigned to a Queue. Additionally, if this option is switched off users can continue to work on items which were already assigned to them that are not in their Queues. These items can be unassigned from the user manually. |
Setup Team & Queues |
Email View Options | Access Email Inbox, Sent Items & Outbox |
Access Unprocessed Emails |
View Blocked Emails Page | Note that this access option does not give users the ability to edit blocked emails information - they will need the 'Edit Blocked Email Address Entries' access option to be switched on as well. |
Edit Blocked Email Address Entries | Note that the 'View Blocked Emails Page' access option must be enabled in order for the 'Edit Blocked Email Address Entries' access option to be enabled. |
Contacts | Access Contacts Page |
Advanced Search | Access Advanced Search |
Export Advanced Search Views into Excel | This gives a user access to the Export to Excel feature in the Advanced Search page that allows users to export their Advanced Search views into Excel. Note that the 'Access Advanced Search' option must be enabled in order to enable the 'Export to Excel' option. |
Reports | Access Reports | This gives a user access to the Reports feature, available from the nav menu, where they can view and edit reports to visualize desired data. Note that in order to enable this option, you must select at least one report the users in the role will be able to access from the resulting Report List option. |
Create Custom Report | This gives a user access to the advanced features on the Reports page - they can create brand new visuals and delete existing visuals. Note that the 'Access Reports' option must be enabled in order to enable the 'Create Custom Reports' option. |
Report List | Choose which reports the role will be able to access | This allows you to choose which standard report(s) you want the users in the role to be able to access. You must select at least one. Note that the Report List will not appear as an option until the 'Access Reports' option has been enabled. |
Edit Business Entities | Customers |
Contracts |
Service Lines | Note that Ticket Category details for a service line can still be edited by users without the 'Service Lines' access option if the 'Ticket Categories' access option is enabled for them. |
Services |
Edit Processes | Cases |
Note that this access option does not allow users to:
|
Tickets | and With this access option, users can:
Note that this access option does not allow users to:
|
Edit Shared Process Data | Action General Settings | Note that the 'Edit Cases' access option under Edit Processes must be enabled in order for a user to edit Action general settings. |
Action Types |
Allocation Settings | Note that either the 'Edit Cases' or 'Edit Tickets' access options under Edit Processes must be enabled in order for a user to edit allocation settings. |
Case Types |
Due Date Settings | Note that the 'Edit Cases' or 'Edit Tickets' access options under Edit Processes must be enabled in order for a user to edit due date settings. |
Ticket Categories |
Ticket Types |
Edit Queues | Queues |
Set Tickets & Cases Live | Set Tickets & Cases Live |
Edit Scheduling | Triggers |
Schedules |
Schedule Structures |
Edit Calendars | Calendars |
Edit Custom Cards & Data | Custom Cards & Custom Data |
Edit User Management | Robot Farms | Note that the 'Users (Service Agents, Robots & Self Service Users)' access option must be enabled in order for a user to edit robot farm data. |
User Roles | This option gives users access to create and edit user roles. Note that a user with this access option will not be able to edit their own user role. |
User Groups |
Access & Edit Users (Service Agents, Robots & Self Service Users) |
Edit Mailbox Settings | Email Routes |
Email Connectors | Note that without this 'Edit Connectors' access option, the Office 365 Integration will be hidden in the System Settings page. |
Edit Email Content | Canned Responses |
Email Templates |
Edit System Settings | System Settings |
Edit Integrations | Marketplace Configurations |
Edit Localizations | Localizations |
Delete Items | Delete Items | This option gives users access to delete objects that they have edit permissions for. Note that you cannot enable the Delete option without having enabled one of the edit options first for Builder Roles. |
Note that when linking a robot to a farm, you may need to create a new farm. See here for .
the
creating a new work item from the
(as this results in the creation of two or more brand new work items)
(as this creates a brand new Case)
sending an email to another that is using Enate that will result in the creation of a new work item for that team.
Creating a
Creating a
Note that users can still use the and they can still .
This gives the user access to use the .
This gives a user access to , either from the homepage or from within the work item itself.
This gives a user access to , either from the homepage or from within the work item itself, or from .
This gives a user access to , either from the homepage or from within the work item itself.
This gives a user access to from within the work item screen by clicking on the due date in the header and changing the date in the resulting pop-up (if the work item has been set up in Builder to allow the due date to be overridden).
This gives a user access to use the feature.
This gives a user access to use the feature.
This gives a user access to use the .
This gives a user access to edit, mark as resolved and delete that have been logged by other people.
This gives a user access to edit the time entries in the that have been logged by other people.
This gives a user access to edit custom card data in a .
This gives a user access to from the files tab section of a work item.
This gives a user access to view their and in the , as well as access to view their team's work or owned work via the 'Team Work Inbox' and 'Team Owned Work' .
This gives a user access to the via the 'Queues' page from the nav menu.
This gives a user access to the , and features, available from the nav menu.
This gives a user access to the , where users can review the unprocessed emails that have arrived into the system and decide how to deal with them (i.e. creating a work item from the email or deleting the email).
Note that if the 'Create Individual Work Items' access option setting is not enabled, users will not be able to .
This gives a user access to view the and therefore access to view information for emails that have been blocked.
This gives a user access to edit the information for emails that have been blocked in the .
This gives a user access to the where they can view and manage external contacts, available from the 'Contacts' option in the nav menu.
This gives a user access to the where they can create search views of work item data in their business area.
This option gives users access to .
This option gives users access to .
This option gives users access to .
This option gives users access to .
This option gives users access to create and . With this access option, users can:
This option gives users access to create and .
This option gives users access to create and edit in Case processes.
This option gives users access to create and edit Action types from either the screen or from .
This option gives users access to create and edit for processes, regardless of their access to edit Cases or Tickets.
This option gives users access to create and edit Case types from either the screen or from the screen.
This option gives users access to create and edit for processes, regardless of their access to edit Cases or Tickets.
This option gives users access to create and edit , either from the screen or from itself.
This option gives users access to create and edit Ticket types from either the screen or from the screen.
This option gives users access to create and edit Queues, either or .
This option gives users access to set and live, both from within the process itself and from the service matrix.
This option gives users access to create and edit - these allow you to drive Case creation based on a repeating frequency to trigger automatic creation.
This option gives users access to create and edit .
This option gives users access to create and edit - .
This option gives users access to create and edit - working calendars are linked to contracts and are used in day to day processing of work items to help determine precise due dates.
This option gives users access to create and edit and .
This option gives users access to create and edit , accessible when creating or editing a robot user account.
This option gives users access to create and edit .
This option gives users access to view, create and edit , and .
This option gives users access to create and edit .
This option gives users access to create and edit , as well as access to view, create and edit an where you can sync Enate to Office 365 email boxes, available in the page.
This option gives users access to create and edit .
This option gives users access to create and edit .
This option gives users access to create and edit . These are the settings that take effect across the entire system and includes , , , , , password policy and SSO settings.
Note that users will not be able to create and edit from here unless the 'Queues' access option has also been enabled. Additionally, note that the , where you can sync Enate to Office 365 email boxes, will be hidden unless the 'Edit Connectors' access option is enabled.
This option gives users access to create and edit app integration configurations in .
This option gives users access to create and edit .
