Intranet questions Australian organisations ask before they commit

Yes, Australian data residency can be treated as a solution requirement, but it must be confirmed for the deployment you choose rather than assumed. Claromentis supports cloud and self-hosted deployment models. During discovery, we document where production data, backups and support access need to sit, then assess the suitable cloud, sovereign or customer-controlled hosting approach. We will not describe a solution as Australian-hosted until that architecture is confirmed in writing.

Sources: Claromentis security overview; Claromentis for regulated industries

Claromentis provides controls commonly required in governed environments, including granular permissions, audit logging, two-factor authentication, IP-based restrictions, encryption and self-hosted deployment. These capabilities can support a government security program, but no platform makes an agency compliant automatically. We work with your ICT, privacy and risk teams to map requirements such as the ISM, Essential Eight, state protective security standards and internal policies to the proposed configuration and hosting model.

Sources: Claromentis security overview; Claromentis for regulated industries

Health organisations can use role-based permissions, audit trails, policy controls, e-forms, workflows, training records and flexible hosting to reduce uncontrolled access and improve governance. Claromentis states that it is ISO 27001:2022 certified and HIPAA compliant. HIPAA is not an Australian legal standard, so we treat it as supporting evidence of regulated-health capability, not a substitute for the Privacy Act, Australian Privacy Principles, state health-records legislation or your own clinical governance review.

Sources: Claromentis for regulated industries; Claromentis cloud deployment

Published Claromentis controls include encryption in use, in transit and at rest; configurable permissions; two-factor authentication; audit logging; IP-based access controls; password policies; vulnerability scanning; penetration testing for cloud environments; and OWASP-aligned application security guidance. The final control set depends on deployment and configuration, so we confirm responsibilities, evidence and testing during solution design.

Sources: Claromentis security overview

Yes. Claromentis supports on-premise or self-hosted deployment as well as SaaS/cloud. Self-hosting can suit organisations that need direct control over infrastructure, data location or network access. It also changes the responsibility model: your team manages the underlying environment while the platform team manages the Claromentis application components defined in the agreement.

Sources: Claromentis security overview; Claromentis for regulated industries

We begin with discovery: audiences, business goals, pain points, systems, content, governance and security requirements. We then shape the information architecture, navigation, page patterns, permissions and visual design around how people actually work. Configuration, integrations, migration, testing and training follow in manageable stages. The result is not simply a reskinned template; it is a governed digital workplace designed around your organisation.

Sources: Intranet Solutions — About us

Your team provides the decisions only you can make: priorities, content ownership, risk requirements, process rules and sign-off. We provide the delivery structure, platform expertise and practical recommendations. A small cross-functional working group—typically communications, ICT, HR or people, records or governance, and representative users—usually produces better decisions than leaving the project with one department.

Timing depends on scope, integrations, content readiness, security review, migration volume and stakeholder availability. A focused rollout can move faster than a whole-of-organisation transformation with complex workflows and legacy data. After discovery, we provide a staged delivery plan with clear dependencies rather than promising a generic launch date.

Yes. The platform can start with priority communications, documents and navigation, then expand into workflows, e-forms, learning, policy management, project spaces, AI-assisted knowledge access and custom applications. Intranet Solutions’ ongoing Beyond Support model is designed to keep the platform useful as needs and adoption patterns change.

Sources: Intranet Solutions — About us; Claromentis integrations and SSO

We recommend a phased transition. First, inventory the current systems and content; identify owners, duplicates, stale material and compliance records; design the new structure; migrate priority content; test permissions and integrations; pilot with representative users; train publishers and administrators; then launch and retire old systems in controlled stages. This prevents a new intranet from becoming a cleaner-looking copy of an old content problem.

Usually not. Migration is the best time to remove duplicate, expired and ownerless content. We agree retention and archive rules with your records, legal and business owners, then move what is current, useful or required. Historical material can be archived separately when it does not belong in the everyday employee experience.

Adoption is designed in from the beginning: task-based navigation, useful integrations, role-relevant content, mobile access, clear ownership and workflows that save people time. Launch communications and training matter, but long-term use depends on whether the intranet reliably helps employees complete real work. Usage patterns and feedback should guide the post-launch roadmap.

Intranet Solutions remains involved after implementation through its Beyond Support approach. Ongoing time can be used for updates, design refinements, new features and improvements based on usage. That continuity matters because intranets are living operational systems, not launch-and-forget websites.

Sources: Intranet Solutions — About us