Good questions.
Clear answers.

Agility is an operating environment connecting people, existing systems and AI. It brings work, context, responsibilities and controlled actions together, so organisations can move from fragmented activity to coordinated outcomes.

No. Agility is designed to work across your existing technology stack. Your systems remain in place while Agility provides a shared environment for coordinating work around them. Connections to individual systems depend on the available integrations.

Agility is designed for teams and organisations that coordinate work across projects, departments, systems and AI. You can begin with a focused use case and expand as your needs evolve.

Yes. Agility provides an environment for managing projects, tasks, teams and responsibilities. AI can be introduced where it adds value, rather than becoming a requirement for every activity.

Not necessarily. Agility is designed to work alongside existing business systems. The data and integrations required depend on the workflows and technical environment of each organisation.

Agility is designed to be model- and agent-agnostic. You are not tied to a single AI provider. Supported models, agents and connections depend on your deployment and integration requirements.

AI agents perform tasks. Agility provides the operating environment in which people, work, systems and agents can contribute together, with shared context, clear ownership and defined boundaries.

Yes. Human responsibility is central to Agility. Organisations can define the roles, permissions and boundaries for work involving AI. The exact review and approval steps are established for each use case and deployment.

Agility is designed around defined authority and operational boundaries. Depending on the workflow and available configuration, certain AI-driven actions may be automated while others require human review. The organisation determines the appropriate level of oversight for each use case.

Your organisation determines who should have access and what they can do. Agility is designed around identity, authority, boundaries and traceability, with roles and permissions configured for the way your teams work.

Agility can be deployed in different infrastructure arrangements, including options for EU-based and private environments. The appropriate hosting, data-processing and security arrangements are confirmed before implementation.

Traceability is part of the Agility control model. The level of logging and audit information available for a particular action depends on the integration, deployment and configured controls.

Yes. You can begin with one team, project or operational workflow, learn from real use and expand when it makes sense. There is no need to replace your entire software environment at once.

Agility offers different ways to get started. Enterprise pricing may include an organisation fee, user-based pricing and metered AI usage, depending on the chosen arrangement. Contact Ongo for current terms and what applies to your organisation.

Start with a conversation about one operational challenge. Together, we can identify a useful first workflow, define the responsibilities involved and choose a practical route to introduce Agility.

Your access depends on your organisation's permissions and project settings.

Check whether you are a member of the relevant team or whether the project is public. Guests need explicit access to a project.

If you believe you should have access, contact your organisation administrator.

Inviting new users depends on your role and organisation settings.

Administrators can invite users without additional approval, while members may require approval. If you're inviting a guest, check whether guest access is enabled in your organisation's settings.

Contact your organisation administrator if you need additional permissions.

Some invitations require approval from an organisation administrator.

If your invitation has not yet been approved, contact your administrator or the person who invited you for an update.

Deleting tasks requires administrator-level effective permissions on the relevant project.

If you do not have those permissions, contact a project administrator to request deletion.

The Kanban board displays tasks belonging to the active sprint.

Tasks from planned or completed sprints will not appear in that view.

Check that the correct sprint is active. If necessary, complete the current sprint and start the next one or move the task to the active sprint.