Skip to main content
Questions about Microsoft 365, GDAP and the service account are in the Microsoft and GDAP FAQ.

Common questions: where to start, clients that aren't ready, ticketing, one client's settings and a failed run (1:26).

Getting started

By invitation from your Triggr account manager or a colleague. Sign in at core.triggr-app.com with Continue with Microsoft or your email address. If Core says Triggr Core isn’t enabled for your organisation, ask your account manager.
Work through Get set up in ~20 minutes on Home, in order, or click Set up with the assistant. See Set up Triggr Core.
No. Ticketing stays off on each workflow until you turn it on under Execution config. Core works with ConnectWise PSA, Halo PSA and Autotask; see Connect your PSA.
Yes: on Home, click Review next to Connect your PSA. See Change it later.

Clients

Import them from Partner Center while you connect Microsoft 365, or later from Clients with Import or Add client. See Add your clients.
Something stops that client being ready. Click the client: Readiness shows the button that fixes it, such as Link to GDAP, Add tenant ID or Map to your PSA. See Fix what’s not ready.
Cloud Only for Microsoft 365-only clients. The other types are for clients with on-premises Active Directory and need the desktop agent on a domain-joined Windows server.

Workflows and forms

Yes. Open it from Config, choose the client in the scope dropdown, click Override on the card, change it and save. Reset returns it to the default. See Settings for each client.
Open it from Config and set the dropdown by its name to Disabled. Internal only, Public form only and Internal + public control who can run it.
Through your public forms, signing in with their Microsoft work account. Triggr matches their Microsoft tenant ID to the client, so each client needs its tenant ID set on Clients. See How Triggr Core works and Share your forms.
Yes. On the workflow’s Restrict access tab, turn on Restrict to group membership and add the group’s display name; Core checks membership in each client’s directory, including nested groups.
The client’s Microsoft tenant ID in Core doesn’t match the tenant their account is in. Correct it on Clients.
A technician running the form in Core sees it once. For public forms, set up Credential delivery on User Onboarding; see Set up User Onboarding.
Yes. Turn on Start date scheduling on User Onboarding’s Execution config.
Yes: Bulk Staff Offboarding, Bulk Update User Details, Grant Mailbox Permission in Bulk and Bulk Add / Remove Users to Group. See the workflow catalogue.
Set its Approval to Internal, submit the form, then reject the request on Approvals. Nothing runs in the tenant until a request is approved, though a PSA ticket is still raised if Ticketing is on.
Build it in Triggr Studio.

Approvals and runs

Set the workflow’s Approval card to Internal (a teammate or group decides on Approvals) or External (the client’s approver decides from an emailed link). See Approvals.
Yes, with Let the approver edit the request on in the Approval card. See Approvals.
On Executions: click the run. A failed run opens on Why it failed, with the cause and how to fix it.
A ticketing problem never stops the work. Open the run for the cause, then create the ticket.
The client’s Microsoft access is missing something. Click How to fix, or see Health checks and repairs.

Your team

Manage members, set up clients’ Microsoft access, Repair GDAP health, and manage Settings > Alerts, API keys and Webhooks. See Invite your team.
Yes. Set up internal approvers from Home, or create a group in Settings > User groups and choose Internal > Group on the workflow’s Approval card.

Email, reports, licences and integrations

Yes, through Pax8, Sherweb or TD SYNNEX StreamOne Stellr. See Buy seats automatically.
Yes, with API keys and webhooks. See API and webhooks.
Turn on GDAP alerts for a daily or weekly digest. Core also checks every GDAP client overnight, fixes what it can by itself, and marks any client that needs you; see Fix Microsoft connection problems.