Team and access
Let other people sign in, give them the right roles, and send build news to Slack.
Local Only lets one person use Oore from the Mac that runs it. These guides open Oore to a team. Do them in this order.
1. Let people sign in
Configure External Access so people can sign in from their own devices over HTTPS. Then pick how they sign in:
- External Access (OIDC) with Google, Microsoft Entra ID, Okta, Auth0, or Keycloak. Choose this unless you already run an access proxy.
- External Access (Trusted Proxy) when an existing authentication proxy already checks who people are.
2. Add people
- Invite a team member with an instance role.
- Manage roles and project access for the projects they need.
- Disable or restore a user when their access should change.
Instance roles control actions across Oore. Project roles control access inside one project. The backend checks both, so hiding a button in the web UI is not what keeps someone out. See Roles and permissions for the full matrix.
3. Keep the team informed
Send notifications to Slack for failed builds, store uploads, rollouts, and approvals.
Next step
Configure External Access. To understand how sign-in, roles, and repository trust fit together, read Oore’s security model.
Promote builds between environments
Define internal, beta and production environments on a project and promote a tested Google Play or TestFlight build between them without rebuilding it.
Invite a team member
Create an Oore invitation, choose an instance role, and share the instance URL with the new user.