> For the complete documentation index, see [llms.txt](https://docs.kyso.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kyso.io/guides/how-to-manage-adoption.md).

# How to manage adoption

All organisations - and especially larger companies with many different teams and departments -  will need to conceptualise how to segment their research and user groups early.

The Kyso platform is structured as below:

*  Company Account
  * **Organizations**: Think of these as different workspaces, or departments within the business.
  * **Channels (Teams)**: Each organization can have multiple channels to organise users and reports. Think of these as similar to Slack channels.
  * **Reports**: Every time a report is published to Kyso, it is published to a specific Team, within an Organization.

To ensure a successful publication, ensure that a report's metadata contains the following variables to correctly categorise it:

* `organization: <organization name>`
* `channel (or team): <channel name>`

## Channel & Report Visibility Settings

You can review how access permissions work in the following document:

{% content-ref url="/pages/vxPiOwAgmzahQZSaa0Do" %}
[Permissions System](/settings-and-administration/permissions-system.md)
{% endcontent-ref %}

Channels have different privacy settings:

* **Private:** only direct members of this channel have access to this team's content.
* **Protected:** only members within the organization can access this channel's content.
* **Public:** any member of any organization can access this channel's content.&#x20;
  * Reports in this channel can also be viewed by external users with no Kyso account by sharing a report's shareable link. Note that users will need authorised access to your company's Kyso deployment (for example, if you have deployed a Kyso self-hosted behind your company's firewall.&#x20;

Users can directly browse through channels **to which they have access.**


---

# 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.kyso.io/guides/how-to-manage-adoption.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.