> For the complete documentation index, see [llms.txt](https://digitals-private-organization.gitbook.io/rizones45678.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://digitals-private-organization.gitbook.io/rizones45678.org/mobile-app-guide/open-your-club.md).

# Open your club

How the club screen is organised, and the add, edit and delete pattern used throughout.

On the Home screen, under **My Connections**, there is a tile for each club and district you are attached to. Every tile carries a role badge (**Club Admin** or **District Admin**), the club or district name, and its member count. If you administer several clubs, you see several tiles. Tap your club's tile to open it.

## How the club screen is organised

Inside, the features are grouped under headings, in this on screen order:

|   | Section                                                                                                        | What it holds                               |
| - | -------------------------------------------------------------------------------------------------------------- | ------------------------------------------- |
| 1 | [Master Modules](/rizones45678.org/mobile-app-guide/master-modules.md)                                         | Day to day club records and communication.  |
| 2 | [Avenues of Service & Public Image](/rizones45678.org/mobile-app-guide/avenues-of-service-and-public-image.md) | Projects under the six service avenues.     |
| 3 | [Payments](/rizones45678.org/mobile-app-guide/payments.md)                                                     | Credits, dues and your club website.        |
| 4 | [E-Governance & Reporting](/rizones45678.org/mobile-app-guide/e-governance-and-reporting.md)                   | Attendance, awards, reports and compliance. |

## The everyday pattern

This works almost everywhere in the app.

{% stepper %}
{% step %}

### Add

Open the feature, tap the **+ (Add)** button, fill the form, then tap **Save**.
{% endstep %}

{% step %}

### Edit

Tap the item, or its pencil or three dots menu, change it, then tap **Save** or **Update**.
{% endstep %}

{% step %}

### Delete

Open the item's three dots menu, or its delete or trash icon, tap **Delete**, then confirm.
{% endstep %}
{% endstepper %}


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://digitals-private-organization.gitbook.io/rizones45678.org/mobile-app-guide/open-your-club.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 `build a script that syncs our docs to a CMS` 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.