# Database Access Management

Within **Data & Content Management**, **Database Access Management** focuses on how data stored in databases is **segmented, governed, and made accessible** in a controlled and predictable manner.

ONEWEB uses **database schemas** and **security domains** to organize data access and enforce boundaries between different types of data and usage contexts.

***

#### **Schema‑Based Data Organization**

A **schema** represents a logical grouping of database objects such as tables, views, and procedures.

By using schemas, ONEWEB can:

* Separate application data by purpose or domain
* Organize transactional, reference, and configuration data
* Reduce accidental cross‑access between unrelated datasets
* Support cleaner data structure and ownership

Schema‑based organization improves readability, maintainability, and long‑term data governance.

***

#### **Security Domains for Access Control**

**Security domains** define how access to database resources is restricted and controlled.

In ONEWEB, security domains are used to:

* Limit which users, roles, or services can access specific schemas
* Control read and write access to data at the database level
* Prevent unauthorized usage of sensitive database resources
* Support separation between environments or application modules

This approach ensures that database access aligns with the intended use of the data.

***

#### **Database Access as Part of Data & Content Governance**

From a data and content management perspective, database access management helps ensure that:

* Business‑critical data remains consistent and protected
* Shared data is reusable without being overly exposed
* Content stored in databases is accessed only through defined pathways
* Data consumption matches business rules and application design

Rather than treating the database as a single shared resource, ONEWEB enforces structured access patterns that support scalability and reliability.

***

#### **Summary**

**Database Access Management** in ONEWEB supports structured and well‑governed use of data within applications.

By leveraging schemas and security domains, ONEWEB enables:

* Clear separation of data by purpose and domain
* Controlled access to database resources
* Reduced risk of data misuse or contamination
* Scalable data and content management across applications

This foundation helps ensure that databases remain a reliable and well‑managed source of information as applications grow and evolve.


---

# 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.onewebstack.com/oneweb-platform-th/building-apps/data-and-content-management/database-access-management.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.
