Administration
Administration
The Admin module is where you configure Frontline PSA. Only resources with the Administrator security level can open it. Every change you make here is written to the audit log.
This page follows the Admin side navigation from top to bottom. Two sections have their own pages: Workflow rules and API integrations.
Overview
Admin → Overview shows a count for each area and a Needs attention list: resources without a timesheet approver, queues without members, customers without a default contract or an SLA, picklist categories with no active values, and SLAs missing a priority target. Click an item to go straight to it.
Settings
Admin → Settings has four groups. Change what you need, then click Save; Discard reverts unsaved edits.
| Group | Settings |
|---|---|
| Organisation | Company name (shown on invoices and quotes) and Business hours: time zone, opening and closing time per day, and holidays |
| Ticket defaults | Default queue, Default priority, Default source |
| Time & expenses | Timesheet approval required, Internal time categories (one per line), Mileage rate |
| Billing | Default tax rate, Show covered lines on invoices, Invoice footer |
Business hours drive every SLA whose clock runs in business hours, and the time zone decides the date used in ticket numbers. Number formats themselves are not configurable.
Resources
A resource is a staff member who can sign in, log time and be assigned work.
- Go to Admin → Resources and click Add resource.
- Enter First name, Last name and Email. The email must match the address the person signs in with.
- Choose a Security level and, optionally, a Department, Default role (the billing role for their time), Time approver, Hourly cost and Weekly capacity.
- Tick any Additional roles they can bill as, and the Queues they belong to.
- Click Add resource.
Click a row to edit it. Safeguards you will meet:
- You cannot change your own security level or deactivate yourself.
- The last active admin cannot be demoted, deactivated or removed. Make someone else an administrator first.
- Remove deletes a resource that was never used. One with history is deactivated instead and can no longer sign in. You can also clear Active (can sign in) and save.
Security levels
Admin → Security levels shows the permission matrix: one row per permission, one column per level. The seven levels are fixed. The matrix is read-only and you cannot create or edit levels; you choose a person's level on Resources.
| Level | What it can do |
|---|---|
| Administrator | Everything, including the Admin module, posting invoices, deactivating companies and contacts, and linking tenants |
| Service manager | View everything; edit and delete tickets; edit CRM, opportunities, projects, contracts, dispatch, inventory and the knowledge base; approve timesheets and expenses; approve billing items but not post invoices; request tenant actions; use AI triage and Scout; write customer memory |
| Dispatcher | View everything; edit tickets; schedule on the dispatch calendar; log own time; view tenants; use AI triage; read customer memory |
| Technician | Edit tickets; view CRM, projects, contracts, dispatch and inventory; write knowledge-base articles; log own time; request tenant actions; use AI triage and Scout; write customer memory. No reports |
| Sales | View tickets, CRM, projects, contracts, inventory, the knowledge base and reports; edit CRM, opportunities and quotes; log own time; read customer memory |
| Finance | View everything; edit CRM and contracts; approve timesheets and expenses; view, approve and post billing; log own time |
| Read only | View everything and read customer memory; change nothing |
Departments
Admin → Departments groups resources and internal projects for reporting. Click Add department, name it and save. A department that resources or projects still use is deactivated rather than deleted.
Roles & rates
Admin → Roles & rates holds billing roles, each with an Hourly rate. Time is billed at the contract's rate for the role if the contract has one, otherwise at the role's rate here. Billing roles are separate from security levels. A role in use is deactivated rather than deleted.
Queues
In Admin → Queues, click Add queue, give it a Name and Description, and tick its Members. The up and down arrows in the Order column set the order of queues in the service desk side navigation. A queue with tickets is deactivated rather than deleted; its tickets stay where they are. See Queues and SLAs.
Picklists
Admin → Picklists edits the dropdown values used across the app. Pick a category on the left: ticket status, priority, type, source, issue type and sub-issue type; company type, classification and market segment; opportunity stage and loss reason; configuration item type; project type; task status; activity kind; KB category; expense category group.
For each value you can change the Label and Tone (colour), reorder it, and switch it Active or not. Sub-issue types have a Parent issue type. Ticket statuses also have a Bucket (open, waiting or done) and an SLA stop tick box that pauses the SLA resolution clock while a ticket is in that status. Click Add value to create one, then Save.
- A value's key is set when you create it and never changes.
- System values, marked with a lock, can be relabelled but not deleted or deactivated.
- A value in use is deactivated rather than deleted.
- Autotask # is the integer that Autotask-compatible API clients send and receive for the value. Only change it when an integration needs a specific number. See Autotask-compatible API.
SLAs
In Admin → SLAs, click New SLA, name it, and choose whether the Clock runs in Business hours or 24 × 7. Under Targets by priority, enter First response, Resolution plan (optional) and Resolution for each priority, for example 30m, 4h, 1h 30m or 2d. Leave a row empty for no target.
Tick Default SLA for the one used when a company has no SLA of its own. The default cannot be deactivated or deleted; make another SLA the default first.
Work types & codes
Admin → Work types & codes has a tab for each kind of billing code: Work types, Material, Expense, Service and Milestone. Each code has a Name, GL code, Taxable and Billable by default. Work types carry no price, because labour is priced by role; the other kinds can have a Unit price and Unit cost.
Audit log
Admin → Audit log is a read-only record of changes across the app: who, when, the kind of record, its ID, the action and a summary. Workflow rules firing, API changes and data exports are recorded too. Filter by entity, action, actor and a From/To date range, or search summaries and record IDs. Click a row for the full detail, including old and new values. CSV downloads the filtered events, up to 10,000 rows.
Notifications
Admin → Notifications opens the Notifications outbox: the queue of outbound email. Messages land here when Frontline PSA would send mail, for example when you send an invoice. Filter by status (queued, sent, failed, suppressed), open a message to read it, and click Suppress to make sure a queued or failed message is never sent.
Limit: Messages are queued here, not delivered. Frontline PSA does not send email yet, so a queued invoice still has to reach the customer another way.
Data
Admin → Data shows the database version, the list of applied migrations, and a row count for each table with a CSV export button. Exports are capped at 50,000 rows per table and recorded in the audit log. There is no import, backup or reset on this page.