Purpose

This policy defines the access levels for Miro users based on their roles within the organization. It ensures data integrity, confidentiality, and appropriate permissions for collaboration.

Roles and Access Levels

The following roles are defined, each with specific access and permissions:

1. System Administrator

Access Level: Unrestricted

• Permissions:
  • Full Access to all boards, settings, and user management.
  • Can create, edit, delete, and manage all boards, templates, and integrations.
  • Responsible for user account management, including assigning roles and permissions.
  • Can configure security settings, backups, and API access.

2. Leadership

Access Level: High

• Permissions:
  • Can create and manage boards within their designated teams.
  • Can invite and manage users within their boards.
  • Can access reporting and analytics on board activity.
  • Limited ability to change organization-wide settings.

3. Student

Access Level: Moderate

• Permissions:
  • Can view and edit boards they have been given access to.
  • Can create personal boards but cannot share them outside their designated teams.
  • Cannot delete organization-wide boards or manage team settings.
  • Limited access to integrations and external app connections.

4. Guest

Access Level: Minimal

• Permissions:
  • Restricted access; can only view specific shared boards.
  • Cannot edit, create, or manage any content.
  • Access is granted on a temporary or per-session basis.

Access Control Measures

• Least Privilege Principle: Users should have the minimum level of access required for their responsibilities.
• Regular Audits: System and Security Administrators should periodically review user access.
• Role-Based Access Control (RBAC): Users should only be assigned roles aligned with their duties.