> ## 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.

# How Triggr Core works

> Your techs run requests from Core, or your clients' staff submit them from a link, and Triggr recognises each client by its Microsoft tenant ID.

A request reaches a workflow one of two ways: your techs run it in Core, or your clients' staff submit it from a link you share.

```mermaid theme={null}
flowchart LR
  T["Your techs: Run a workflow"] --> W["The client's version of the workflow"]
  S["Client staff: open the form link"] --> M["Sign in with Microsoft"]
  M --> R["Tenant ID matched to a client"]
  R --> W
  W --> X["Work done in the client's Microsoft 365"]
```

Both routes record the request, raise a PSA ticket if ticketing is on, wait for approval if the workflow has one, then run the same workflow in the client's tenant. Every run appears in [Executions](https://university.triggr-app.com/core/use/executions.md).

## Your techs run it from Core

Anyone in your Core organisation clicks **Run a workflow**, picks the workflow and the client, and fills in that client's form. The workflow must be Internal only or Internal + public. See [Run a workflow](https://university.triggr-app.com/core/use/run-a-workflow.md).

## Your clients use a live login

Each public workflow has one link for every client, listed on Public forms. Their staff open it, click Sign in with Microsoft and sign in with their usual work account: no Triggr account, and Triggr never sees their password. To offer a workflow this way, set it to Public form only or Internal + public. See [Share your forms](https://university.triggr-app.com/core/get-started/share-your-forms.md).

## How Triggr knows the client

Every Microsoft 365 organisation has a tenant ID. When someone signs in, Triggr reads it and finds the client on Clients with the same Microsoft tenant ID. Nothing is set up per person: anyone at Acme Corp, with any Acme Corp account, gets Acme Corp's form. Partner Center import and Look up from domain fill in the tenant ID; see [Add your clients](https://university.triggr-app.com/core/get-started/add-your-clients.md). The messages a visitor sees when no client matches are in [Share your forms](https://university.triggr-app.com/core/get-started/share-your-forms.md#troubleshooting).

The tenant ID only recognises the client. To do the work, the client must also be connected: linked to GDAP, or approved by its admin with a per-client app. Otherwise the request is recorded and the run fails at its first Microsoft step; see [Fix Microsoft connection problems](https://university.triggr-app.com/core/reference/fix-microsoft-connection-problems.md).

## What the client's settings change

Triggr builds the form and runs the workflow with that client's settings: Base config, plus anything you've overridden for the client. See [Settings for each client](https://university.triggr-app.com/core/get-started/configure-user-onboarding.md#settings-for-each-client).

| Part | Uses the client's |
| - | - |
| Form | Questions, required fields, dropdown options and email domain |
| Approval | Approver: your team, or the client's own |
| Run | Licences, groups and shared mailboxes, ticketing, password delivery and on-premises AD |

Client staff see that a request needs approval, but never who approves it or what access it grants.

Next: [Set up Triggr Core](https://university.triggr-app.com/core/get-started/overview.md).


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