> ## Documentation Index
> Fetch the complete documentation index at: https://kb.mspprocess.com/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> Quick answers to common questions about setting up and running Triggr Core: clients, your PSA, forms, approvals, your team, reports and licences.

Questions about Microsoft 365, GDAP and the service account are in the [Microsoft and GDAP FAQ](https://kb.mspprocess.com/core/reference/microsoft-faq.md).

<video controls preload="none" playsInline poster="/images/videos/core-faq.jpg" src="https://mintcdn.com/triggr/qlzU2ZPfGS3YFsZy/images/videos/core-faq.mp4?fit=max&auto=format&n=qlzU2ZPfGS3YFsZy&q=85&s=6773dcaa5811bf94d54802a350927c8c" />

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

## Getting started

> [accordion] How do I get a Triggr Core account?
>
> By invitation from your Triggr account manager or a colleague. Sign in at [core.triggr-app.com](https://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.

> [accordion] Where do I start?
>
> Work through Get set up in \~20 minutes on Home, in order, or click **Set up with the assistant**. See [Set up Triggr Core](https://kb.mspprocess.com/core/get-started/overview.md).

> [accordion] Do I need a PSA?
>
> 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](https://kb.mspprocess.com/core/get-started/connect-your-psa.md).

> [accordion] Can I change PSA, or its credentials, later?
>
> Yes: on Home, click **Review** next to Connect your PSA. See [Change it later](https://kb.mspprocess.com/core/get-started/connect-your-psa.md#change-it-later).

## Clients

> [accordion] How do I add my clients?
>
> Import them from Partner Center while you connect Microsoft 365, or later from Clients with Import or Add client. See [Add your clients](https://kb.mspprocess.com/core/get-started/add-your-clients.md#add-clients).

> [accordion] What do Not linked, No tenant ID and Not mapped mean?
>
> 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](https://kb.mspprocess.com/core/get-started/add-your-clients.md#fix-whats-not-ready).

> [accordion] Which environment type should a client have, and when do I need the agent?
>
> Cloud Only for Microsoft 365-only clients. The other types are for clients with on-premises Active Directory and need the [desktop agent](https://kb.mspprocess.com/core/get-started/add-your-clients.md#deploy-the-desktop-agent) on a domain-joined Windows server.

## Workflows and forms

> [accordion] Can a workflow work differently for one client?
>
> 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](https://kb.mspprocess.com/core/get-started/configure-user-onboarding.md#settings-for-each-client).

> [accordion] How do I stop offering a workflow?
>
> 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.

> [accordion] How do our clients' staff submit requests?
>
> 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](https://kb.mspprocess.com/core/how-core-works.md) and [Share your forms](https://kb.mspprocess.com/core/get-started/share-your-forms.md).

> [accordion] Can the forms use our own domain?
>
> Yes. See [Use your own domain](https://kb.mspprocess.com/core/get-started/add-your-branding.md#use-your-own-domain-optional).

> [accordion] Can I limit who at a client can use a form?
>
> 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.

> [accordion] A client's staff see “These requests aren't available”
>
> The client's Microsoft tenant ID in Core doesn't match the tenant their account is in. Correct it on Clients.

> [accordion] Who gets a new starter's temporary password?
>
> 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](https://kb.mspprocess.com/core/get-started/configure-user-onboarding.md#set-up-user-onboarding).

> [accordion] Can onboarding wait until the start date?
>
> Yes. Turn on **Start date scheduling** on User Onboarding's Execution config.

> [accordion] Can I run a workflow for several users at once?
>
> Yes: Bulk Staff Offboarding, Bulk Update User Details, Grant Mailbox Permission in Bulk and Bulk Add / Remove Users to Group. See the [workflow catalogue](https://kb.mspprocess.com/core/reference/workflow-catalogue.md).

> [accordion] How do I test a workflow without changing anything in Microsoft 365?
>
> 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.

> [accordion] Can I add a workflow that isn't in the catalogue?
>
> Build it in [Triggr Studio](https://kb.mspprocess.com/studio/introduction.md).

## Approvals and runs

> [accordion] How do approvals work?
>
> 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](https://kb.mspprocess.com/core/use/approvals.md).

> [accordion] Can the approver fix a mistake in a request?
>
> Yes, with Let the approver edit the request on in the Approval card. See [Approvals](https://kb.mspprocess.com/core/use/approvals.md#set-it-up).

> [accordion] Where do I see what a run did, or why it failed?
>
> On [Executions](https://kb.mspprocess.com/core/use/executions.md): click the run. A failed run opens on Why it failed, with the cause and how to fix it.

> [accordion] Why did a run's Create Ticket step fail when the user was still created?
>
> A ticketing problem never stops the work. Open the run for the cause, then [create the ticket](https://kb.mspprocess.com/core/use/executions.md#create-a-missing-ticket).

> [accordion] The run form warns that something “will fail for” a client
>
> The client's Microsoft access is missing something. Click **How to fix**, or see [Health checks and repairs](https://kb.mspprocess.com/core/reference/microsoft-faq.md#health-checks-and-repairs).

## Your team

> [accordion] What can admins do that members can't?
>
> Manage members, set up clients' Microsoft access, Repair GDAP health, and manage Settings > Alerts, API keys and Webhooks. See [Invite your team](https://kb.mspprocess.com/core/get-started/invite-your-team.md).

> [accordion] Can approvals go to a team rather than one person?
>
> Yes. [Set up internal approvers](https://kb.mspprocess.com/core/use/approvals.md#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

> [accordion] Can approval emails come from our own address?
>
> Yes. See [Send client emails from your own address](https://kb.mspprocess.com/core/get-started/add-your-branding.md#send-client-emails-from-your-own-address-optional).

> [accordion] Can clients get a regular licensing report?
>
> Yes, monthly. See [Schedule a monthly licensing report](https://kb.mspprocess.com/core/use/reports.md#schedule-a-monthly-licensing-report).

> [accordion] Can Core buy a licence seat when a client has none free?
>
> Yes, through Pax8, Sherweb or TD SYNNEX StreamOne Stellr. See [Buy seats automatically](https://kb.mspprocess.com/core/manage/licences-and-distributors.md#buy-seats-automatically).

> [accordion] Can we connect Core to our own portal or tools?
>
> Yes, with API keys and webhooks. See [API and webhooks](https://kb.mspprocess.com/core/manage/api-and-webhooks.md).

> [accordion] How do we hear about broken Microsoft access before a run fails?
>
> Turn on [GDAP alerts](https://kb.mspprocess.com/core/manage/gdap-alerts.md) 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](https://kb.mspprocess.com/core/reference/fix-microsoft-connection-problems.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.