> 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-admin/onboarding-new-users/onboarding-email-templates.md).

# Onboarding email templates

Below you’ll find Secoda’s suggested email templates for various stakeholders.

Feel free to use the following templates as you begin onboarding users onto Secoda. We've separated these by Role in Secoda, and have left space for you to insert your workspace-specific details <mark style="color:red;">(in red)</mark>.

### Viewers in Secoda

Typically end / business users, data *consumers*

> Hi <mark style="color:red;">name</mark>,
>
> We’ve recently implemented a new data management tool into our data stack, called Secoda. Secoda stands for **Se**archable **Co**mpany **Da**ta and will enable you to discover the assets that you need in order to make data-driven decisions. With this platform, you’ll be able to:\\
>
> * Search in plain language to find information about the data in our organization
> * Ask Questions to the Data team
> * Explore the end-to-end Lineage of our data stack
> * See a list of verified Dictionary terms and Metrics that drive our company KPIs
> * ...and much more!
>
> We’ve set you up with a Viewer account, which you can access at this link <mark style="color:red;">(insert link to your workspace). Add relevant context here re: Team they will be in, data assets they should be aware of, which integrations you’ve set up that they can explore etc.</mark>
>
> You can read more about the product and its capabilities [here](/readme/secoda-as-a-viewer/introduction-guide.md).

### Editors in Secoda

Typically Data Analysts, Project/Product Managers, Engineers, data *producers*

> Hi <mark style="color:red;">name</mark>,
>
> We’ve recently implemented a new data management tool into our data stack, called Secoda. Secoda stands for **Se**archable **Co**mpany **Da**ta and will be the one-stop-shop for all data needs including: searching, cataloging, viewing lineage, data quality monitoring, and managing data governance. With this platform, you’ll be able to:
>
> * Find verified resources to do your own discovery and analysis
> * Automatically document data assets that you own
> * Explore the end-to-end Lineage of our data stack and identify breaking changes
> * Configure essential Monitors to be alerted about changes to your data
>
> We’ve set you up with an Editor account, which you can access at this link <mark style="color:red;">(insert link to your workspace). Add relevant context here re: Team they will be in, data assets they will own and should add documentation to, any documentation standards, which integrations you’ve set up for them etc.</mark>\\
>
> You can read more about the product and its capabilities [at this searchable site](https://docs.secoda.co/) and see an editor's checklist [here](/readme/secoda-as-an-editor.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-admin/onboarding-new-users/onboarding-email-templates.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.