> ## Documentation Index
> Fetch the complete documentation index at: https://university.triggr-app.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](/core/reference/microsoft-faq).

## Getting started

<AccordionGroup>
  <Accordion title="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>

  <Accordion title="Where do I start?">
    Work through Get set up in \~20 minutes on Home, in order. See [Set up Triggr Core](/core/get-started/overview).
  </Accordion>

  <Accordion title="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](/core/get-started/connect-your-psa).
  </Accordion>

  <Accordion title="Can I change PSA, or its credentials, later?">
    Yes: on Home, click **Review** next to Connect your PSA. See [Change it later](/core/get-started/connect-your-psa#change-it-later).
  </Accordion>
</AccordionGroup>

## Clients

<AccordionGroup>
  <Accordion title="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](/core/get-started/add-your-clients#add-clients).
  </Accordion>

  <Accordion title="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](/core/get-started/add-your-clients#fix-whats-not-ready).
  </Accordion>

  <Accordion title="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](/core/get-started/add-your-clients#deploy-the-desktop-agent) on a domain-joined Windows server.
  </Accordion>
</AccordionGroup>

## Workflows and forms

<AccordionGroup>
  <Accordion title="Can a workflow work differently for one client?">
    Yes. Open it from Config, choose the client in the scope dropdown and click **Override** on the card; Reset returns it to the default. See [Settings for each client](/core/get-started/configure-user-onboarding#settings-for-each-client).
  </Accordion>

  <Accordion title="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>

  <Accordion title="How do our clients' staff submit requests?">
    Through your public forms, signing in with their Microsoft work account. Each client needs its Microsoft tenant ID set on Clients. See [Share your forms](/core/get-started/share-your-forms).
  </Accordion>

  <Accordion title="Can the forms use our own domain?">
    Yes. See [Use your own domain](/core/get-started/add-your-branding#use-your-own-domain-optional).
  </Accordion>

  <Accordion title="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>

  <Accordion title="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>

  <Accordion title="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](/core/get-started/configure-user-onboarding#set-up-user-onboarding).
  </Accordion>

  <Accordion title="Can onboarding wait until the start date?">
    Yes. Turn on **Start date scheduling** on User Onboarding's Execution config.
  </Accordion>

  <Accordion title="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](/core/reference/workflow-catalogue).
  </Accordion>

  <Accordion title="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>

  <Accordion title="Can I add a workflow that isn't in the catalogue?">
    Build it in [Triggr Studio](/studio/introduction).
  </Accordion>
</AccordionGroup>

## Approvals and runs

<AccordionGroup>
  <Accordion title="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](/core/use/approvals).
  </Accordion>

  <Accordion title="Can the approver fix a mistake in a request?">
    Yes, with Let the approver edit the request on in the Approval card. See [Approvals](/core/use/approvals#set-it-up).
  </Accordion>

  <Accordion title="Where do I see what a run did, or why it failed?">
    On [Executions](/core/use/executions): click the run, then a step.
  </Accordion>

  <Accordion title="Why did a run's Create Ticket step fail when the user was still created?">
    A ticketing problem never stops the work. See [Executions](/core/use/executions#troubleshooting) for the two common causes.
  </Accordion>

  <Accordion title="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](/core/reference/microsoft-faq#health-checks-and-repairs).
  </Accordion>
</AccordionGroup>

## Your team

<AccordionGroup>
  <Accordion title="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](/core/get-started/invite-your-team).
  </Accordion>

  <Accordion title="Can approvals go to a team rather than one person?">
    Yes. Create a group in **Settings > User groups**, then choose Internal > Group on the workflow's Approval card.
  </Accordion>
</AccordionGroup>

## Email, reports, licences and integrations

<AccordionGroup>
  <Accordion title="Can approval emails come from our own address?">
    Yes. See [Send client emails from your own address](/core/get-started/add-your-branding#send-client-emails-from-your-own-address-optional).
  </Accordion>

  <Accordion title="Can clients get a regular licensing report?">
    Yes, monthly. See [Schedule a monthly licensing report](/core/use/reports#schedule-a-monthly-licensing-report).
  </Accordion>

  <Accordion title="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](/core/manage/licences-and-distributors#buy-seats-automatically).
  </Accordion>

  <Accordion title="Can we connect Core to our own portal or tools?">
    Yes, with API keys and webhooks. See [API and webhooks](/core/manage/api-and-webhooks).
  </Accordion>

  <Accordion title="How do we hear about broken Microsoft access before a run fails?">
    Turn on [GDAP alerts](/core/manage/gdap-alerts) for a daily or weekly digest. Core also checks every GDAP client overnight.
  </Accordion>
</AccordionGroup>


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