<article><h1>Plugins &amp; integrations</h1><p>Plugins and integrations connect Opries to an external service for a specific, approved purpose. Each connection belongs to one organisation and should use only the information and actions it genuinely needs.</p><h2>Publishing connections</h2><ul><li><a href="/plugins-and-integrations/ghost-cms-connection/">Add a Ghost CMS connection</a></li></ul><h2>Before adding a connection</h2><p>Confirm who has authorised the connection, what information may leave Opries and who is responsible for the external service. Adding or testing a connection may contact that service.</p><p>Use a dedicated credential for each organisation. Do not paste credentials into support cases, public discussions or ordinary organisational documentation.</p><h2>Planned connections</h2><p>Some services shown in Opries are marked <strong>Planned</strong>. They are visible so the Opries Community can discuss the required workflow and safeguards, but they cannot yet be connected.</p></article>

Add and manage governed connections between Opries and external services.

Set up your organisation and find your way around the Opries platform.

Get started with Opries Opries brings your organisation's approved documentation, shared work and governance records into one place. Start with your organisation After signing in, select the active organisation beside the Opries brand. If you belong to more than one organisation, switch there before viewing its documentation or work. Find documentation Use Documentation to browse the organisation's alpha-numeric structure, or press Command-K on macOS or Control-K on Windows to search. Search results only show documentation and records you are authorised to see. Need help or found a problem? Use Report a problem while signed in to create a support case. Opries keeps the case linked to your account and organisation. Where a report is a confirmed product defect, the support team may link it to a private engineering issue.

Get started with Opries

A practical orientation to the organisation, work and documentation experience in Opries.

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.

How Opries works

Practical guidance for using and administering the Opries platform.

How can we help? Find practical guidance for using and administering Opries. Start with the article below, or search the Help Centre. Start here How Opries works Get started with Opries Understand Opries permission levels Browse by topic Plugins &amp; integrations Report a problem If you use Opries and need to report a problem, sign in to the platform first. Your report will be linked to your account and active organisation.

Opries Help Centre

Learn what Reader, Editor, Approver and administrator access allows in Opries.

Understand Opries permission levels A system permission controls what a person can do in Opries for a particular organisation. It is assigned through User access when an invitation is prepared or an existing person's access is edited. Use the lowest permission level that allows the person to do their work. A permission can be changed later without deleting the Person record or their organisational history. Reader A Reader can read approved organisation information that is available to them and use ordinary reader experiences such as assigned learning. Reader access does not allow the person to change drafts, approve governed records or administer the organisation. Editor An Editor has reader access and can create or change drafts, then submit those changes for review. Editing does not approve or publish a change. The governed review and publication steps remain separate. Approver An Approver has reader access and can review governed changes and approve or reject them according to the applicable workflow. Approval does not automatically make information public, create a delegation or authorise an external action. Publication and organisational authority remain separate decisions. Organisation administrator An Organisation administrator manages people, organisation access and Opries platform settings for their organisation. This includes assigning organisation permission levels through User access. This permission should be limited to people who genuinely need to administer the organisation's Opries environment. It does not, by itself, make the person an office holder, committee member, manager or authorised delegate. Platform administrator Platform administrator is an internal Opries-wide permission used to operate the platform across organisations. It is managed by Opries and is not an organisation-managed role. Platform access must still respect tenant isolation, auditability and the purpose for which access is required. Permissions are not organisational authority System permissions are deliberately separate from: participation roles , such as volunteer, staff or management committee; restricted-content access groups , which provide access only to explicitly assigned restricted information; governed role descriptions , which define responsibilities, authority and limitations; and approved appointments and delegations , which establish effective organisational authority. Changing a person's system permission does not appoint them to a governed role, give them delegated authority, approve a document or make information public. Assign or change a permission Open the account menu for the active organisation. Select User access . Add the Person first if they do not already have a Person record. Prepare their invitation or open the action menu beside an existing user. Select the required System permission . Review the change before saving or sending the invitation. Permission changes should record who made the change, the previous and new levels, and when it occurred. Disabling or archiving access should preserve the Person record and its history while removing effective application access.

