# Creating a read-only channel using SOGS
Some SOGS operators may want to set up a room on their SOGS which features one way style communication; these rooms allow moderators and administrators to update the room with new messages, but disallows unprivileged users to send new messages. These sorts of rooms can be useful for providing updates or information.
#### 1. Create a new room
```
sogs --add-room TOKEN --name "NAME" --description "DESCRIPTION"
```
{% hint style="success" %}
Skip to step 3 if you already have a room and you are an administrator in that room
{% endhint %}
Replace `TOKEN` with the address to use in the room URL (which must consist of **ONLY** lowercase letters, numbers, underscores, or dashes), replace `NAME` with the room name to display in Session and optionally replace `DESCRIPTION` with a short description of the topic of the room.
#### 2. Ensure you are an administrator of the room
```
sogs --room TOKEN --admin --add-moderator ACCOUNTID
```
Replacing `TOKEN` with the room token you created in step 1, and replacing `ACCOUNTID` with your own Account ID.
#### 3. Alter room permissions
There are 4 types of permission currently available in rooms
* r = Read (ability to read messages)
* w = Write (ability to write new messages)
* u = Upload (ability to upload attachments, including files, voice notes, images and videos)
* a = Access (ability to join the room)
When modifying these permissions changes will only apply to non admins/moderators, the default permissions in a room will be "rwua" for all users
To create a read only group we want to remove regular users ability to write and upload attachments, we can do this using the following command:
```
sogs --add-perms ra --remove-perms wu --room TOKEN
```
This command will ensure read and access permissions are provided and remove write and upload permissions for regular users.
As the permission changes do not affect administrators and moderators, they will still be able to read, write and upload to the group. New Account ID's can be given write/upload access by making those Account ID's moderator or admin, this can be done directly in the Session Desktop client or via the[ CLI](https://github.com/oxen-io/session-pysogs/blob/dev/administration.md).
---
# 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://docs.getsession.org/readme/advanced-features/communities/creating-a-read-only-channel-using-sogs.md?ask=
```
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.