Admin & access

Alongside the personal Settings every user sees (profile, security, notifications, appearance), an Admin group of sections appears in the same sidebar for administrators. This is where a clinic — or Qyire itself — is configured: who has access to what, which modules and AI features are switched on, and the operational registers a regulated platform needs to keep.

Who sees what

Each Admin section is gated independently. There are two ways in:

• Vendor administrators (Qyire's own operations team) see every Admin section, across every organisation, plus a few controls no one else gets: the AI provider connection, the full user access matrix with groups, and impersonation for support.
• Anyone holding the matching feature grant sees just that section, scoped to their own organisation. A clinic can, for example, give one administrator visibility into AI Usage or Services & DPAs without making them a full admin.

Your own organisation admins get a related but smaller set of screens — their organisation's profile, their own Users & Access, an Audit log, AI usage, and Billing for their organisation — under an Organisation group instead of Admin. They don't get cross-organisation views, the feature-grant matrix, or the toggles that control who can see patient identity or use AI features — those stay vendor-controlled, since they gate a regulated capability.

Organisations

A directory of every organisation on the platform: name, status, and the modules each one has active. Vendor administrators open an organisation from here to view or edit its profile — branding, contact details, and identifiers like ODS code or CQC provider ID — and to archive an organisation that's no longer active. Archiving hides an organisation; its data is never deleted.

Users & Access

The single place to manage who can sign in and what they can do — for one organisation, or (for vendor administrators) across all of them.

Roster

Invite a new user by email, add someone directly with a temporary password, change a person's role, or deactivate their account. Deactivating a user immediately ends their active sessions — it isn't just a label. There's no hard delete: leavers are deactivated, not erased, so the audit trail stays intact.

Roles

Every user has one role: Admin, Clinician, Staff, or Read-only. Roles set the baseline of what someone can do before any individual adjustment is applied.

Groups (vendor administrators)

Vendor administrators can organise users into groups and grant features to the whole group at once, rather than one person at a time. A user's actual access is always the combination of their role, any group they belong to, and anything granted or denied to them individually — shown resolved, per person, on this screen. You never need to impersonate someone to check what they can see.

Feature grants (vendor administrators)

Full admin access isn't all-or-nothing. A grant matrix lets a vendor administrator switch on a single capability for a specific person or group without making them an administrator at all — for example, giving one staff member visibility into AI Usage, or letting a finance contact see Billing, while everything else about their account stays as a Clinician or Staff role normally would.

The same matrix also carries the AI feature toggles — Ask MIA, Scribe, AI drafting, and blood-test interpretation — which are switched off by default for every new user. AI capabilities are enabled deliberately, person by person, rather than turned on for a whole clinic at once.

Seeing an un-pseudonymised patient's real identity is a separate, non-grantable capability tied to clinical need, not a feature you switch on for convenience.

Modules

Qyire is built from modules — core functionality plus condition-specific and AI add-ons. This screen shows every module available, which category it belongs to (core, clinical, AI, or presentational), and whether it's active for the selected organisation.

• Core modules are always on and can't be turned off.
• Everything else can be activated or deactivated per organisation.

Turning a module off only hides it from that organisation's interface — nothing is deleted. Re-activating it later brings all the previous data straight back.

AI Providers

Vendor-only. The connection details for the AI providers behind Qyire's AI features — whether the required credentials are configured, shown as a status indicator rather than the credential itself, plus a masked hint of the current value so you can confirm it's the right one without exposing it.

AI Usage

A running record of AI activity: requests over time, broken down by model, by feature (summaries, Ask MIA, drafting, and so on), by organisation, and by individual member. Filter the time range from the last 24 hours out to a year, and switch which breakdown you're looking at to see where usage — and cost — is coming from.

Logs

The platform audit trail: every clinical record insert, update, and deletion, across every organisation, newest first. Each entry shows when it happened, which organisation and table were affected, who did it, and what kind of change it was. Filter by organisation or by action type (insert, update, delete) to narrow it down. Every table in the system is covered — there's no opt-out for a table to go unaudited.

Services & DPAs

A read-only register of every third-party service Qyire depends on — infrastructure, AI providers, analytics, email, billing, and more — with each one's operational status and data processing agreement status at a glance: signed, covered automatically by the provider's terms, still to be signed, or gated pending review. It exists so anyone checking Qyire's data processing footprint has one place to look, rather than having to ask. This register changes only through a reviewed update to its underlying configuration, not through a control on this screen.

Billing

Account-wide billing: the current plan, subscription status, and payment details for an organisation, plus wholesale arrangements where they apply. Available to vendor administrators for any organisation, and to an organisation's own administrators (or anyone holding the Billing grant) for theirs.

Import data

A guided wizard for bringing patient data into an organisation from a CSV or Excel export. Because imported rows become part of the clinical record, review the preview carefully before confirming.

A note on data

Across every Admin section, the same rule applies: deactivating, archiving, or turning something off removes it from view — it never deletes the underlying data. Clinical records, audit history, and organisation data persist regardless of what's currently switched on. Interface visibility is the only thing a toggle ever controls.