Understand Opries permission levels

Connect an approved Ghost CMS destination so authorised public documentation can be published from Opries.

Add a Ghost CMS connection A Ghost CMS connection gives your organisation a governed destination for publishing approved, public-eligible documentation. Connecting Ghost CMS does not publish a document, expose a draft or change a document's classification. External publication remains a separate, explicit action on the exact approved version. Before you begin You need: Organisation administrator access in Opries; permission to create a Custom Integration in Ghost CMS; approval to connect the destination and publish organisational information to it; and the HTTPS Admin URL and Admin API key for a dedicated Ghost CMS Custom Integration. Use a separate Custom Integration for each Opries organisation. Do not reuse a key from another organisation or an unrelated publishing workflow. Create the Custom Integration in Ghost CMS Sign in to Ghost CMS Admin for the destination site. Open Settings , then Integrations . Select Add custom integration . Use these recommended integration details: Title or name: Opries Description: Publishes approved public documentation from Opries to this Ghost CMS site. Icon: use the Opries Ghost CMS integration icon . Save the Custom Integration. Copy the Admin API URL and Admin API key shown for the integration. The icon is the approved square Opries identifier supplied as an SVG file. Open the icon link and save the file before uploading it to the Custom Integration. These details make the connection easy to recognise in Ghost CMS Admin; they do not change its access or publishing permissions. Use the Admin API key, not the Content API key. The Admin API key can create and change pages, so keep it private. Ghost CMS documents Custom Integrations and Admin API authentication in its Custom Integrations guide and Admin API documentation . Add the connection in Opries Sign in to Opries and select the organisation that owns the connection. Open your account menu and select Plugins &amp; integrations . Select Add connection . Choose Ghost CMS · Available as the provider. Enter a clear Connection name . Enter the HTTPS Ghost CMS Admin URL shown by the Custom Integration. The Admin URL may differ from the site's public address. Do not add /ghost/api/admin/ to the end. Paste the dedicated Ghost CMS Admin API key . Confirm that the connection and public-document destination have been authorised by the organisation. Select Test and add connection . Opries first checks that the Admin URL is a reachable public HTTPS destination and uses the key to make a read-only connection test. The destination is added only if that test succeeds. Confirm the connection After a successful test, the Ghost CMS destination appears in the connection register as Enabled with its last verification time. Use Verify connection to run the read-only test again. Verification does not publish, update or withdraw a page. The stored Admin API key is encrypted and remains server-only. Opries does not display the key again after the connection is added. If the test fails Check that: the URL is the HTTPS Admin URL for the same Ghost CMS site as the key; you copied the Admin API key , not the Content API key; the Custom Integration still exists in Ghost CMS; the Ghost CMS site is publicly reachable; and no firewall or access rule blocks the connection from Opries. Correct the details and select Test and add connection again. A failed test does not register the destination. If the key is exposed or revoked Revoke or replace the Custom Integration key in Ghost CMS immediately, then contact Opries support to replace the stored connection credential. Existing publishing and verification actions will fail until the connection is updated. Do not include the old or replacement key in a support case. Opries support will provide an approved secure replacement process. What can be published The connection does not make all organisational information public. Opries will allow external publication only when the document is public-eligible, the exact current version is approved and the person performing the action has the required permission. Drafts, restricted information and documents that have not completed their governed workflow are not eligible for Ghost CMS publication.

Add a Ghost CMS connection

Plugins &amp; integrations Plugins and integrations connect Opries to an external service for a specific, approved purpose. Each connection belongs to one organisation and should use only the information and actions it genuinely needs. Publishing connections Add a Ghost CMS connection Before adding a connection Confirm who has authorised the connection, what information may leave Opries and who is responsible for the external service. Adding or testing a connection may contact that service. Use a dedicated credential for each organisation. Do not paste credentials into support cases, public discussions or ordinary organisational documentation. Planned connections Some services shown in Opries are marked Planned . They are visible so the Opries Community can discuss the required workflow and safeguards, but they cannot yet be connected.