Frontline PSA Docs

Intelligence

Customer tenants

A customer tenant is a customer's Microsoft 365, Okta or Datto RMM environment. Frontline PSA reaches these through DPGatekeeper, a separate broker that holds the vendor connections and approvals. Frontline PSA holds no vendor credentials and can never approve its own requests. It links a Gatekeeper tenant to a company, asks Gatekeeper to run a fixed set of actions, and records the outcome on the ticket.

Tenants and their connections are created in the Gatekeeper console, not here. Setting up the connection between Frontline PSA and Gatekeeper is covered in Deployment.

Note: If you see a MOCK GATEKEEPER tag on these screens, Frontline PSA is not connected to a live Gatekeeper. The tenants and results are fictional demo data and no real tenant is touched.

The Tenants list

Open Tenants in the main navigation.

Frontline PSA
Tenants list showing linked tenants with connection chips and health, and unlinked tenants below

The banner at the top shows whether Gatekeeper is reachable and which identity Frontline PSA is using. If it reads Gatekeeper not reachable, tenant actions will not work until that is fixed. The four tiles count Linked tenants, Healthy, Needs attention and Pending approvals.

  • Linked lists tenants bound to a company. Each row shows the PSA company, Domain, a chip per connection (for example Microsoft Graph or Okta), Health (Healthy, Attention, Unavailable or Unknown) and Last verified. A chip with an amber or red dot has a problem; hover over it for details. A not visible tag means Gatekeeper no longer shows that tenant to Frontline PSA.
  • Unlinked lists tenants that Gatekeeper shows but that are not yet bound to a company. Where a company name matches, it appears under Suggested company.
  • MSP connections lists connections shared across all customers, such as Datto RMM.

Use the side panel to filter by Healthy, Needs attention or Unlinked, or to jump to a linked tenant.

You need tenant administration rights for this.

  1. Under Unlinked, click Link to company on the tenant's row.
  2. Choose the PSA company. A suggested match is filled in when there is one.
  3. Optionally enter a Default domain and a Note.
  4. Click Link.

Tickets for that company, and for its child companies that have no link of their own, now offer tenant actions. On a linked row, Pause stops tenant actions for the company without removing the link (Resume turns them back on), and Unlink removes it. Unlinking changes nothing in Gatekeeper and history is kept.

The tenant page

Click a tenant to open it. The header shows the linked company, default domain and when the link was last verified. Verify now re-checks that Gatekeeper still shows the tenant and its connections.

Frontline PSA
Tenant page with connections, available actions and link details
TabWhat it shows
OverviewConnections (read-only here, managed in Gatekeeper), counts of available actions, Recent activity, and the Link panel.
DirectoryLive reads from the tenant: Users, Groups, Licences, Domains, Devices, Mailbox usage and OneDrive usage. Use Filter to narrow rows and Refresh to fetch again.
ExecutionsEvery read and write requested for this tenant, with status, requester, approver and ticket.

Directory results are shown as plain text and may be the first page only when the vendor has more rows.

Datto RMM sites

Datto RMM is one connection shared by all customers, so each company must be bound to its own RMM sites. In the Link panel, a tenant administrator picks a site under Bind an RMM site and clicks Bind. Until a site is bound, RMM actions are refused for that company, and sites belonging to other companies are never shown.

Tenant actions on a ticket

