How to manage adoption
Learn our best practices on segmenting users and content, and scaling adoption of the platform across the organisation.
Last updated
Was this helpful?
Learn our best practices on segmenting users and content, and scaling adoption of the platform across the organisation.
Last updated
Was this helpful?
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>
You can review how access permissions work in the following document:
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.
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.
Users can directly browse through channels to which they have access.