Using DNN’s Workflow Module for cross-department approvals

Scattered email threads and chat messages make it difficult to show who approved a page, product note or campaign before publication. DNN’s Workflow Module turns that informal exchange into a repeatable publishing process. Pages, news items, product notes and campaign assets can move from draft to review and publication, with each decision recorded in the portal. For organisations using Aricie solutions such as Acoléa, Adylic, AricieGrid or Budg-Immos, this provides one governance layer without separating departmental teams into disconnected tools.

A DotNetNuke (DNN) workflow can define the people, stages and permissions needed to approve content across departments. A content owner submits an item, subject experts assess it, and an authorised publisher releases it. Status indicators, notifications and an audit history show what is waiting, who owns the next action and whether approval came from the correct role.

Australian organisations add practical complications to this process. Content may be prepared in Sydney while legal review happens in Melbourne, a Brisbane team serves eastern states, and colleagues in Perth work eight hours ahead of UTC. Where personal information or commercial email is involved, the Privacy Act 1988, Australian Privacy Principles and Spam Act 2003 can shape the required review without slowing routine publishing.

Map the approval path

Begin with the content types that actually require coordination. A simple news article may need an editor and publisher, while a pricing update may involve product, finance and legal reviewers. List each stage, its expected output and the condition that allows work to advance. This prevents every article from following an unnecessarily heavy process.

Build routes around the organisation rather than a fixed linear sequence. Drafting, subject review, compliance review, final approval and publication can be standard stages, but branches can handle urgent updates or content that requires legal advice. A rejected item should return to the content owner with a clear reason, while approved material can be scheduled or published automatically.

Keep exceptional work visible in the same system. If a campaign must be checked against Australian Consumer Law requirements, the workflow should record that review rather than leave it in an inbox. Australian date formats, GST information and ABN details can also be marked as required checks where relevant.

Define roles and decision rights

Map DNN security roles to real responsibilities, not job titles alone. A content owner prepares and resubmits work, a departmental reviewer confirms accuracy, a compliance officer checks sensitive material, and a publisher controls release. The same person may hold several roles for low-risk content, but that permission should be deliberate.

Use group membership and workflow assignments to route each task to the right department. Temporary delegation can cover leave, while escalation rules can alert a manager when a review ages. Separate authorship from final publication where the organisation’s controls require it, and avoid shared credentials because they weaken both accountability and the audit history.

Review the map whenever teams or responsibilities change. A new office, an additional legal reviewer or a revised approval threshold should alter permissions and routes before it creates a bottleneck. Configuration by Aricie can incorporate these rules while retaining familiar DNN administration.

Keep reviews visible and accountable

Each submitted item should display its current stage, owner, due date and any unresolved comments. Reviewers need enough context to make a decision without searching through several inboxes. If DNN’s standard notifications do not match the process, Aricie can extend the portal with targeted reminders, escalation notices or links back to the item.

Make the status history meaningful. Record when a reviewer approves, rejects, delegates or requests a change, and keep the content version associated with that decision. This makes it easier to establish what was approved, which wording went live and whether a later correction is needed. It also supports internal assurance and external audits.

Schedule reminders around Australian working patterns rather than sending everything at midnight. Sydney, Melbourne and Canberra observe AEDT during daylight saving, Brisbane remains on AEST, and Perth uses Western Australian Standard Time. State public holidays, company shutdowns and seasonal leave can be reflected in reviewer calendars so valid content is not held by an unavailable approver.

A practical configuration checklist

Before production, agree on naming, ownership and service levels with every participating department. Then test the complete path using realistic examples.

• Create one content type per review need, with clear draft, review and published states.
• Assign least-privilege roles and name a backup for every required approval.
• Pilot with marketing, operations and finance using low-risk and high-risk examples.
• Train authors and reviewers together, including rejection, delegation and escalation handling.

Run user-acceptance tests in a non-production environment, checking permissions, notifications, version history and mobile access. Test Australian date formats, time-zone display, accessibility requirements and links from campaign material to the portal. Record configuration decisions so future changes do not undermine the audit trail.

Roll out with training and local support

Start with a small pilot and publish a short governance guide. Explain which content requires review, who may approve it, how quickly tasks should be completed and what happens when a deadline is missed. A visible queue for outstanding tasks gives authors a dependable alternative to chasing reviewers.

Aricie can configure DNN workflows, adapt existing portal modules and develop custom software where approval logic requires additional functionality. Its teams in Mureils, Paris, Lyon and Grenoble can work with Australian stakeholders through scheduled handovers, shared documentation and role-based training for administrators, authors and reviewers.

Support should cover both the technical workflow and the people using it. Monitoring can reveal rejected items, approval delays and overloaded roles, allowing the process to be adjusted before it becomes routine friction. Contact Aricie to request a DNN workflow demonstration, an assessment of your approval stages and a scoped rollout plan for your organisation.