System Guide
Learn how to use the support management system
- 1Understand your role
Learn what your role allows you to do in the system
- 2Learn the dashboard
Understand the statistics and information available to you
- 3Learn how issues work
Understand the issue lifecycle and management process
- 4Learn your permissions
Know what actions you can and cannot perform
- 5Start handling issues
Begin working with issues according to your role
- Always verify the issue before changing information.
- Do not modify information unnecessarily.
- Use the correct category and tags.
- Keep issue information clear and accurate.
- Do not share account credentials.
- Do not perform actions outside your permissions.
- Escalate issues when you are unsure.
- Review issue history before making decisions when necessary.
- Never delete information unless you are authorized and it is required.
- Keep customer information confidential.
Introduction
The support management system helps organizations document, track, and resolve customer issues efficiently.
This platform serves as a centralized knowledge base where support teams can document common issues, their symptoms, and solutions. It enables consistent problem resolution across teams and preserves institutional knowledge.
The exact workflow depends on permissions and the type of issue. Different roles have different responsibilities.
Roles & Permissions
Understanding your role is crucial for proper system usage.
Support members are primarily responsible for handling customer issues and maintaining the knowledge base.
- Handling customer issues
- Viewing issues assigned to them
- Updating issue information
- Adding notes or relevant information
- Changing issue status when permitted
- Working with tags/categories when permitted
- Escalating issues when necessary
- Keeping issue information accurate
- Following the organization's support workflow
- Delete issues (if current permission system prevents it)
- Manage users
- Manage system-wide settings
- Perform Owner-only actions
- Access administrative functionality unless explicitly permitted
Admins are responsible for managing the support operation and overseeing content.
- Managing issues
- Reviewing support activity
- Managing categories
- Managing tags
- Monitoring issue status
- Reviewing issue history
- Supporting Support members
- Managing relevant system data
- Performing administrative actions allowed by current permission system
- Manage users (limited access compared to Owner)
- Perform Owner-only actions
- Access Owner-only functionality
Owner has the highest level of access and is responsible for system oversight.
- Full system visibility
- Managing users
- Managing Admins and Support members
- Monitoring system activity
- Reviewing statistics
- Managing important system-level settings
- Reviewing issue history
- Supervising Admin and Support activity
- Performing Owner-only actions
- Nothing - full system access
- Should perform actions carefully as they affect the entire system
| Action | Support | Admin | Owner |
|---|---|---|---|
View Issues All roles can view issues | Allowed | Allowed | Allowed |
Create Issues All roles can create issues | Allowed | Allowed | Allowed |
Update Issues All roles can update issues | Allowed | Allowed | Allowed |
Delete Issues Only owner can delete issues, admin may have limited access | Not allowed | Partly allowed | Allowed |
Manage Users Only owner and some admin levels can manage users | Not allowed | Partly allowed | Allowed |
Manage Categories Support cannot manage categories | Not allowed | Allowed | Allowed |
Manage Tags Support cannot manage tags | Not allowed | Allowed | Allowed |
View History Only admin and owner can view issue history | Not allowed | Allowed | Allowed |
View Audit Logs Only admin and owner can view audit logs | Not allowed | Allowed | Allowed |
Change User Roles Only owner can change user roles | Not allowed | Not allowed | Allowed |
Create Admin Accounts Only owner can create admin accounts | Not allowed | Not allowed | Allowed |
How the Issue System Works
Understanding the complete issue lifecycle is essential for effective support management.
- 1Issue Created
An issue enters the system either through manual creation by a team member or automatic import from customer support channels.
- 2Issue Reviewed
Support members review the issue to understand its nature and determine the appropriate response.
- 3Issue Categorized
The issue is classified with appropriate categories and tags for easy identification and searchability.
- 4Issue Worked On
Support members investigate, troubleshoot, and document the solution for the issue.
- 5Issue Updated
Changes and progress are recorded in the system to maintain a complete history.
- 6Issue Resolved
Once the issue is fully addressed, it's marked as resolved with the solution documented.
- 7History Recorded
All important changes are tracked through the issue history/audit system for future reference.
- Find an issue: Use the search bar or browse through categories and tags
- Search/filter issues: Use keywords, categories, tags, or date ranges
- Open an issue: Click on any issue title to view its details
- Understand issue information: Review the problem description, error messages, and solution
- Update an issue: Use the edit function (available based on your permissions)
- Change status: Update the issue status as work progresses
- Use categories: Assign appropriate categories to group related issues
- Use tags: Add relevant tags for better searchability
- Add/update information: Keep all details current and accurate
- Issue history: Track all changes made to the issue over time
Understanding the Dashboard
Your dashboard provides key insights into system activity and performance.
Shows the total number of users in the system
Indicates system adoption and team size
Breakdown of users by role (Owner, Admin, Support)
Helps understand team composition and permissions
Total number of issues documented in the system
Indicates knowledge base size and coverage
Number of categories for organizing issues
Reflects organizational structure of support topics
Number of tags available for issues
Indicates granularity of issue classification
User activity and issue engagement statistics
Shows system usage and effectiveness
Issue History / Audit Trail
Tracking changes is important for accountability and learning.
Issue history records all changes made to issues over time, including who made the changes and what was modified.
- What it tracks: Issue creation, updates, and deletions
- Who can view: Admins and Owners can view full history
- Why it matters: Provides accountability and helps understand issue evolution
- When to use: When investigating how an issue changed over time
Regularly review issue history to ensure proper procedures are followed and to identify patterns in support activities.
User Management
Understanding how user accounts and roles are managed in the system.
| Role | Description | Permissions |
|---|---|---|
| Support | Support members | Handle issues and maintain knowledge base |
| Admin | Admins | Manage content and support operations |
| Owner | Owner | Full system access and control |
Do not give permissions unnecessarily. Always follow the principle of least privilege - give users only the permissions they need to perform their duties.
Frequently Asked Questions
Common questions and answers about using the system.
I can't access a page. Why?
Why can't I delete an issue?
When should I escalate an issue?
Why are categories and tags important?
Where can I see what changed?
Who should I contact when something is wrong?
What Should I Do?
Role-specific guidance for getting started.
- 1Log in to the system
- 2Review assigned/current issues
- 3Open an issue and understand its details
- 4Work on the issue following company procedures
- 5Update necessary information
- 6Escalate when necessary
- 7Verify before marking as complete
- 1Review dashboard statistics
- 2Monitor active issues
- 3Oversee support activities
- 4Manage categories and tags
- 5Review issue history when needed
- 6Handle administrative tasks
- 7Escalate important issues to Owner
- 1Review overall system health
- 2Monitor all activities
- 3Manage users and roles
- 4Review system statistics
- 5Ensure proper workflows
- 6Handle critical issues
- 7Maintain system integrity