๐ Nimbly [Issue Tracker](../../Issue Tracker/IssueTrackerOverview.md): Access Control
The [Issue Tracker](../../Issue Tracker/IssueTrackerOverview.md) - Access Control feature empowers administrators to define and manage user role permissions, specifying precisely which roles can perform various actions within the Nimbly Web Adminโs [Issue Tracker](../../Issue Tracker/IssueTrackerOverview.md) module. This ensures a controlled, secure, and efficient workflow for managing and resolving all [issues](../../Issue Tracker/IssueTrackerOverview.md).
๐ Status & Compatibility
- Current Status: Released and available in the production environment.
- Platform: Web
๐ Access & Permissions
Configuring [Issue Tracker](../../Issue Tracker/IssueTrackerOverview.md) access control requires elevated privileges within the Nimbly platform.
| Requirement | Details |
|---|---|
| Required Roles | Superadmin, Account Holder, Admin |
| Interface Location | Settings > Access Control > Issue Tracker tab |
| Configurable Roles | Superadmin, Account Holder, Admin, Supervisor, Auditor, and any Customized Roles defined in your Nimbly environment. |
Export to Sheets
โจ Key Capabilities
[Issue Tracker](../../Issue Tracker/IssueTrackerOverview.md) Access Control provides granular control over user interactions with the module:
- Role-Based Access Control: Define [Issue Tracker](../../Issue Tracker/IssueTrackerOverview.md) capabilities distinctly for each user role.
- Granular Permissions: Control specific actions that roles can execute within the [Issue Tracker](../../Issue Tracker/IssueTrackerOverview.md).
- Issue [Visibility](../Data Visibility/DataVisibilityOverview.md) Management: Regulate which roles have permission to view [issues](../../Issue Tracker/IssueTrackerOverview.md).
- Issue Assignment Control: Determine which roles can assign [issues](../../Issue Tracker/IssueTrackerOverview.md) to users or departments.
- Comprehensive Issue Management: Control permissions for:
- Updating issue status
- Modifying issue due dates
- Adding members to an issue
- Creating new issue categories
โ๏ธ Core Workflows & UI Walkthrough
1. Navigating to [Issue Tracker](../../Issue Tracker/IssueTrackerOverview.md) Access Control
- Log in to the Nimbly Web Admin.
- Navigate to
Settingsfrom the main menu. - Click on
Access Control. - Select the
Issue Trackertab.
2. Viewing and Modifying Role Permissions
- The page presents a matrix:
- User Roles (e.g., Superadmin, Account Holder, Admin, Supervisor, Auditor, Customized Role) are displayed across the top.
- [Issue Tracker](../../Issue Tracker/IssueTrackerOverview.md) Actions are listed along the side.
- Key actions include:
Approve IssuesAdd new issueUpdate issue statusAssign departmentAssign userModify issue due dateAdd memberCreate Category
- Permissions are visually indicated by:
- Checkmarks: The role has the corresponding permission.
- Empty Boxes: The role does not have the corresponding permission.
- To toggle a permission, simply click on the checkmark or empty box.
- After making changes, click
Saveto apply the updated permissions.
๐ ๏ธ Configuration & Customization
Administrators have the flexibility to customize which roles can access specific [Issue Tracker](../../Issue Tracker/IssueTrackerOverview.md) functions, enabling them to tailor the system precisely to their organizationโs operational workflows and security policies.
๐ Related Features & System Connections
- User Roles: This feature is fundamentally built upon the user roles and definitions established elsewhere in the Nimbly Web Admin.
- [Issue Tracker](../../Issue Tracker/IssueTrackerOverview.md) Module: Access Control directly governs user capabilities within the [Issue Tracker](../../Issue Tracker/IssueTrackerOverview.md).
- Dashboard [Issue Tracker](../../Issue Tracker/IssueTrackerOverview.md): Permissions configured here directly impact a userโs ability to interact with [issues](../../Issue Tracker/IssueTrackerOverview.md) visible in the Dashboardโs [Issue Tracker](../../Issue Tracker/IssueTrackerOverview.md) overview. This dashboard provides real-time [visibility](../Data Visibility/DataVisibilityOverview.md) into reported [issues](../../Issue Tracker/IssueTrackerOverview.md), enabling proactive monitoring, identification of recurring problems, and continuous process improvement based on the access granted to various roles.
โ Best Practices
- Principle of Least Privilege: Always grant only the minimum necessary permissions for each role to perform its duties effectively. Avoid over-privileging users.
- Regular Review: Periodically review and update permissions to ensure they accurately reflect any changes in user roles, responsibilities, or organizational processes.
- Thorough Testing: After making any changes to permissions, test thoroughly with affected user accounts to verify that users have the correct and intended access levels, and no more.