Justin Sheehan
Chief Journey Officer
Draft permission-set options
- Â Locked-down âFort Knoxâ version.Â
- Â Balanced default version.Â
- Â More open innovation / testing version.Â
Decide who can see chat history
- Â Company admins?Â
- Â Ambassador-level super admins?Â
- Â Only under safety, legal, or support escalation?Â
- Â This was one of the biggest unresolved governance questions.Â
Define data retention rules
- Â What gets saved?Â
- Â What gets deleted?Â
- Â What can users control?Â
- Â What can companies configure?Â
Decide how content flagging should work
- Â What types of prompts get flagged?Â
- Â Who gets notified?Â
- Â Should this be required or configurable by company?Â
Define company knowledge-base rules
- Â What documents can be uploaded?Â
- Â What needs approval first?Â
- Â What should be restricted, especially financial, legal, HR, or sensitive documents?Â
Clarify company memory vs. model training
- Â Make it simple: Daryle.AI may use approved internal knowledge to improve the private company experience, but it is not training OpenAI, Anthropic, or Gemini models.
- Schedule a follow-up governance meeting
- Â Review the security white paper.Â
- Â Review permission-set options.Â
- Â Decide the default policy posture before rolling out to affiliates.