Create a technician role
Go to `Settings` > `Roles and Groups` > `Technician Roles`.
Click on `Create` at the top right corner.
Enter the role name and description.
Configure the role as follows:
MSP Settings:
Technicians - `View` only
Technician Groups - `View` only
Ticketing Settings:
Ticket Fields - `View` only
SLA Policy - `View` only
Reply Template - `View` only
Ticket Form - `View` only
Runbook - `View` only
Client Settings:
Client - `View` only
Custom Fields - `Add` & `View`
All Clients - `Allow`
Ticketing:
Tickets - All permissions
All Tickets - `Allow`
Set SLA - `Allow`
Views - `View` only
Task Settings:
Task Template - `View` only
5. Click on `Save` at the top right corner to create the role.
Create a technician or assign the role to an existing technician
Go to `Settings` > `My MSP` > `Technicians`.
Create a new technician by clicking the `Create` button at the top right corner, or edit an existing technician.
Under the `Role` field, select the role created in the previous step.
Get the Subdomain name of your SuperOps account
Login as an admin to your SuperOps account.
Go to `Settings` > `My MSP` > `MSP Information`.
Copy the text under `The subdomain's name`, **without** the `https:\\` or `.superops.ai` part.
Save it for later when configuring the integration in Guardz.
Create API token
Login as the technician with the role created in the first step.
Click on your technician icon at the bottom left corner and then on the name of the technician at the top of the menu.
Under `API Token`, click on `Generate Token`.
Copy the token and save it for later when configuring the integration in Guardz.
Create the Integration in Guardz
Log in to your admin account in Guardz application, click on your user icon at the bottom-left, and select PSA Integration
Select `SuperOps` in the integrations list
Use the Subdomain name and API token you saved earlier to fill in the required fields.
Follow the other steps to create the integration, once it's done and active you should start seeing issues from Guardz as tickets in SuperOps (according to how you configured the integration)
