From installation
to your first answer.

Before you install

Prove it on your team’s work.

Start with one team, a few approved sources and questions you can check. A suggested evaluation is 5–10 people over two weeks. Agree availability, any usage allowance and support with your rollout contact before installation; this plan is not a commercial trial offer.

1. Choose one recurring problem.

   Start with release blockers, a current policy question or a thread follow-up. List the source content and destinations your admin has approved, and decide what a useful answer must contain.

2. Check the evidence and the boundaries.

   Ask a question with a known answer and open the cited source. Try the same question with a teammate who has different access. Ask about something undocumented and check that Ashoon identifies what it cannot verify.

3. Measure the work that remains.

   Record whether answers were useful, how long checking or correction took, and whether people came back in week two without a reminder. Compare with their existing workflow. Investigate access problems immediately; any unauthorized disclosure stops the evaluation.

Download the evaluation scorecard ↓

The scorecard is a blank Markdown worksheet for your own approved workspace. Downloading it submits no information. Choose your success criteria before starting, then decide whether to continue, change the scope or stop.

For the installing admin

Set up your workspace.

Have someone who can approve Slack apps and authorize the source connection complete these steps.

1. Install in the right Slack workspace.

   Choose your company’s workspace and review the requested permissions. If approval is required, ask your Slack workspace admin. Each workspace configures its own sources and member access.

2. Open your private setup link.

   Use the setup link on the installation success page and sign in with Slack as the installing account. The eligible installer becomes Ashoon’s first admin. To reopen setup later, send admin in a direct message to Ashoon, then choose Get started.

3. Connect and test one source.

   In Connect, choose a source, save its settings and service credentials, and enable it. In Test, run the connection test. You do not need to connect every tool. A passed connection test checks connectivity; your first question will also exercise content access and retrieval.

4. Allow your teammates to use Ashoon.

   In Members → Access, set the allowed company email domains or have an admin link members individually. Until member access is configured, installation alone does not enable every employee. Guests and external Slack accounts cannot use company answers.

   For channel use, approve the channel in Ashoon’s admin console and add Ashoon to it in Slack. Start in a DM if you do not need channel answers yet.

5. Ask and check a real question.

   DM Ashoon about information you know exists in the connected source. Open its citations and compare the answer with the source. Give Helpful / Not helpful feedback when available. Check access and answer quality with a small group before expanding.

Connect your tools

What each tool needs.

Your admin connects and tests each source in Connect, and decides who can use it. Open a tool to see what to prepare. Availability depends on your deployment, the source’s permissions and your configuration.

SlackConversations+

A workspace admin installs Ashoon and configures employee access. For channel answers, approve the channel in Ashoon and add the app in Slack.

Microsoft TeamsConversations+

Coordinate the custom Teams app package and Microsoft sign-in with your rollout contact. Your admin links the organization, configures member access and approves channels.

ConfluenceCompany docs+

Prepare a dedicated service user with an API token and access to the spaces you choose. Your admin checks user and group matching before enabling restricted pages.

GitHubCode & pull requests+

Prepare a GitHub App with access to selected repositories and organization membership. Your admin checks source-account links so private code follows the right people.

JiraProject tracking+

Prepare a dedicated service user with an API token and access to selected projects. User and group lookup permissions are needed to check issue access; live-update setup may need Jira admin access.

Jira Service ManagementRequests & approvals+

Use an Atlassian service user with an agent role on the service desks in scope. Your admin checks access to requests and approvals before enabling the connection.

BitbucketCode & pipelines+

Prepare workspace credentials with repository and member access. Your admin confirms the available token method and webhook permissions for your Bitbucket plan.

CompassService ownership+

Prepare the Atlassian service user and API token. Compass context is read live when requested; it is not part of the recorded company-memory change history.

StatuspageService status+

Prepare an organization API key from the Statuspage account owner. Choose the pages in scope and test incident and component-status access.

Google DriveFiles, Docs, Sheets & Slides+

A Google Workspace admin prepares access to the selected drives and files. Your admin verifies file sharing and user identity before making documents available.

Google MeetMeeting transcripts+

A Google Workspace admin prepares access to recorded meeting transcripts. A meeting needs a transcript Ashoon can read; this connection does not transcribe meetings itself.

Google CalendarYour calendar+

This is a personal connection. Connect your own calendar from a private conversation after your admin enables the provider; your personal context stays private.

SharePoint & OneDriveFiles & documents+

A Microsoft 365 admin grants the configured app access to the files in scope. Your admin checks source sharing and employee identities before enabling the connection.

OutlookYour mail & calendar+

Connect your own Outlook account after the Microsoft provider is enabled. Personal mail and calendar context use your private conversation and your own access.

Microsoft PlannerPlans & tasks+

A Microsoft 365 admin grants the configured app access to plans and tasks. Planner is read live when asked; this connection does not provide source change notifications.

