ACCESS, APPROVALS & CONTROL
The answer has to fit
the audience.
A useful answer needs evidence and the right readers. Here is what Ashoon checks, what your admin controls, and what to verify with your own systems before rollout.
Plan an access-aware pilot →01 / BEFORE AN ANSWER IS SHARED
Check the sources and the readers.
Ashoon checks whether the requester and the destination audience can read the cited source material. A channel answer may include less detail than a private answer because its audience is wider.
Connected service credentials make retrieval possible; they do not grant every employee that credential’s access. Your admin configures employee identity links, source scope and approved channels.
A release question, two audiences.
An engineer may receive a permitted ticket and private pull-request detail in a DM. A channel containing people without repository access must not receive that private code detail. The answer depends on the current source permissions and audience.
Illustrative access scenario; validate it with your own source accounts.02 / BEFORE SUPPORTED WRITES
Review what will happen.
Supported proposed actions show the content and destination for human approval. Approval is bound to that action; changes or expiry can require another review.
Scheduled documents have an explicit owner, readers and configured write destination. Their authorized refreshes are a different workflow from approving an individual draft. Check that scope before turning on recurring work.
03 / YOUR OWN CONNECTIONS
Keep personal context private.
Optional personal mail and calendar connections use the person’s own authorization in their private conversation. Personal credentials are separate from the company service identities used for channel work.
Availability depends on the enabled provider and the user’s connection. Connect a personal tool only when you want to use that capability.
04 / UNDERSTAND THE DATA FLOW
Know what the service processes.
The configured AI provider receives the request, instructions and relevant source excerpts needed to generate an answer. Ashoon also stores task and audit records, configured credentials, and indexed content from supported connected sources.
Credentials are encrypted in storage. Admins configure supported retention controls; indexed source content and generated documents have their own lifecycle. Exact hosting, provider processing terms, retention scope and customer agreements must be confirmed for your deployment.
Review the approved privacy notice, terms and any required data-processing agreement before using sensitive company content. This page explains product controls; it does not claim a certification or a contractual guarantee.
05 / KEEP THE ROLLOUT SCOPED
Start with the sources you choose.
- Connect and test each source before enabling it.
- Configure employee access and approve answer channels.
- Inspect task history and audit activity when a result needs investigation.
- Disable a connector to stop new calls through it.
- Review your own recurring work in My workflows; pause or change supported schedules.
Source freshness varies by connector, event delivery and synchronization health. If access or source evidence cannot be established, content may be withheld.
CHECK WITH YOUR OWN SYSTEMS
Make access part of the evaluation.
Ask the same known question as two people with different source access. Check a private answer and a channel answer against the originals. Inspect a proposed action’s exact destination and content. Record any missing evidence or access problem.
Any unauthorized disclosure stops the pilot for investigation. Use the evaluation scorecard to document what you observed, then agree the next scope with your admin.
Plan your evaluation →