Permissions
Use this page to decide who can join a meeting, who can moderate it, and who can see the follow-up afterward. It is the main reference for separating meeting entry, live-room controls, artifact visibility, export rights, and downstream sharing.
After you finish this page, you should be able to explain the default permission model for guests, members, hosts, co-hosts, admins, and owners without mixing meeting access together with recap access.
Wireframes
Section titled “Wireframes”┌──────────────────────────────────────────────────────────────────────┐
│ Hyper app.hyper.video/security/permissions │
├──────────────────────────────────────────────────────────────────────┤
│ │
│ Artifact permissions │
│ │
│ Applies to: recap, transcript, recording, shared files │
│ │
│ ┌──────────────────────────────────────────────────────────────┐ │
│ │ Audience Members of Product and selected guests │ │
│ │ External share Disabled by default │ │
│ │ Link access Sign-in required │ │
│ │ Retention 180 days for recordings │ │
│ └──────────────────────────────────────────────────────────────┘ │
│ │
│ Exceptions │
│ - Hosts can grant per-meeting access │
│ - Admins can enforce stricter workspace defaults │
│ │
└──────────────────────────────────────────────────────────────────────┘
Separate controls for summaries, transcripts, recordings, and exports make it easier to reflect real-world data boundaries.
When to use this
- External collaboration, high-sensitivity meetings, and large workspaces with different teams and data boundaries.
- Rollouts where meeting access and artifact access must be separated cleanly.
Before you start
- Define workspace roles and defaults before relying on per-meeting overrides.
- Identify which artifacts should be visible to all participants versus a smaller follow-up audience.
- Review how Slack, Notion, exports, or automations should inherit or respect these rules.
Settings and options
Permission model
- Meeting access controls decide who can enter the room.
- Artifact permissions decide who can see what after the meeting.
- Workspace defaults create consistency, while meeting owners handle exceptions inside those policy bounds.
Permission model
- Meeting access decides who can enter the live room and whether admission is automatic or host-controlled.
- Live moderation decides who can admit participants, promote co-hosts, remove people, or change in-meeting collaboration permissions.
- Artifact visibility decides who can see summaries, transcripts, recordings, notes, and recap pages after the meeting ends.
- Export and downstream sharing decide whether content can leave Hyper through downloads, Slack, Notion, or other connected systems.
- Workspace defaults should create the baseline. Meeting-level overrides should be used for exceptions, not as the only policy layer.
Role and capability matrix
Use this matrix as a rollout checklist, not as a substitute for the actual workspace and meeting settings. Final access still depends on invite policy, waiting room behavior, artifact sharing, and export rules.
| Role | Typical meeting entry | Typical live moderation | Typical follow-up access | Typical policy control |
|---|---|---|---|---|
| Guest | Can join only if invited, approved, or admitted under the meeting policy | None by default | Only the artifacts explicitly shared with them | No workspace-default control |
| Member | Can join meetings allowed by workspace or invite policy | Only if promoted to host or co-host | Access depends on meeting and artifact sharing rules | No workspace-default control |
| Host | Can manage entry and moderation for meetings they host | Admit, remove, mute, restrict, and promote within the meeting | Usually sees recap artifacts for their meetings, subject to workspace rules | Can change meeting-level settings inside workspace limits |
| Co-host | Same meeting access as assigned by the host and workspace | Shares most live-room moderation duties for that meeting | Follows the same artifact rules the meeting or workspace grants | No workspace-default control |
| Workspace admin | No automatic access to every meeting unless separately invited or shared | Only if also acting as host or co-host in that meeting | Depends on sharing, audit, and admin tooling available in the workspace | Can define workspace defaults and review policy posture |
| Owner | Same meeting access model as other users unless separately invited or shared | Only if also acting as host or co-host in that meeting | Depends on sharing and admin controls, not ownership alone | Can change the highest-level workspace defaults and ownership settings |
Rollout checklist
- Define meeting entry rules before defining recap-sharing rules.
- Review guest access and artifact visibility as separate decisions.
- Confirm whether exports and integrations inherit the same audience as the in-product recap.
- Test one internal meeting and one guest-facing meeting before changing defaults broadly.
Related tasks
What this feature helps with
Per-artifact controls
Set visibility for each recording, transcript, and summary independently. Share a summary without sharing the recording.
Role-based access
Admins, managers, and members have different default permissions. Customize roles to match your organization's structure.
Workspace policies
Set organization-wide defaults for artifact retention, sharing, and visibility. Individual meetings can override within policy bounds.
How to work with it
Set workspace defaults
- Configure organization-wide permission policies
- Choose default visibility for recordings, transcripts, and summaries
Customize per team
- Teams can have their own default permissions
- Override workspace defaults where needed
Adjust per meeting
- Change permissions for any individual meeting artifact
- Share selectively with specific people or groups
Where it fits well
Enterprise teams
- Organization-wide policies enforced automatically
- Role-based access matches org hierarchy
- Audit trails for compliance
- Bulk permission management
Cross-functional projects
- Share summaries with stakeholders, keep recordings private
- Per-project permission groups
- Temporary access for external collaborators
- Clean separation between project workstreams
Client-facing teams
- Client meeting recordings visible only to the account team
- Summaries shared internally, recordings restricted
- External sharing controls for deliverables
- Privacy boundaries between client accounts
What to expect
- Per-artifact granularity
- Role-based defaults
- Workspace-wide policies
- Audit logging
- Temporary access grants
- Policy inheritance with overrides
Questions that come up often
Can I share a summary without sharing the recording?
Yes. Each artifact (recording, transcript, summary) has independent permissions. Share exactly what you want, nothing more.
How do workspace policies work?
Admins set organization-wide defaults. Teams and individuals can adjust permissions within the bounds of the workspace policy.
Is there an audit trail?
Yes. All permission changes and access events are logged. Admins can review who accessed what and when.
Related tasks
Limitations and rollout notes
- Permissions only stay consistent if downstream integrations are configured intentionally.
- Legacy habits such as broad link sharing can undermine otherwise strong artifact controls.
Troubleshooting
A guest can join but should not see the recap
- Review the artifact visibility rules separately from the meeting entry policy.
- Check whether the recap was shared through Slack, Notion, or export in addition to Hyper.
- Use narrower defaults for guest-facing meetings and only open sharing when necessary.