> For the complete documentation index, see [llms.txt](https://docs.gmetri.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gmetri.com/metaverse/player/it-permissions/whitelisting-for-editing-experiences.md).

# Whitelisting for Editing Experiences

If you are unable to view Experiences on GMetri on certain networks, which is commonly the case on corporate and university networks, it may be required to whitelist GMetri's servers and ports so that they are not blocked by the firewall. 

## Essential

These domains cover the bare minimum domains that need to be whitelisted for any GMetri experience to run.

1. `*.gmetri.com`
2. `*.vrgmetri.com`
3. `*.s3.amazonaws.com` For uploading files from the editor

## Recommended

In addition to the above list, you will need to additionally whitelist the below domains

1. `*.paddle.com` Subscription and Billing management
2. `*.flickr.com, *.staticflickr.com` Integration with Flickr
3. `*.sketchfab.com` Integration with Sketchfab
4. `*.googleapi.com, developers.google.com, *.google.com, *.gstatic.com` Maps, location-based analytics

We use ReadyPlayerMe as our 3D avatar provider. Users can log in to their own RPM account and import their avatars into GMetri, our create a new one as guests. 

1. `readyplayer.me`
2. `cname.vercel-dns.com`
3. `avatars.readyplayer.me`
4. `d1a370nemizbjq.cloudfront.net`

## Optional Services

We use a number of services to keep GMetri systems functional and support advanced features.

### Google SSO / Location Tracking (Optional)

These are required for Google SSO and location tracking. These are optional but are required is you're looking to use Social and Google Auth for your GMetri Experiences

1. `*.googleapis.com`
2. `developers.google.com`

### Help / Support (Optional)

These are required for any remote debugging issues at the user's end. We use Trackjs to collect any errors reported on users' devices and Calendly to book meetings.

1. `*.trackjs.com`
2. `calendly.com`


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.gmetri.com/metaverse/player/it-permissions/whitelisting-for-editing-experiences.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.