Organisation boundaries
Membership of one organisation does not grant access to another. The application must confirm the permitted organisation for each customer operation.
Data & access
The right context. The right access.
Useful information is not information that everyone can see. Omnisio Team separates public product discovery from customer work and applies the permissions required by the organisation and the data involved.
Your existing account remains your account.
The customer login opens the existing Team authentication flow. The new public site does not create a parallel account database or collect your Team password. Existing additional verification steps remain part of the sign-in process where enabled.
Organisation, squad and role matter.
Role-specific access
Medical, coaching, management and technical responsibilities are different. Infrastructure administration alone is not permission to read athlete health details.
Permission to share
Personal Omnisio data is not exposed to a club simply because the athlete has an account. The configured relationship and relevant sharing permissions govern what can be used.
A number should have a source.
Device recordings, personal context, staff observations and calculated outputs serve different purposes. Missing, stale, withheld or insufficient data is not represented as a reassuring zero or a healthy score. Review the source and time before acting.
AI does not create additional permission.
An AI-assisted summary remains subject to the same relevant access and source boundaries. It supports the staff’s review; it is not a diagnosis, an instruction to override consent or a substitute for a qualified professional.
Confirm the deployment details that matter to your organisation.
Hosting location, service providers, retention, support and contractual data responsibilities must match the agreed service. Discuss these requirements during scoping. This page does not claim a certification, a universal residency option or a legal compliance guarantee.
Questions about access or personal data?
Contact support for an account-access issue. For privacy questions, use the privacy contact. Do not send passwords, recovery codes or athlete medical records in a general enquiry.
Email the Team specialistsFrequently asked questions
Does the public site display our athlete data?
No. Public product examples use clearly labelled illustrative data. Private customer information belongs in the authenticated Team application, not in public page content or search metadata.
Do you need our athlete records to arrange a demo?
No. Describe your organisation and workflow. A demonstration request should not include health information or personal athlete files.