> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/creating-user-groups.md).

# Creating User groups

#### ***Applies to version v2.9, v2.10, v3.0***

One or more user groups can be created to define access rights, such as read only, read/write, or no access at all. Access rights can be assigned to all regions of the web portal or to specific areas.

**To create a user group:**

1- Click **Users** in the navigation panel.

![Users Navigation Panel A](https://docs.telcobridges.com/w/images/2/2d/Users_Navigation_Panel_A.png)

2- Select the **User Groups** tab and click **Create New User Groups**, to add a new user group.

![Users CreateNewUserGroup B](https://docs.telcobridges.com/w/images/f/f7/Users_CreateNewUserGroup_B.png)

3- Assign a name to the user group in the **Name** field.

![Users AssignNewUserGroup B](https://docs.telcobridges.com/w/images/4/4d/Users_AssignNewUserGroup_B.png)

4- Configure the access for the user group by one of the following two methods:

4a- Select an Authorization type, from the **Apply All** field , such as:

* Read
* Read/Write
* No access

This will apply the authorization to all regions of the web portal.

4b- Customize authorization and access individually by setting the authorization type in each web portal field.

![Users CustomizeNewUserGroup B](https://docs.telcobridges.com/w/images/a/a8/Users_CustomizeNewUserGroup_B.png)

5- Click **Create**.

**Path**

```
/user_groups/@[user_group_name]
```

**Parameters (text)**

```
/user_groups/@[user_group_name]
name                   = @[user_group_name]

/user_groups/@[user_group_name]/authorization_sections
1+1                   = "Read"
applications          = "Read"
audio_prompts         = "Read"
backups               = "Read"
bits_clock_interfaces = "Read"
call_trace            = "Read"
cas                   = "Read"
clocking              = "Read"
configurations        = "Read"
file_db               = "Read"
gateway               = "Read"
h.248                 = "Read"
hardware_units        = "Read"
hosts                 = "Read"
ip_interfaces         = "Read"
isdn                  = "Read"
isup                  = "Read"
iua                   = "Read"
lawful_interception   = "Read"
logs                  = "Read"
m2pa                  = "Read"
m2ua                  = "Read"
m3ua                  = "Read"
mtp2                  = "Read"
mtp3                  = "Read"
nap_columns           = "Read"
naps                  = "Read"
nats                  = "Read"
packages_and_licenses = "Read"
point_codes           = "Read"
profiles              = "Read"
radius                = "Read"
report                = "Read"
routes                = "Read"
routesets             = "Read"
routing_script        = "Read"
sccp                  = "Read"
sctp                  = "Read"
services              = "Read"
sip                   = "Read"
statistics            = "Read"
status                = "Read"
system                = "Read"
tcap                  = "Read"
tdm_line_interfaces   = "Read"
test_call             = "Read"
users                 = "Read"
```

**Parameters (json)**

```
{
  "authorization_sections" : {
    "1+1" : "Read",
    "applications" : "Read",
    "audio_prompts" : "Read",
    "backups" : "Read",
    "bits_clock_interfaces" : "Read",
    "call_trace" : "Read",
    "cas" : "Read",
    "clocking" : "Read",
    "configurations" : "Read",
    "file_db" : "Read",
    "gateway" : "Read",
    "h.248" : "Read",
    "hardware_units" : "Read",
    "hosts" : "Read",
    "ip_interfaces" : "Read",
    "isdn" : "Read",
    "isup" : "Read",
    "iua" : "Read",
    "lawful_interception" : "Read",
    "logs" : "Read",
    "m2pa" : "Read",
    "m2ua" : "Read",
    "m3ua" : "Read",
    "mtp2" : "Read",
    "mtp3" : "Read",
    "nap_columns" : "Read",
    "naps" : "Read",
    "nats" : "Read",
    "packages_and_licenses" : "Read",
    "point_codes" : "Read",
    "profiles" : "Read",
    "radius" : "Read",
    "report" : "Read",
    "routes" : "Read",
    "routesets" : "Read",
    "routing_script" : "Read",
    "sccp" : "Read",
    "sctp" : "Read",
    "services" : "Read",
    "sip" : "Read",
    "statistics" : "Read",
    "status" : "Read",
    "system" : "Read",
    "tcap" : "Read",
    "tdm_line_interfaces" : "Read",
    "test_call" : "Read",
    "users" : "Read"
  },
  "name" : @[user_group_name]
}
```


---

# 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://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/creating-user-groups.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.