> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/readme/secoda-as-an-editor.md).

# Secoda as an editor

Here you can find resources for new Editors within Secoda

As an Editor in Secoda, you are pivotal in enriching data resources and fostering a data-driven culture within your organization. Here's how you can make the most out of your role:

**Start Here:**

* [ ] **High-level** [introduction to Secoda](/readme/secoda-as-a-viewer/introduction-guide.md)
* [ ] **Video Tutorials:**
  * [ ] Video: [Introduction to Secoda](/readme.md#video-resource-introduction-to-secoda)
  * [ ] Video: [Initial steps for new Editors in Secoda](https://www.loom.com/share/ba344cf7b50d41c8af25b67b2a943712?sid=fcca1054-2431-4d54-b3fe-4ab364e49b0f)

**Enhance and Enrich:**

* [ ] **Best Practices:** Read up on[ ](https://chat.openai.com/c/eab2984d-7157-4080-873f-f2cc92e2f22b)[best practices within Secoda](/best-practices.md).
* [ ] **Identify Ownership:** Determine which data resources you own and begin [adding valuable context and enrichment](/best-practices/documentation-best-practices.md).
* [ ] **Chrome Extension:** Download and use the [Chrome extension](/extensions/chrome-extension.md) to manage Secoda metadata directly in tools like Tableau and Snowflake.

**Engage and Enhance:**

* [ ] **Secoda AI Assistant:** Interact with the [Secoda AI Assistant directly in Slack](/extensions/slack-connection/slack-user-guide.md) for data inquiries—ensure your Admins have enabled this integration.
* [ ] **Documentation and Glossary Terms:** Populate the tool with essential [Documents](/features/documents.md) and [Glossary terms](/features/glossary.md) related to your resources.

**Customize and Configure:**

* [ ] **Notification Settings:** Set your [notification preferences ](/features/notifications.md)to stay updated on changes and updates.
* [ ] **Personal Homepage Customization:** Tailor your [personal homepage](/features/homepage.md) with links to frequently accessed resources for quicker navigation.

**Explore Further:**

* [ ] **Learn More:** Dive deeper into the extensive features available to you as an Editor in Secoda. [Explore features](/features.md).


---

# 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.secoda.co/readme/secoda-as-an-editor.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.