How Opries works

Opries is your organisation's shared place for approved documentation, the work that follows from it, and the records that show what happened. It is designed to make organisational knowledge usable in daily work without separating it from governance, projects, learning or follow-up.

This guide gives you the basic mental model. You do not need to understand Git or the platform's underlying technology to use Opries.

Start with the active organisation

The organisation shown beside the Opries brand is the organisation you are currently working in. It is not just a display preference: it determines which documentation, work and private records you can see.

If you belong to more than one organisation, switch organisation before you start work. Opries checks your membership and permissions for the selected organisation before showing its information.

Five connected workspaces

Dashboard: what needs attention

The Dashboard is your starting point after sign-in. It brings together the work, updates, learning, compliance and follow-up that are relevant to you. Items should either help you take an authorised action or take you to the record that explains why it matters.

Work: shared operational follow-through

Work brings together projects, milestones and shared tasks. A task should keep a link back to the project, document, decision, case or other source record that created it. Completing a task does not, by itself, approve a document, make a governance decision or create delegated authority.

People: private participation and engagement records

People brings together the private, need-to-know records that support a person's relationship with the organisation, such as engagements, agreements, appointments and relevant compliance information. These records are not part of public documentation, public search or offline documentation bundles.

Operations: day-to-day records and follow-up

Operations is where you manage day-to-day organisational activity, reporting and follow-up. It keeps operational records connected to the documentation, project, location, case or other source context that explains them.

Governance: meeting cycles, decisions and assurance

Governance supports the recurring work of governing bodies and subcommittees: preparing meetings, recording attendance and declarations, developing agendas, recording decisions, publishing authorised communications and following actions through to evidence and closure.

Documentation is the organisation's source of truth

Documentation is where you find the organisation's approved policies, procedures, registers and related knowledge. It uses a stable alpha-numeric structure, so an identifier such as I.2 or R.1.1 remains meaningful even if the title changes.

Open Documentation to browse that structure. You can read a document beside your current Dashboard, Work, People, Operations or Governance workspace, or open its full page when you need its complete workflow, history, printing or formal review controls.

Search without losing the boundary

Press Command-K on macOS or Control-K on Windows to search. Results are grouped so it is clear whether you are opening:

• authorised organisation documentation, workspace records or private people records; or
• public Opries Help guidance about using the platform.

Public Help Centre articles are separate from your organisation's information. They cannot reveal private titles, records or search results.

Records stay connected to their source

Opries is intended to avoid disconnected lists and duplicate records. For example, a project task can point to the milestone it supports; an agenda item can retain its briefing and resulting decision; and a governed role can point to its source authority and related documentation.

When you use a record, look for its links to the document, project, decision, register or other context that explains it.

Approval, publication and authority are different things

Some actions have formal organisational consequences. Opries keeps those separate and visible:

• editing creates or changes a draft; it does not make it approved;
• approving a version does not automatically make it public;
• publishing makes an approved version available to its approved audience; and
• a role tag, contact change or assigned task does not create delegated authority.

Only an appropriately approved appointment to a governed role can create an active delegation. This distinction helps people understand what they may do, what still needs approval, and where the source of authority sits.

What to do next

If you are new to Opries, start with Get started with Opries. Then use the Dashboard to find your next action, Documentation to understand the relevant approved guidance, and Work to follow through.

As the Help Centre grows, this guide will gain annotated screenshots from a synthetic demonstration organisation. Those examples will show realistic use without exposing a customer's data.