Organization Controls
Organization Controls
Section titled “Organization Controls”Use organization controls to define workspace-wide defaults before hosts start sharing meetings broadly. These settings decide how people enter the workspace, how external participants are handled, and which teams or roles can manage policy.
Before you change defaults
Section titled “Before you change defaults”- Confirm who owns identity, support, and guest-access decisions for the workspace.
- Decide whether the goal is a broad internal rollout, a restricted pilot, or frequent external collaboration.
- Review meeting access and artifact visibility together so the join policy does not conflict with follow-up sharing.
Core controls
Section titled “Core controls”- Join settings (domain auto-join, approval, SSO-only, required 2FA)
- Member invitation and role management
- Team structure for restricted-access meetings
Access strategy
Section titled “Access strategy”- Use domain and approval settings to control workspace growth.
- Use team structure to simplify meeting-level allow lists.
- Audit member roles regularly as teams change.
- Review these controls before enabling guest-heavy meetings or broad recap sharing.
Recommended change process
Section titled “Recommended change process”- Update the workspace default.
- Test the outcome with a pilot host and participant account.
- Re-check meeting access, artifact sharing, and calendar flows before announcing the change broadly.
Troubleshooting
Section titled “Troubleshooting”Guests can join meetings, but follow-up sharing is wider than expected
Section titled “Guests can join meetings, but follow-up sharing is wider than expected”- Meeting access and artifact visibility are separate controls.
- Review recap, transcript, recording, and export defaults after any guest-policy change.
- Check whether integrations or exports are sending follow-up outside Hyper even though the meeting itself is restricted.