> For the complete documentation index, see [llms.txt](https://lightpaper.polyversity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lightpaper.polyversity.io/polyversity-light-paper/roles-and-responsibilities/world-web-administrators.md).

# World/Web Administrators

### &#x20;WORLD/WEB ADMINISTRATORS <a href="#docs-internal-guid-03a4f149-7fff-c82d-03a8-6411d2665beb" id="docs-internal-guid-03a4f149-7fff-c82d-03a8-6411d2665beb"></a>

&#x20;This is a role designated to a select handful who will be responsible for developing the entire world as a whole. WAs include the development team for both the  website and metaverse, as well as management. This role is to be used sparingly since WAs have the ability to make sweeping changes to the entire platform.

&#x20;

WA privileges include but are not limited to:

&#x20;

1\. Creating new land parcels and regions in the virtual world and administering them globally.

2\. Altering the landscape, ambience, time of day and controls across every parcel in the world.

3\. Administration of public spaces such as the Genesis plazas and public teleport locations.

4\. Broadcasting world-wide announcements, updates, notifications and communications.

5\. World security: Complete control over all user profiles and addressing/resolving complaints.

6\. Technology: Platform updates, maintenance and upkeep of all spaces across the world.

7\. Support: Addressing complaints, service requests and user suggestions.

&#x20;

Post MVP, we would need to break down the WA tasks to separate teams that are responsible for specific areas like security, policing, maintenance, communications and others.

<br>


---

# 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://lightpaper.polyversity.io/polyversity-light-paper/roles-and-responsibilities/world-web-administrators.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.