Teams meetingsMeeting transcripts+

A Microsoft 365 admin configures transcript access and the Teams application access policy. Only available transcripts that pass access checks can be read.

NotionTeam knowledge+

Prepare an integration token and share the pages in scope with the integration. Your admin also configures the access map; integration visibility alone does not grant every employee access.

LinearIssue tracking+

Prepare an API key or supported bearer token with access to the selected workspace. Your admin checks team access and whether the credential can manage live-update webhooks.

GitLabCode & merge requests+

Prepare the supported group or personal access token for your GitLab deployment. Your admin checks group membership, project access and webhook permissions.

AsanaTasks & projects+

Prepare the supported Asana token with access to selected teams and projects. Your admin checks people and project visibility before enabling task retrieval.

TrelloBoards & cards+

Prepare the supported Trello credentials and select boards in scope. Board membership and visibility determine which cards can appear in an answer.

ZendeskSupport context+

Prepare supported Zendesk OAuth credentials with access to the chosen support context. Your admin tests user matching and ticket permissions before enabling the connection.

SentryError context+

Prepare an integration token for the organizations and projects in scope. Your admin tests project access and live-update setup before enabling error context.

PagerDutyIncident context+

Prepare the supported PagerDuty API credentials for the teams and services in scope. Your admin verifies incident access and webhook setup.

incident.ioIncidents & follow-ups+

Prepare an API key that can read the incident data in scope. Private incidents are not read because this connector cannot establish their reader permissions.

LaunchDarklyFeature flags+

Prepare an API token for the projects and environments in scope. Your admin verifies member access and live-update permissions before enabling flag context.

FigmaDesigns & comments+

Prepare a team admin’s token with the supported read and webhook scopes. Your admin checks which files and projects can be read by the people asking.

ZoomMeeting transcripts+

Prepare the customer-owned Zoom app and access to meeting transcripts. Your admin configures the app and verifies recording and transcript permissions.

Microsoft Teams

Use Ashoon in Teams too.

Teams supports cited answers, approved actions and scheduled questions with the same source access checks. Colleague messaging, handoffs and living-document workflows currently use Slack. A company can use both: people keep one Ashoon workspace.

1. Already using Ashoon in Slack?

   An Ashoon admin connects Microsoft 365 with Connect with Microsoft on any Microsoft source. This confirms your Microsoft 365 organization: its verified domains must match the workspace’s allowed email domains. Then open Products → Chat platforms and choose Enable Microsoft Teams.

2. Add the Ashoon app in Teams.

   A Teams admin adds the Ashoon Teams app to the teams and chats where it should answer. The Teams app store listing is not available yet: your Ashoon contact provides the app package to upload as a custom app, if your Teams admin allows custom apps.

3. Only on Teams?

   Arrange the rollout with your Ashoon contact before adding the custom app. Adding the app or sending its first message can currently create a workspace for an unlinked Microsoft organization. The eligible person who adds the bot becomes its first admin. Your rollout contact should verify this account and Microsoft sign-in setup before inviting employees. Then configure Members → Access and connect one trusted source.

4. Ask in Teams.

   Message Ashoon in a 1:1 chat, or mention it in a channel thread where it is installed and the channel is approved in Ashoon’s admin console. Guests and people from other organizations get no company answers.

For employees

Ask where you already work.

Open Ashoon in Slack’s Apps list and send start in its Messages or Chat tab for a short guide. Send help for available commands.

Ask about a source your admin has connected and that you can read. For example:

• “Where is our current time-off policy? Include its source.”
• “What are the open blockers for our next release?”
• In an approved channel: “@Ashoon summarize this thread and list the agreed next steps.”

Use a DM for your first question. In approved channels, mention @Ashoon. Follow up in the same thread to clarify or correct the answer; to stop a task that is still running, press Stop on its status card.

Answers depend on both your access and the people who can see the response. A channel may receive less detail than your DM. Check citations before relying on an answer; tell Ashoon when something is missing or incorrect.

Recurring work

Your schedules, under your control.

Create a scheduled question in chat, for example schedule daily 09:00 in me: What changed in our release project?. Schedule times use UTC. Sources and destination access still apply to every run.

Open My workflows and sign in with Slack or Microsoft to review your own scheduled questions and living documents. Pause, resume, or change a supported schedule there. New workflows and instruction changes start in chat.

Living documents currently start from Slack and can be published as an Ashoon page, Slack canvas, Confluence page, Notion page or Google Doc when that destination is configured. An Ashoon page’s link requires sign-in and current reader access.

When something needs attention

Find the next step.

Get help

Keep the right person in the loop.

Employees: contact your workspace’s Ashoon admin for connection and access issues. Admins can use the console’s task state and audit information to investigate. During a pilot, escalate unresolved issues through the person who arranged your rollout.

Share the task reference, what you expected, and the time of the problem. Keep credentials, private answer text and personal admin links out of shared support conversations.