Data Access
One Horizon scopes data by team. What you can see depends on which teams you belong to and what role you have.
Roles and visibility
| Role | What data they can see |
|---|---|
| Workspace Owner | All teams' data across the entire workspace |
| Workspace Member | Data from teams they belong to only |
| Team Admin | Their team's data only — admin rights cover managing the team, not expanding data visibility |
| Team Coordinator | Their team's data — same visibility as a Team Member |
| Team Observer | Their team's data — same visibility as a Team Member |
| Team Member | Their team's data — recaps, standups, insights, and the Team Journal |
A workspace owner who is also a team member gets both: their team's data plus cross-workspace visibility. Team Admin, Coordinator, and Observer all have the same data visibility as a regular Team Member — the role differences are about what they can manage and whether their own work appears in the team's recaps, not what they can see.
For the full breakdown of what each role can do (invite members, configure settings, etc.), see User Onboarding.
Team scoping
Only members of a team can see that team's data. This includes:
- Team recaps and work summaries
- Team standup history and notes
- Team Insights metrics and analytics
- The Team Journal (who worked on what)
If someone isn't a member of a team, they can't access any of that team's data — even if they're in the same workspace.
Cross-team visibility
Teams are isolated from each other. A member of Team A can't see Team B's recaps, standups, or insights, even if both teams are in the same workspace.
This is intentional. It keeps sensitive work data — like what a team is struggling with or what engineering shipped last week — visible only to the people who actually need it.
Workspace owners
Workspace owners can see data across all teams in the workspace, so they don't need to be added to every team to manage it.
If your organization has strict data access requirements, limit the number of people with workspace owner access.
Personal data
A user's daily recap — what they worked on, their tasks, their activity — is only visible to them. Team summaries show aggregated activity, but individual task details stay private.
Integration data
Each user's integration data is scoped to the accounts and organizations they connected. One Horizon only pulls data from integrations a user authorized.
One Horizon doesn't bypass your existing platform governance. If your GitHub org restricts repository access, or your Slack workspace limits what apps can do, those rules apply to One Horizon too.
GitHub
If your GitHub organization has OAuth app access restrictions enabled — standard on GitHub Enterprise — a GitHub org admin must approve One Horizon for each user before they can connect their account. Users will see an access request screen when they try to connect; the org admin approves or denies it in the GitHub org settings.
One Horizon only accesses repositories the user already has permission to read in GitHub. If they can't see a repository there, One Horizon can't see it either. See GitHub Integration for connection setup.
One Horizon only captures work from users who have connected their GitHub account to One Horizon. Commits from unconnected users are ignored — there's no way to attribute that work without the link.
Commit attribution also requires the email address on the commit to match a verified email in that user's GitHub account. GitHub Enterprise accounts usually have this sorted, but if a user's commits aren't showing up, a mismatched commit email is the first thing to check.
Slack
Slack approval happens at the workspace level. When a Slack Workspace Admin installs One Horizon (see Enterprise Integrations), that covers the whole workspace — users don't need individual approval. Once the integration is active, team members can interact with the @one bot directly.
One Horizon's Slack access is limited to what was granted during installation: posting to configured channels and responding to direct messages. It doesn't read channel history or access channels it hasn't been invited to.
Other integrations
For Linear, Jira, and Google Calendar, each user authorizes their own account. One Horizon can only see the projects, issues, and calendars that account already has access to. There's no org-level approval step, though your IT policy may require users to get sign-off before connecting third-party apps.