# Introduction

Biuwer applies an **access refusal criteria by default**. This means that a user has no access to anything as soon as it is created, nor does he or she have permission to create or edit content, and another user has to enable him or her to do so.

Permissions obtained through roles have priority, as they are horizontal. For example, the "Content Viewer'' role in Biuwer has read-only access to all the content of the Organization.

The management of Users, Groups of Users and Roles is done from the administration panel of the Organization.

![Access to the Administration Area in Biuwer](/files/-MN-1SrSl3LA_WilWyS8)

Below is a Security Diagram of the Biuwer platform, with which we try to explain how to specify who can do what.

![Security diagram of the Biuwer platform](/files/-MQkrteZad3YVRnooWkU)

These are the 3 basic principles of the security system for any organization using Biuwer:

1. **Default access refusal** criteria.
2. Any action is performed by, or on behalf of a user.
3. There are two approaches to assigning permissions: **platform permissions** (horizontal, very powerful but dangerous) and **object permissions** (individual, more controlled but can be tedious).


---

# 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.biuwer.com/security-management/introduction.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.