# Models that stay in the institution (https://docs.akollo.com/en/ai/local-models)



An administrator can run the small assistant models on a machine the institution controls. The product sends a
request only to an address the administrator has configured.

| Where the model runs               | How it behaves                                                                                                                                                        |
| ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| A machine the institution controls | Receives requests only at the address the administrator configured                                                                                                    |
| A cloud CPU service                | Serves one model. It checks the model file before it answers, does not start until the administrator has set a key, and listens only on the port the platform assigns |
| A developer machine                | The local model service accepts connections only from that machine                                                                                                    |

<Mermaid
  title="How a request reaches a local model"
  chart="`flowchart LR
A[Akollo] -->|Only to the configured address| B[Model service]
B --> C[Suggestion]
C --> D{Manager or agent accepts?}
D -->|Yes| E[Record changes]
D -->|No| F[Nothing changes]`"
/>

People still see suggestions, not automatic changes. A manager or an agent accepts anything that would change a
record.

## Night notes [#night-notes]

After the organisation's night run, a project page can show a short note about that project, and **My insights**
can show a short note about your timesheet day.

* No note is stored while the organisation has the assistant switched off, or while an emergency stop is on.
* Each note is a suggestion. It does not change the project, the timesheet or anyone's record.
* A support session can read a project note and cannot change it.

<Callout type="info" title="Note">
  If your organisation switches the assistant off or turns on an emergency stop, no new night notes are stored.
</Callout>

## Describing a flow [#describing-a-flow]

On the automations page, and inside a flow, you can describe what the flow should do in your own words.

<Steps>
  <Step>
    ### Describe the flow [#describe-the-flow]

    Open the automations page, or open a flow, and write what the flow should do.
  </Step>

  <Step>
    ### Review the suggestion [#review-the-suggestion]

    You see a suggestion and what it would change.
  </Step>

  <Step>
    ### Save a draft [#save-a-draft]

    Saving keeps a draft. The flow does not start, and nothing is published.
  </Step>

  <Step>
    ### Publish later yourself [#publish-later-yourself]

    The flow starts only when you publish it yourself later.
  </Step>
</Steps>

A support session can see the box and cannot ask for a suggestion.

## FAQ [#faq]

<Accordions type="single">
  <Accordion title="Where does Akollo send requests for a local model?">
    Only to the address the administrator has configured.
  </Accordion>

  <Accordion title="Can a night note change my timesheet?">
    No. Each note is a suggestion. It does not change the project, the timesheet or anyone's record.
  </Accordion>

  <Accordion title="Why is there no night note today?">
    No note is stored while the organisation has the assistant switched off, or while an emergency stop is on.
  </Accordion>

  <Accordion title="Does a described flow start running when I save it?">
    No. Saving keeps a draft. The flow does not start, and nothing is published, until you do that yourself later.
  </Accordion>
</Accordions>

## Related pages [#related-pages]

* [Running the model in the institution](/en/ai/on-prem)
* [AI connections](/en/ai/connections)
* [Automation](/en/product-guide/automation)