---
id: KB-MA-018
url: https://app.codecontract.io/help/marta/how-far-what-marta-sees-reaches
idioma: en
categoria: marta
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-MA-003, KB-MA-008, KB-MA-020]
citadoPor: [KB-MA-012]
---

# How far what Marta sees reaches

_It searches your organisation's material, not your user's. The difference matters more than it looks._

**Responde a:** can marta see every document · can it see a document that is not mine · do permissions affect what it answers · what is the assistant's scope

It is the first question anyone with responsibility asks: how far does it reach. And the answer matters because it is not the intuitive one — people assume it answers with «your stuff», when in fact it searches the organisation's.

## Where the limits really are

| Limit | Exists | What it means |
| --- | --- | --- |
| Your organisation | Yes, and it is the hard limit | It does not reach another company's, even with a shared supplier |
| Whatever is inside the organisation | That is where it searches | Including material that person would not open on their own |
| What you make up in the question | It does not fill in | If it is not stored, it does not know it |
| What was deleted | Out of reach | What was withdrawn does not come back by asking |

> [!IMPORTANT]
> That second point is the one to settle before opening it to the whole team: **asking is a way of searching, and it searches the organisation as a whole**. If some material should not be within everyone's reach, the control is where it lives and who has access to that part — not the hope that nobody asks about it. It is exactly the criterion you apply to a shared folder, applied to a conversation.

## What you do about it, in practice

**En corto**

- Decide where sensitive material lives before opening the assistant to the team.
- And do not use «nobody knows about it» as access control: it never was.
- What does depend on the person: what they can do with what they find.
- Searching and acting are different things, and the second carries its own permissions.

> [!WARNING]
> There is another reach that surprises more, and it is that of instructions: **what is saved «for the whole organisation» changes other people's answers**. If someone states that reports should always follow a particular criterion, that applies too to whoever asks tomorrow without knowing the instruction exists. It is not a fault — it is what lets the assistant work the way the house works — but those instructions deserve an owner and a review, like any other shared setting.

## How to check it for yourselves

1. **Ask about something that only sits in one specific folder** — Whether it turns up tells you more than any explanation.
2. **Repeat the test with a lower-permission user** — That shows where the real line sits in your account.
3. **And review which instructions are saved for everyone** — They pile up without anyone rereading them.

> [!NOTE]
> What gets processed, what leaves your organisation and what can be switched off is a separate conversation, explained elsewhere. This is only about the reach of the search.

**Can it see another organisation's material?**

No. That is the line that is not crossed.

**What if I delete a document?**

It stops being available to answer with.

**Is there a record of what it is asked?**

Yes, and it is worth knowing before asking anything.

## Ejemplos

**A company wants to open the assistant to the whole team and hesitates over HR documents.**

- Moves them to a restricted area first, then checks by asking

→ The reach of the answers matches the access it had already decided, not luck.

**A file you have no access to is asked about.**

- Checks the scope before relying on it

→ The answer is read knowing what it covers.

**The answer looks incomplete.**

- Checks which files it can see

→ The omission is explained.

**It is expected to see documents from another organisation.**

- Checks which one the question is coming from

→ The confusion clears.

**A user sees more than they should in an answer.**

- Reviews their permissions

→ The scope matches the role.

**An answer is shared with somebody outside.**

- Checks what information it contains

→ No more goes out than should.