Only users with access to your project within the platform can view or edit your stakeholder mapping. This typically includes:

• Your internal project team (e.g. Manager, Project Creator, Organiser, Reviewer)
• ConnectGo and LEVEL's Analysts and Account Manager

Different roles have different levels of access:

• Project Creators can create and edit all stakeholder information
• Organisers can update stakeholder details and engagement plans
• Reviewers can approve, comment, and suggest edits
• Account Managers can access data across multiple projects

Stakeholder responses are not shared externally unless you choose to include them in a public report or during a learning review. The primary purpose of this data is to support:

• Internal project planning and decision-making
• Risk assessment and mitigation strategies
• Monitoring stakeholder engagement effectiveness
• Learning and improvement processes

If you need to share stakeholder insights with external parties:

• Use the platform's export tools to create sanitized reports
• Consider aggregating data to protect individual perspectives
• Seek permission before attributing specific feedback
• Apply appropriate data classification labels

Be honest and transparent — but always respectful. These entries are used for learning, risk management, and accountability, not for external publication. When documenting stakeholder information:

• Focus on observable behaviors and concrete examples
• Avoid making personal judgments or using inflammatory language
• Document evidence for any claims about influence or power
• Note the source of information where relevant

Some information requires special consideration:

• Political affiliations or personal relationships
• Potential conflicts of interest
• Historical tensions between stakeholder groups
• Feedback that could be perceived as critical

The SMRV platform implements multiple layers of protection:

• Encrypted data storage and transmission
• Regular security audits and vulnerability testing
• Multi-factor authentication for user access
• Automated monitoring for suspicious activities

Users also play a key role in protecting stakeholder data:

• Never share login credentials
• Log out when accessing from shared devices
• Be mindful of who might see your screen when reviewing data
• Report any potential security concerns immediately

All actions within the stakeholder module are tracked:

• Who made each entry or edit
• When changes were made
• What specific information was modified
• Comments explaining significant changes

Formal review processes are also documented:

• Who approved each version
• When approvals were granted
• Any conditions attached to approvals
• Resolution of flagged items

Stakeholder data is retained according to the following schedule:

• Active projects: Full access to all data
• Completed projects: Retained for two years after project close
• Archived projects: Key insights preserved in anonymized form

If your organization or project has specific retention requirements:

• Discuss these with your Account Manager
• Document any special requirements in your project setup
• Consider data minimization principles

When gathering information from stakeholders:

• Be clear about how their input will be used
• Explain who will have access to their feedback
• Specify whether their contributions will be attributed
• Offer options for anonymity where appropriate

Building trust regarding data usage:

• Share relevant insights back with stakeholders
• Demonstrate how their input has influenced decisions
• Respect confidentiality requests consistently
• Acknowledge concerns about data usage openly