> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.3/administration/security/story-zone.md).

# Story Zone

Data Stories function as a knowledge base within OvalEdge. Users can create, edit, and organize business knowledge to facilitate data discovery and reuse across the organization.

**Features**

* **Document Business Knowledge:** Create and maintain well-structured documentation for data assets.
* **Support Data Discovery:** Enhance users' data findability and understanding.
* **Content Organization:** Group related data stories under specific "Story Zones."

**Security Management (Administrators Only):**

* **Create and Manage Story Zones:** Define access controls for story zones, specifying who can view or modify stories.
* **User Permissions:** Grant or revoke access to story zones for individual users or user roles.

  <figure><img src="https://content.gitbook.com/content/8fgltewNgYZ8ucAp7Svt/blobs/jZtuxsKcrZxFJ5jo02jg/image.png" alt=""><figcaption></figcaption></figure>

  **Story Zone Permissions (SGA & OE\_ADMIN only)**

  Users with SGA and OE\_ADMIN roles can manage access permissions for Story Zones within OvalEdge.

  * **Grant/Deny Access:** Control which users or roles can view or edit stories within a Story Zone.
  * **Bulk Permission Management:** Efficiently update role permissions across multiple Story Zones simultaneously.

  **Detailed Permission Management:**

  * **Individual Permissions:** Add, modify, or delete metadata (view/edit) permissions for specific roles or users on individual Story Zones.
  * **Role-Based Access:** Set metadata permissions for roles based on license type limitations.

  **Additional Actions:**

  * **Define Story Zone Admin:** Assign a role as admin for a Story Zone, granting them the highest permissions (OE\_ADMIN only).
  * **Delete Story Zones:** Delete existing Story Zones, including any associated stories.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ovaledge.com/release8.3/administration/security/story-zone.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.