Open a ticket and find the Tenant actions section. It shows which company the tenant was resolved from (the ticket's company or a parent company) and lists the actions available. Press A to jump to the Filter actions box. An action that is greyed out shows the reason when you hover over it, for example a missing or disabled connection.

Read actions

Reads run immediately and need no approval.

ActionReturns
List usersMicrosoft 365 users: name, sign-in name, enabled or disabled
Find userA user by exact email or sign-in name, or by the start of their name
GroupsMicrosoft 365 groups
LicencesLicence SKUs with assigned, total and free seats
DomainsTenant domains and verification state
Managed devicesIntune managed devices and compliance
Mailbox usageMailbox size and item counts, last 7 days
OneDrive usageOneDrive storage and file counts, last 7 days
List Okta usersOkta users: login and status
RMM sitesDatto RMM sites bound to the company
RMM devices for a siteDevices in one bound Datto RMM site
  1. Click the action. If it needs input (such as UPN, email or name for Find user), fill it in and click Run.
  2. Review the result shown under the list.
  3. To keep it, click Add to ticket as internal note.

List results return one page from the vendor, so large tenants may not show every row.

Write actions

There are three write actions:

ActionWhat it doesYou provide
Disable accountBlocks sign-in for one Microsoft 365 accountUser
Send mailSends a plain-text message from a tenant mailboxFrom mailbox, To (up to 10 addresses), Subject, Message
Suspend Okta userSuspends one Okta userOkta user

For Send mail, the sender must be on the connection's approved sender list in Gatekeeper.

Every write follows the same two-person process:

  1. Click the action, fill in the fields and click Review.
  2. Check the exact parameters shown: tenant, connection, operation and target. Enter a Reason. It is added to the ticket note. The reason is not enforced by the form, but your approver will expect one.
  3. Click Submit for approval. Nothing changes at the vendor yet.
  4. A different person approves the request in the Gatekeeper console. The card on the ticket shows Awaiting approval in Gatekeeper with a countdown. You can leave the page.
  5. Once it is approved, click Execute. Only the person who made the request can execute it.

Requests expire 15 minutes after they are made. If a request is not approved and executed within that time, nothing is sent to the vendor.

You cannot submit a second identical request while one is still open.

Limit: Write actions are limited to Disable account, Send mail and Suspend Okta user. The ticket lists the rest under Not available through Gatekeeper yet: password reset and forced change, revoking sessions, Temporary Access Pass and resetting authentication methods, sign-in and audit logs, enabling an account, adding or removing group members, assigning or removing licences, Intune device actions (lock, retire, wipe, sync) and Autopilot, Exchange administration (quarantine, forwarding) and Teams presence or phone, joiner/mover/leaver provisioning, and tenant onboarding. Do these in the vendor's own admin tools.

Approvals

Open Tenants → Approvals to see every request made from Frontline PSA.

Frontline PSA
Approvals page with requests awaiting approval, approved requests and recent executions

The page lists requests that are Approved — waiting for the requester to execute, then those Pending approval in Gatekeeper, then Recent · 7 days, which you can filter by All, Writes or Reads. You cannot approve here. Approval always happens in the Gatekeeper console, by someone other than the requester.

StatusWhat it meansWhat to do
pendingWaiting for a different person to approveAsk an approver to act in the Gatekeeper console. Cancel request if it is no longer needed.
approvedApproved and waiting for the requesterThe requester clicks Execute before the countdown ends.
runningGatekeeper is calling the vendorWait. If it stays here, treat it as unknown.
succeededThe vendor accepted the changeNothing. The outcome is on the ticket.
failedThe call did not succeedRead the error code and explanation. Use Copy request id when reporting it. Request again makes a new request. Nothing is retried automatically.
expiredNot approved and executed in 15 minutes; nothing was sentRequest again if it is still needed.
unknownThe vendor may or may not have applied the changeCheck in the vendor's admin tool first. Then click Record what the vendor shows…, choose whether the change was applied, and enter your evidence. Do not request again until you have checked.
submittingThe request was sent but the answer was lostClick Re-check with Gatekeeper. This re-sends the same request and cannot create a duplicate.
stopped trackingYou cancelled the requestNothing. Request again if needed.

Cancel request only stops Frontline PSA from tracking and executing the request. Gatekeeper has no cancel, so the request stays there until it expires, but it cannot run without the requester pressing Execute.

Only the requester and tenant administrators see a request's parameters and reason. Other users see the action, target, status and times.

What is recorded

When a write finishes, Frontline PSA adds an internal note to the ticket with the action, target, tenant, who requested it, who approved it, the outcome and your reason. Passwords, secrets and raw vendor responses are never written to the note. Each request and execution is also recorded in the audit log.

Who can do what

With the default roles:

  • Technicians, dispatchers, managers and administrators can see tenants and run read actions.
  • Technicians, managers and administrators can request write actions.
  • Only administrators can link, pause or unlink tenants and bind RMM sites.