> For the complete documentation index, see [llms.txt](https://bloxroar.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bloxroar.gitbook.io/docs/staff/lr+-information.md).

# LR+ Information

What LR+ staff do and what's expected of them.

LR+ means **Low Rank and above**. These are the staff members who keep BloxRoar Shopping running day to day. Every higher rank also follows everything on this page.

{% hint style="info" %}
This page is a draft written for a store that is still being built. Staff leadership may update duties and requirements as the game grows.
{% endhint %}

## Your role

LR staff are the friendly face of the store. You help players find their way around, answer simple questions and keep the shop feeling welcoming.

## Core duties

* Greet players and help them find what they're looking for
* Answer basic questions about the game, the shops and how to play
* Keep your area of the store tidy and in working order
* Report bugs, broken items and rule-breaking to a higher rank
* Stay active during your shifts

## Expectations

{% stepper %}
{% step %}

### Be professional

Stay polite and helpful, even when a player is rude. Never argue with players.
{% endstep %}

{% step %}

### Follow the rules

You must follow the [community rules](/docs/community-and-rules.md) and the Roblox Community Standards at all times.
{% endstep %}

{% step %}

### Ask when unsure

If you don't know what to do, ask a higher-ranked staff member rather than guess.
{% endstep %}

{% step %}

### Protect accounts

Never share your password or login code with anyone, and never ask a player for theirs.
{% endstep %}
{% endstepper %}

## What LR staff cannot do

* Punish or remove players on their own
* Change game settings or give out items without permission
* Promote, demote or discipline other staff
* Share private staff information outside the staff team

## Handling problems

| Situation                     | What to do                                                   |
| ----------------------------- | ------------------------------------------------------------ |
| A player breaks a rule        | Give a calm reminder, then report it to an MR+ member        |
| A player is upset or confused | Be patient and point them to the [FAQ](/docs/faq.md)         |
| You find a bug                | Report it in the staff channel on Discord with what happened |
| You're not sure what to do    | Ask a higher rank                                            |

## Moving up

Promotions are based on activity, behavior and how well you do your duties. Staff are chosen by higher ranks, so asking repeatedly will not speed it up. Do your job well and it will be noticed.

Next rank: [MR+ Information](/docs/staff/mr+-information.md)


---

# 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://bloxroar.gitbook.io/docs/staff/lr+-information.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.