From the Campus Operations edition of October 18, 2026
University of Alaska sets five principles for staff AI use in communications, warning that an unannounced Zoom AI Companion summary can create a distributed, records-requestable document
University of Alaska System Office of Public Affairs · Public university system: communications staff, records management and meeting tools · Alaska, United States
- Publisher
- University of Alaska News Center
- Original publication
- 16 October 2026 (UA News Center; page last updated 16 October 2026)
- Source retrieved
- 2026-10-19
- Event date
- 2026-10-16
What happened
UA explains the five principles behind its recently published guidelines for generative AI in communications work: authenticity, discernment, accountability, transparency and respect. It says AI should assist but not play a stand-alone role, and that published content should disclose AI use. Its worked scenario: a staff member enables Zoom AI Companion without telling participants; the auto-sent summary accurately captures a budget discussion but also paraphrases comments on a colleague's performance, which are now documented, distributed and potentially subject to records requests. The bottom line given is that AI is assistive, not authoritative. Why now: published 16 October and not previously archived.
Why it matters
Highlights a concrete, under-discussed operational risk: AI meeting summaries can automatically create public records and personnel-sensitive documents. Records, HR and IT need settings and norms, not just principles.
Evidence and measured results
Institutional guidance with an illustrative, not reported, scenario. No incident or usage data.
Limitations and uncertainty
The scenario is hypothetical; guidance is scoped to communications work. The full guidelines were not opened.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-18; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Staff AI use in meetings and communications is creating records and disclosure risks faster than policy covers them.
- Stakeholders
- Public affairs and communications
- Records manager
- CIO
- HR
- General counsel
- Discovery questions
- Who can enable AI meeting summaries, and do they auto-send?
- Are AI summaries covered by your records schedule?
- Do your communications staff disclose AI use?
- Value hypothesis
- Interpretation: reviewing meeting-AI defaults could reduce accidental records and personnel disclosures.
- Potential engagement
- A meeting-AI settings, notice and retention review for one institution.
- Unsupported claims
- That UA had such an incident
- Any measured compliance
- Coverage beyond communications work
Pre-sales engineering
Role takeaway
- Fit
- Relevant to any campus with AI meeting assistants enabled.
- Architecture and integration
- Zoom and Teams AI summary settings, distribution rules and retention policies.
- Prerequisites
- Admin access to meeting-tool AI settings
- State public-records guidance
- Retention schedule
- Constraints
- Public-records laws
- Vendor default behaviour
- Security
- Limit auto-distribution, enable participant notice and set retention for summaries.
- Proof of value
- Run a test meeting confirming notice and host-confirmed distribution
- Verify retention applies to summaries
Delivery
Role takeaway
- Work
- Set meeting-AI defaults, publish staff guidance and align retention.
- Dependencies
- Meeting-tool administration
- Records management input
- Ownership
- IT owns configuration; records management owns retention; communications owns disclosure norms.
- Skills and adoption
- Staff need short training on when to enable AI summaries and what they create.
- Governance checkpoints
- Settings review before enabling AI features
- Records schedule update
- Acceptance criteria
- Proposed: summaries require host confirmation before distribution
- Proposed: participant notice enabled tenant-wide
- Risks
- Personnel comments distributed in summaries
- Summaries released under records requests
- Guidance ignored without settings changes
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Meeting-assistant defaults, such as auto-sending summaries to all attendees, are a configuration decision with records consequences.
Governance
Who approves, reviews and stays accountable for outcomes?
Ties AI use to disclosure, human oversight and institutional accountability for published content.
Security and privacy
What data, permissions and controls need testing?
AI meeting summaries can capture personnel matters and distribute them widely; public-records exposure follows.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Staff are asked to apply judgment; a two-question survey is gathering confidence levels.
Procurement
What should contracts, pricing and exit terms secure?
Meeting-tool AI features should be reviewed for default behaviour and retention before enablement (interpretation).
Operating model
Which teams own the service once it runs?
The communications office issues principles; records and IT settings need to follow.
Publication history
- 2026-10-18Campus Operations · Issue 417 resources
Stable resource ID: ualaska-ai-communications-principles-zoom-companion-records-20261016