> For the complete documentation index, see [llms.txt](https://docs.redivis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.redivis.com/reference/organizations/workflows.md).

# Workflows

Any [workflows](/reference/workflows.md) created by, or shared with, your organization will appear on the **Workflows** section of the administrator panel.

Notably, all workflows using your organization's data will automatically be shared with your organization. As an administrator, you will have view-only access to any workflow that uses your organization's data.

Clicking on any workflow will navigate to that workflow's page, where you can [edit](/reference/workflows/create-and-edit-workflows.md) the workflow if it is owned by your organization or you are an editor.

<div data-with-frame="true"><img src="/files/k6vFYg5OtNaQjwJw2Qne" alt=""></div>

## Featured workflows

In order to help researchers work with your organization's data, it's recommended to feature exemplary workflows using your datasets.

On the homepage of your organization's data portal, you will see **Workflows** tab. This list contains all featured workflows analyzing with your organization's data, and is useful for showcasing common workflows and providing training material.

Users will only be able to see featured workflows that they have access to, and in most cases it is recommended to make featured workflows public.

{% hint style="info" %}
Making a workflow public *does not* make its data content public. While users will be able to open the workflow, they will not be able to see any data content that they don't have access to, including in derivative tables.

*Learn more about* [*data access in workflows*](/reference/workflows/collaboration-and-sharing.md)
{% endhint %}

In order to feature a workflow, navigate to the **Workflows** section of the administrator panel. Right click on any workflow to feature it. You can also select multiple workflows to feature / un-feature them all at once.


---

# 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://docs.redivis.com/reference/organizations/workflows.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.