Access & Permissions

Defines user roles and privileges to control who can view, edit, or manage repository content

In MDVisual, access control ensures that repositories and their data are securely managed, preventing unauthorized edits or visibility into sensitive components.
Each user’s level of interaction with repositories—whether viewing, modifying, or administering—is governed by assigned roles and permissions.

User Roles

MDVisual supports a role-based access model. This allows organizations to define clear boundaries and responsibilities for users working within the same environment.

Typical roles include:

• Administrator — Full access to all repositories and system configurations. Administrators can create, edit, delete, and assign permissions to others.
• Developer — Can view and modify repository content relevant to development work. This includes refreshing repositories, analyzing code, and adding documentation.
• Viewer/Analyst — Has read-only access. Ideal for users who need to review or analyze repository data without making any changes.

Roles help maintain the integrity of repositories by limiting who can alter core content or settings.

Repository-Level Permissions

Each repository in MDVisual can have its own access configuration.
Permissions define what actions a user can perform:

• View — Grants read access to repository structure and analysis results.
• Edit — Allows modification of repository metadata, refreshing content, and updating dependencies.
• Delete — Enables removing repositories or cleaning up obsolete data.
• Manage — Provides administrative control, such as assigning access rights and performing backups.

By assigning these privileges at the repository level, teams can ensure that only authorized users can modify production or critical repositories.

Security and Data Integrity

To maintain data security and consistency:

• All repository operations (creation, refresh, deletion) are tracked through internal job logs for auditing and troubleshooting.
• Access credentials are verified against the IBM i environment before performing any library or source-level analysis.
• Sensitive or restricted libraries can be configured to allow read-only scans, ensuring no data is altered during repository generation.
• Backup repositories act as safe recovery points to restore or compare previous versions if accidental modifications occur.

Collaboration and Shared Access

MDVisual supports collaborative environments where multiple developers or teams can access the same repository.
Shared access promotes transparency while still respecting role-based restrictions.

When a repository is shared: - Each user’s actions are logged separately.
- Concurrent updates are handled safely to prevent data conflicts.
- Only users with edit or manage rights can perform repository refreshes or deletions.

Best Practices

• Assign roles carefully—only trusted users should have administrative privileges.
• Review and update access permissions regularly, especially after team changes.
• Use read-only access for analysts and auditors.
• Maintain backups of critical repositories before granting wider access.
• Enable activity logging to track repository usage and modification history.

Through well-defined roles, permissions, and security policies, MDVisual ensures that every repository remains protected, consistent, and controlled—supporting collaborative development without compromising integrity.