# Work in public

<figure><img src="?path=%2Ffiles%2F2ri0SFC1tMj7YGW4HlXA" alt=""><figcaption></figcaption></figure>

#### Metanet: Open and Transparent Public Group Chats <a href="?path=%23corela-open-and-transparent-public-group-chats" id="corela-open-and-transparent-public-group-chats"></a>

Metanet allows you to connect with your audience through open, transparent public group chats.

Case Study: The Metanet Team Our development team is active on Metanet every day, often engaging in the /metanet community.

In our community channels, we have public spaces open for everyone to view. These channels are set to "Read-only," meaning anyone can observe the conversations, but only team members can post.

For interactive engagement, our Q\&A channel is open for both reading and posting. This setup fosters a strong feedback loop with our most dedicated supporters and collaborators.

For private discussions, we utilize several private channels to handle user-specific information, financial planning, and other sensitive topics that require confidentiality.


---

# Agent Instructions: 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:

```
GET https://metanet.gitbook.io/metanet/how-to-use-metanet/how-to-use-metanet/work-in-public.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.