Slack

ASUME in Slack is intended to let authorised users interact with company understanding without moving every question or discussion back into the ASUME application.

Depending on the capabilities available when the interface is released, users may be able to ask ASUME about a company, bring relevant understanding into a conversation, and use objective-specific outputs from within Slack.

The purpose is not to reproduce the full ASUME application inside Slack. It is to make relevant parts of ASUME available where collaboration is already happening.

Using ASUME from Slack does not create a separate Slack version of a company.

A company can be explored in the ASUME application and later discussed through Slack while both interfaces continue to work from the maintained understanding available to the workspace.

This allows teams to change where they interact with ASUME without fragmenting the company state ASUME maintains.

An interface determines where ASUME is used. A source determines which information ASUME is allowed to use.

Slack could eventually serve both roles, but they are separate product behaviours and require separate permissions.

Connecting Slack as an interface does not automatically give ASUME permission to read Slack messages, channels, files, or other workspace information. Likewise, allowing ASUME to use permitted Slack information as a source does not necessarily make ASUME available as an interface inside Slack.

Access through Slack will remain subject to the permissions of the ASUME workspace and the Slack environment.

A user should only be able to access company understanding and capabilities they are authorised to use. Connecting the interface should not expand a user's access to information simply because that information is available elsewhere in the workspace.

Because the Slack interface is planned, its final capabilities, permission model, and supported workflows may change before release.