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

# Who it is for

> Who can use Hence during the pilot, which situations it fits, and who should not wait for it.

<Warning>
  **The pilot is not open.** While the execution layer is being built, running errands is limited to
  accounts on the company domain. Anyone may add the connector and complete the consent flow — the
  connection simply refuses to run tasks until access is enabled for the account. See
  [Connect](/connect/claude) for what that refusal looks like.
</Warning>

## The shape of person this fits

Hence is for someone who already knows roughly what needs doing and does not want to be the one
doing it: logging into four servicers to copy down APRs, working out whether a deferral rate is
actually capturing the whole match, filling a distribution form from two recordkeeper portals.

That means the first errands assume you have:

* **Online access to the accounts involved.** Hence signs in as you, through a single-use page you
  complete yourself. It does not open accounts, and it does not recover logins for you.
* **US accounts.** The first errands are US consumer credit and US employer retirement plans. Rules,
  forms and the plan mechanics are jurisdiction-specific, and the errands say so.
* **A reason to delegate rather than to be advised.** If what you want is an explanation, that is a
  different job, and a good assistant can already do it.

## Who should not wait for this

* **Anyone in an active dispute that has become legal.** A debt lawsuit, identity theft or
  insolvency is a hard stop. Hence refuses and points you at a professional, and that is the correct
  answer rather than a limitation to work around.
* **Anyone who needs money moved.** Hence does not move money between accounts. Nothing in the
  current errand set does, and the boundary is structural rather than a missing feature.
* **Anyone who needs something signed today.** Signatures, elections, spousal consent and identity
  proofing are yours. An errand can get you to the moment of signing; it cannot take it from you.

## Access during the pilot

Access is decided on our side, for your account, at the moment a tool is called — not by who holds
an invite link and not by your assistant. The practical consequences:

1. **Adding the connector always works.** The consent flow will succeed for any Hence account.
2. **Running an errand may not.** If access is not enabled, every tool refuses cleanly and tells you
   so, with a link to request access. Nothing half-runs.
3. **Nothing needs redoing when access arrives.** The connection you already made starts working.

<Note>
  **Whether a new user can sign up directly, or must be invited, is not settled yet.** The Hence app
  gates access by list today. This page will state the answer plainly once it is decided; until
  then, see the account step on [Connect Claude](/connect/claude).
</Note>