> For the complete documentation index, see [llms.txt](https://www.xrdev.app/mixed-reality-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.xrdev.app/mixed-reality-docs/lessons/lesson-7/what-could-go-wrong.md).

# What could go wrong?

### Can one user access to another user's anchors?

Yes, if you build you can prevent that from happening. You can implement Authentication in your application and check for permission before you respond to an API call for Anchors. [Read more...](< https://docs.microsoft.com/azure/spatial-anchors/concepts/authentication?tabs=csharp\&WT.mc_id=github-mixedrealitycurriculum-ayyonet>)

### What effects the accuracy of the Spatial Anchors?

Lighting, people moving arround and the changing environment can reduce the retreivability of the anchors. Finding contrasting colored an unchanged object and starting the session from there would be helpful.&#x20;

### I can't retrieve my placed anchors, what can I do?

You can retreive a nearby anchor and ask for the other anchors in a radius.&#x20;

### How can I have access to my anchor offline?

You can store your Spatial Cloud Anchors as local anchors in your device.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.xrdev.app/mixed-reality-docs/lessons/lesson-7/what-could-go-wrong.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.