An intranet with a knowledge graph is not a simple file repository. It is a system that organizes information by concepts and relationships, allowing people to find answers with context and meaning. To make it work, choosing the best technology is not enough; a multidisciplinary team must define the knowledge model, access rules, and processes. The following profiles explain who should participate and what responsibilities each one takes on.
The first essential profile is the executive sponsor. Their role is not to attend every meeting, but to unlock budget, align the project with business strategy, and make decisions when departments disagree. Without a sponsor with real decision-making power, the intranet loses priority compared with other initiatives. This role should belong to a senior executive who understands knowledge as a corporate asset and can communicate the project's purpose across the organization.
The second role is the product owner or functional manager. This person owns the project vision and the improvement backlog. They define priorities, validate user stories, and decide which features enter each iteration. They also measure success indicators: search time, reduction of internal email, onboarding speed, document reuse rate, and so on. In knowledge graph intranet projects, this role usually falls to someone in knowledge management, digital transformation, or process improvement.
The third group is business users. It is not enough to talk with executives and IT managers. You need to listen to the people who actually work with information every day: technicians, administrators, salespeople, customer service, HR, operations. They know what terms they use, what questions they ask, what documents they need, and what relationships between concepts are not documented. End users must also participate in testing and semantic search validation, because their way of searching should guide how the system is tuned.
Within business users, it is useful to identify knowledge champions in each department. These people act as a bridge between their team and the project team. They help clean content, identify critical information sources, detect duplicates, and propose improvements. Their presence accelerates deployment and increases adoption because the rest of the team sees that someone close to them endorses the tool.
The fourth group is the technical team. This includes the people responsible for architecture, integrations, security, and operations. A knowledge graph intranet needs to connect to existing systems: ERP, CRM, SharePoint, Teams, Active Directory, and internal databases. A good integration avoids creating an information island and allows the graph to feed on real data. At Q2BSTUDIO we work with modern architectures and custom software to adapt the platform to each company's processes, instead of forcing the client to change the way they work. This integration work requires a technical profile with experience in APIs, databases, and identity management.
The cloud manager also needs to be involved. The platform can run on AWS/Azure cloud environments with AI services and scalable storage. This profile decides the network architecture, access policies, backup mechanisms, and observability. If the company does not have this role, an external consultancy can cover it, but it is better to have an internal contact who knows corporate policies and industry restrictions.
Security is another unavoidable role. The cybersecurity manager must validate authentication flows, role-based permissions, encryption in transit and at rest, and audit logs. A knowledge graph connects information from many systems; if permissions are not properly configured, someone could see data from other areas without realizing it. Cybersecurity should not be a final addition, but a core criterion from the design phase. Internal security teams should work with external cybersecurity specialists to run penetration tests and review the threat model.
The data protection officer or compliance manager is also necessary. The intranet may contain personal data, evaluations, contractual information, or confidential records. GDPR compliance and industry regulations must be present at the design stage, not afterwards. This profile defines retention periods, access rights, legal bases, and breach notification processes. Involving them from the start avoids expensive redesigns and gives confidence to risk committees.
Advanced projects add profiles such as information architect or data steward. The information architect defines the graph taxonomy and ontology: what types of concepts exist, what properties they have, and what relationships are relevant. The data steward ensures data quality: removing duplicates, normalizing values, and setting maintenance rules. Without these profiles, the graph degrades over time and search precision declines.
AI specialists, including prompt and RAG engineers, are also key. A knowledge graph intranet often relies on language models and AI agents to answer questions, summarize documents, or suggest connections between people and projects. These professionals configure indexes, tune embeddings, validate answers, and define when the system should escalate a query to a human. At Q2BSTUDIO we help companies implement this kind of AI with a web portal that allows clients to manage prompts and observe performance, reducing technical dependency.
A change management and internal communication lead is essential. This person plans training, guides, Q&A sessions, and adoption campaigns. A knowledge graph intranet changes how people work; if nobody manages this change, the system will be abandoned. Communication must explain not only what the tool does, but what it is for in daily work and which problem it solves.
A small, agile steering committee is as important as individual roles. It can be made up of the sponsor, product owner, a technical lead, a user representative, and a security or compliance expert. This committee meets every two weeks, reviews progress, decides priorities, and resolves dependencies. At Q2BSTUDIO we facilitate an initial role assignment and governance workshop so the client knows who makes each decision and how progress is communicated.
Integration with existing systems also affects the profiles involved. If the intranet must connect with SAP, Dynamics, Salesforce, Odoo, or NetSuite, a functional manager from each system should participate in design sessions. Their knowledge of where critical data lives and how it is structured avoids errors in field mapping and synchronization. Also, when BI/Power BI data is included, the data analyst must verify that metrics shown in the portal come from the same sources of truth as official reports.
Q2BSTUDIO's experience in this kind of project shows that the overall team does not need to be very large, but it does need complementary profiles. A small team of five or six people, with direct access to key users, usually performs better than a wide committee without clear authority. The key is that each participant knows their responsibility and has a direct channel with the product owner.
In conclusion, a knowledge graph intranet is a corporate project, not an isolated technical one. The roles involved in its definition and governance determine the quality of the graph, adoption levels, and return on investment. Including the sponsor, business users, IT, security, compliance, change management, and AI specialists from the start is the most effective way to avoid mistakes and build a tool that the organization actually uses. If your company is considering such a project, having a technology partner that helps bring these profiles together is as important as choosing the right technology. At Q2BSTUDIO, as a software development company, we offer support in designing the knowledge model, integrating custom software, and deploying AI agents so that the intranet evolves with the business.
