Governance
Governance
Set the workspace-wide rules, defaults and settings that shape how planning, delivery, support, reporting and AI work in Paradym Next.
Most of Paradym Next is about doing the work: raising ideas, planning them, delivering them and supporting what was delivered. Governance is where your organisation decides how that work runs. The settings here apply to everyone in the workspace, so they are usually looked after by administrators, heads of product or delivery, and other leads.
Every stage of the wider flow has settings in Governance:
| Stage of the flow | What Governance controls |
|---|---|
| An idea is raised | The questions Next asks when someone submits an idea (Planning → Submissions). |
| Ideas are triaged in the Inbox | The impact types a triager can assign to a cluster (Planning → Impact types). |
| Items are planned in the Portfolio | The planning workflows items move through, the agent packs that draft documents, review timings, scoring and categorisation (Planning). |
| Items are prepared in the Intake Queue | The steps someone works through before promotion, and the systems work can be handed to (Delivery → Promotion, Delivery → Integrations). |
| Work runs in Projects and work streams | The work stream templates, project status wording and Next Studio settings (Delivery). |
| Delivered work is supported | Ticket types, priorities and SLAs, queues and issue clustering (Support). |
Alongside the flow, Governance also holds the AI providers and models the workspace uses, the settings for each application and knowledge base, and which reports people see.
Before you start
- Governance appears in the sidebar only if your role includes it. Each area inside it can also be switched off for your workspace. If you cannot see a page described here, your organisation may not use it, or your role may not include it. See Understanding roles.
- AI & Models has its own permission, separate from the rest of Governance. A role can be given AI settings without the other Governance areas, and the other way round.
- Some roles can read Governance settings without changing them. If that applies to you, you see the note View only — you don’t have permission to change these settings. at the top of the page, and the controls are switched off. Ask an administrator if something needs changing.
How Governance pages are laid out
Each area in the sidebar opens a page with a row of tabs across the top, one tab for each part of that area. For example, Governance → Delivery has the tabs Workflow, Promotion, Next Studio, Projects and Integrations.
Every Governance page has a guided tour. Open the help (?) menu in the top bar to replay it.
How changes are saved
Most Governance pages save automatically. While a change is being stored you see Saving… beside the section heading, then Saved once it is done. Text fields usually save when you click or tab out of them.
A few pages work differently:
| Page | How it saves |
|---|---|
| Delivery → Integrations | Nothing is saved until you select Save. You are warned if you try to leave with unsaved changes. |
| Work stream template editor | Nothing is saved until you select Save template. |
| AI & Models provider keys | Each key is checked with the provider and saved when you select Save beside it. |
| AI & Models → Embedding Inference | The embedding model is locked in only after you select Use this model and confirm. |
| Knowledge Bases → Sharing | This page is for reading only. |
Areas in Governance
The areas appear in the sidebar in this order.
| Area | What it controls | Pages |
|---|---|---|
| AI & Models | The AI providers, API keys and models the workspace uses for text, images and embeddings. | AI & Models |
| Applications | Each application’s name and description, files to skip when code is uploaded, and whether uploads are summarised. | Applications |
| Delivery | Work stream templates, the steps before promotion, Next Studio, project statuses and delivery integrations. | Workflows, Work stream template editor, Promotion, Next Studio, Project statuses, Integrations |
| Knowledge Bases | Knowledge base names and descriptions, and what the workspace shares with partner workspaces. | Catalogue, Sharing |
| Planning | How ideas are captured, drafted, reviewed, scored and triaged, and the workflows planning items follow. | Submissions, Agent Packs, Workflows, Planning workflow editor, Review, Prioritisation, Impact types, Strategy, Generation |
| Reporting | Which reports appear on the My Reports page, whether each is ready, and which roles see it. | Reporting |
| Support | Ticket types, priorities and SLAs, queues and statuses, and how issues are clustered. | Ticket types, Priorities & SLAs, Queues & statuses, Issue clustering |
Typical workflow
When a workspace is first set up, administrators usually work through Governance in roughly this order:
- Connect AI. In AI & Models, add provider keys for text inference, choose the embedding model, and switch off any models the workspace should not use.
- Shape idea capture. In Planning → Submissions, set the questions Next asks when someone raises an idea.
- Set up triage. In Planning → Impact types, set the impact labels triagers use in the Inbox.
- Define planning. In Planning → Workflows, choose or build the workflow items follow, then set the agent packs, review timings and prioritisation scoring.
- Define delivery. In Delivery → Workflow, build the work stream templates, then set the promotion steps, project status wording and any integrations.
- Set up support. In Support, set ticket types, priorities and SLAs, and queues.
- Decide who sees what. In Reporting, publish reports and limit them to roles where needed.
After that, Governance is mostly revisited when a process changes, for example when a new review rule is agreed or a new delivery system is adopted.